-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation error with Zynq fpag #279
Comments
This looks like there are old packages hanging around. Can you try deleting these directories to get a totally fresh start and trying again? ~/.ivy2/cache/edu.stanford.cs.dawn ? |
It works now. |
Just caught a mistake in the synth makefile (if you are using our scripts to synthesize instead of your own). I will push a fix, but in the short term you should edit zynq.hw-resources/build/Makefile. Change line 24 from |
Thanks for reminding. I manually changed it and reran the flow. Everything works fine till Phase 3 of vivado synthesis. "The packing of instances into the device could not be obeyed." Any insight that why this would occur? I am using Vivado v2017.2_sdx.
|
It looks like the design didn't fit on the board. There should be a synth_utilization_hierarchical.rpt in the verilog/ directory that may give hints as to what parts of the app are taking a lot of resources. We can look at that and try to figure out if there are opportunities for improvement in the app. The best way is to either open the rpt in Vivado, or parse it as a csv and sort by whichever resource you want to tackle first (probably LUTs) |
I parse it as a csv and sort by LUT usage and got this:
It seems no particular component used too much resources but when they addup, it becomes unacceptably large. Again, I am using |
Thanks for pointing this out. It seems like we've never actually tried to synthesize this app before 😬 . We have usually just used it to show how to do miscellaneous things in spatial, but the load+store+scatter+gather streams seem to add up to a DMA that is way too big for the Zynq (Fringe is usually around 25% of this board if I recall correctly. 62.83% is huge. Most of the area for real apps should go into the AccelUnit). If your goal is to just get the flow working from start to finish, you can just comment out the scatter and gather lines (49 and 51) and I think it should fit (testing now). |
Following the advice in #277 , I tried to use Zynq as target device. However, this result in errors at compilation stage.
I used spatial-quickstart run the following commands:
This results in a lot of errors.
The text was updated successfully, but these errors were encountered: