- Newest
- Most votes
- Most comments
Hi,
Looks like either your design is running into congestion issues, or you are running out of memory on host machine. Does the build run successfully if you reduce the number of multiplications in your design?
Alternatively, you can try running builds on instances with larger memory.
Vivado tool outputs vivado.log to check the progress of builds.
Thanks!
Chakra
Hi Chakra,
Thank you very much for your reply!
1. Possibility of running out of memory on host machine
I've looked at the the RAM usage on the host machine. It uses at most 24.7 GB RAM with total of 60 GB RAM available on the host machine. Therefore, I suppose memory is not a critical issue here?
2. Does the build run successfully if you reduce the number of multiplications in your design?
Yes, the build does run successfully if the number if multiplications is reduced. Please see https://forums.xilinx.com/t5/Vitis-Acceleration-SDAccel-SDSoC/Vitis-hardware-emulation-cannot-finish-scheduling/td-p/1131555 for my vivado hls reports for matrix size of 100 and 1000. When compiling with matrix size of 1000, seems like vivado hls is stuck on scheduling. Do you have any insights on why this happens? Any suggestions you have is greatly appreciated!
According to my post in Xilinx (the link above), seems like they also recommend me to use the latest release of Vitis, which is not officially supported by AWS. I am wondering if that is worth trying?
Thank you,
Owen
Hello,
Thanks for the feedback. Please stay tuned for availability of the latest Vitis version for F1.
-Chakra
Turns out the problem is due to a large array partition factor (500). If any is caught into the problem as I did please try a smaller partition factor.
Relevant content
- asked 3 years ago
- asked 4 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 20 days ago