7051 - Radiant: Why is the NBR Summary seems to be showing different values compared to the PAR Timing Report in terms of number of timing violations?

There is an info and note on the Place & Route report that mentions that NBR calculations are different from the calculations on the Place & Route Timing Report.

The values may not be equal to the values reported in the timing report.

Furthermore, number of connections is based on the Slice to Slice, Slice to Pad, Slice to component or pad to component connection. This is not the entire timing path which is reported in the timing tool which is from one Pad/FF to another Pad/FF. A timing path may have multiple connections on it depending on the number of logic levels of the path.

For final timing signoff, please always refer to the Place & Route Timing Analysis Report.

• Related Articles

• 7420 - Radiant: Why is the result of my timing different on the PAR report compared with the TWR report?

  The result from .PAR and from .TWR is expected to be different. For Radiant 2023.2, multi-corner timing analysis is implemented, the idea is for: A. 2023.2 1) PAR Timing Analysis (.PAR) - The Timing model used is the model with "WORST" case at ...

• 7761 - Why is the output of "des_set_operating_condition" is always -1C in TCL+?

  Below is a step-by-step explanation on why the default operating temperature in TCL+ defaults to -1C and observe its effect on timing analysis: 1. When you open the PAR-generated UDB file using des_read_udb and run des_report_operating_condition, the ...

• Radiant: How does the user interpret the Single Clock Domain table entries on the Clock Summary section of the Place & Route Timing Analysis Report?

  The Single Clock Domain table of the Clock Summary Section of the Place & Route Timing Analysis report: There are three values on this table: 1. The Target is the frequency or period based on the clock constraint. This should always be the lowest of ...

• 6787 - Radiant: Is it recommended to check the initial timing report generated by Synplify Pro under the SRR file?

  Customers should not be using the timing report generated by Synplify Pro. There is a warning on the Synplify Pro timing report to refer to the FPGA vendor place and route report. See the warning below: Please use the timing report generated by ...

• 7037 - All Nexus / Radiant 2023.1 or earlier: How are the clock-to-out max and clock-to-out min values on the I/O Timing Analysis report calculated?

  Clock-to-out max corresponds to the arrival time of the data of the external timing path when setup time is analyzed. Clock-to-out min corresponds to the arrival time of the data of the external timing path when hold time is analyzed. If there are ...