You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to directly use hls_run.start(xrt::autostart{2}) (run the two iterations without updating the input array and fetching the output array). But the execution time is simply 2x of hls_run.start(xrt::autostart{1}). However, if pipelined execution is enabled, I expected a much shorter execution time through overlapping - is this the case?
Could you guide me how to enable the pipelined execution? E.g., did I miss anything on the HLS side or the XRT side?
Best,
Hanchen
The text was updated successfully, but these errors were encountered:
Hi,
I'm trying to implement the pipelined execution model described in XRT document. Conceptually, I have the following HLS design:
->
means streaming channels (AXI-S), while=>
means external memory access (AXI-MM). I want to implement the following execution schedule in XRT:On the HLS side, I have set the following configurations:
I tried to directly use
hls_run.start(xrt::autostart{2})
(run the two iterations without updating the input array and fetching the output array). But the execution time is simply 2x ofhls_run.start(xrt::autostart{1})
. However, if pipelined execution is enabled, I expected a much shorter execution time through overlapping - is this the case?Could you guide me how to enable the pipelined execution? E.g., did I miss anything on the HLS side or the XRT side?
Best,
Hanchen
The text was updated successfully, but these errors were encountered: