Fitter routing operation verbosity

[AEsqu]

Hello,

Vivado brings several information while the routing is running (congestion level,  TNS/WNS, ..)

which are quite useful.

Quartus stays totally quite and do not show any info,

only when it finishes (with an error if it cannot route for example).

Is it possible to raise the verbosity to get some information of what quartus is busy with?

I use quartus prime 21.1.0 standard edition.

[AEsqu]

Well, when it fails it gives the signal names it couldn't route at the end + the coordinates.

[SyafieqS]

Hi Alexandre,

You can find more information in compilation report regarding the routing. Judging from your snapshot, failed routing is due to resource used more that device capacity, you probably need to modify your code or do some optimization to reduce the resource. 

[SyafieqS]

Hi Alexandre,

May I know if there is any update from your end?

Regarding the info related to TNS,WNS, you can actually look at timing analyzer report in compilation report (assuming successfully pass the flow) with simplify information. You can see more details in Timing Analyzer for more other report.

[AEsqu]

Ok so you confirm that verbosity cannot be changed during the run.

Let's close the ticket.

[SyafieqS]

We do not receive any response from you to the previous reply that I have provided, thus I will put this case to close pending. Please post a response in the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you with your follow-up questions. 

[AEsqu]

Note: For some reason, using fast fit makes it easier to route than auto fit.

[AEsqu]

What does really help Quartus to route the design is to reduce the fanout.

For example a fanout of 128 set in Synplify helps a lot.

[aesq]

I will try the same option as I indicated in the other topic to solve the routing problem in the cyclone V:

set_global_assignment -name AUTO_CLOCK_ENABLE_RECOGNITION OFF