Skip to content
Snippets Groups Projects
Commit c5c5f214 authored by Yaman Umuroglu's avatar Yaman Umuroglu
Browse files

[Docs] document flushing requirement after AXI lite read/write

parent 66a722ba
No related branches found
No related tags found
No related merge requests found
IMPORTANT: After using AXI lite to either read or write the weights,
always "flush" the accelerator by first passing a dummy input
vector through the accelerator. This will get rid of any old
weight data from the weight FIFOs.
Memory Streamer Address Map
......@@ -37,6 +41,5 @@ C | N/A
To perform a write to mem[0], the AXI master writes to AXI Addr 0,4,8 in any
order, then writes to AXI Addr 0xC to commit the write. To read mem[1][63:32],
the AXI master reads from AXI Addr 0x14. The words of mem can be written to or
the AXI master reads from AXI Addr 0x14. The words of mem can be written to or
read from in any order.
......@@ -99,6 +99,12 @@ class StreamingFCLayer_Batch(HLSCustomOp):
# (mem_mode = decoupled only) whether weights will be writable through
# an AXI-lite interface during runtime
# 1 for enabled, 0 for disabled.
# see finn-rtllib/memstream/doc/README for more about the memory
# address map used for writable weights
# IMPORTANT: After using AXI lite to either read or write the weights,
# always "flush" the accelerator by first passing a dummy input
# vector through the accelerator. This will get rid of any old
# weight data from the weight FIFOs.
"runtime_writeable_weights": ("i", False, 0),
}
my_attrs.update(super().get_nodeattr_types())
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment