05-28-2020 04:30 PM
I am using Xilinx System generator to build an ip and Vivado 2018.3 to implement it on RFSoC ZCU1275 board. However, I received an error saying design is not routable as the congestion level is 6.
Therefore, I changed the implementation strategy to Congestion_SpreadLogic_high. However the issue still persists.
I have attached a screenshot of the error message, portion of the log and the block design here with. Can someone help me with this?
05-28-2020 06:31 PM
You can refer to https://www.xilinx.com/support/answers/66314.html . Congestion is a complex issue, sometimes you have to modify your design.
05-28-2020 07:38 PM
Hi @najathakram ,
Also as the congestion level is of 6, you can try different sets of directives in each phase of implementation and try running multiple implementation runs.
Also if you want it to be checked at our end, you can share the post place dcp.
Accordingly i will arrange the secure EZMove package.
05-28-2020 10:41 PM
Thank you very much. I am doing some changes to the design and, let me try a simplified version.
05-28-2020 10:52 PM
Thank you very much for the kind response. I would really appreciate if you could help me with this. However, I am not familiar with running multiple implementation runs at different implementation phases. I simply set the implementation strategy and tried running that. I have tried few other options, yet they didn't work. Could you please guide me through that?
I have added implementation files in this folder.
Thank you very much!
05-29-2020 05:05 PM
Taking a look at the utilization, many of the resources are not very utilized such as the LUTs (7%) and FFs (16). However, the DSPs are greatly over-utilized at 86.89 percent. This means a large number of bus nets using local resources. This can be seen by enabling the Vertical Routing Congestion metrics from the device view, which look to follow the DSP sites.
I would try moving many of these to other logic resources. To do so, the synth_design argument "-max_dsp 3000" can be used. This should put the DSPs at around 70 percent.
I would also suggest running the report_clock_interaction report and addressing the paths with no common clock marked as "Timed (unsafe)". This will not help the implementation QOR.