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 the three frequencies (lower than the actual and lower than the maximum for the block) or at least equal to the actual frequency.
2. The Actual is the actual frequency that the design can reach for the specific clock considering the timing delays due to logic. This could either be equal to the maximum clock frequency or lower but this should always be greater than the clock frequency set on the constraints.

3. The MPW is the maximum frequency that the specific clock can reach. This is either based on IO port standards if the clock is from a port, from fabric speed if the clock is generated from fabric, or if this is a clock from hardened blocks then this is limited by the physical implementation of the hardened block. MPW stands for minimum pulse width.

 

• Related Articles

• 129 - Lattice Diamond: How can I single out a specific path or transfer in the timing analysis TRACE report?

  TRACE lists the paths per timing preference starting from the worst case path going down. Let's say you want to look at a path that maybe the 1001st worst case path in the design. You do not want to list 1001 paths in the trace report. How can this ...

• 1712 - Diamond: How can user get estimated timing of my design before running place and route?

  In both ispLEVER and Lattice Diamond tools, user can generate the timing using the static timing analysis tool after map, and before place and route. The static timing analyzer (TRCE) will generate timing using estimated models, as well as the fanout ...

• <div>Radiant: What type of clocks do the Clock Port column of the I/O Timing Analysis Report refer to?</div>

  For I/O timing analysis, the "Clock Port" column/field could refer to the following depending on the destination clock: 1. Internal oscillator clock: If the destination clock is directly from the internal oscillator, or if the destination clock is ...

• 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.

• All Nexus / Radiant version 2023.1 or earlier: Are there any guidelines when changing the speed grades for Place & Route Design and Place & Route Timing Analysis on the strategy settings?

  It is not recommended to change the default speed grade settings for both the Place & Route (PAR) Design and Place & Route Timing Analysis. DEFAULT VALUES: The default values (especially for HOLD) are for worst case timing calculations. For PAR ...