07-11-2017 09:41 AM
I have a function with several for loops that vary the number of times they are executed overtime. Therefore, Vivado HLS cannot estimate what its latency is.
Is it possible to measure how many clock cycles the function takes to execute every time I call it from the test bench file?
07-12-2017 06:11 PM
In short, look at the loop trip count directive. Specify a min/max trip count for each loop and HLS can make an estimate of the overall function latency. It should already report the II and loop latency for each loop and pulls that information with the bounds you provide to report overall latencies.
07-12-2017 09:23 PM
If you do a cosimulation, HLS should be able to calculate latency there (based on the provided test data). It can't do it during C simulation because the C simulation has no concept of "clock cycles".
07-15-2017 01:08 PM