AR# 7013


14.x Timing - The maximum delay path does not match the minimum period value in any timing report (two-phase)


When I examine a timing report, the reported maximum delay path is less than the minimum period (by definition, the maximum delay path should be the same as the minimum period). I have instructed the software to keep the longest five path delays.


Check your design to see if any two-phase clocks are present, as these will affect the delay. For example, if the period is 50 ns, the total delay will be 50 ns x 2 = 100 ns to account for the two-phase clock in the design.

Consequently, if the highest reported delay is 75 ns, you must report more than just five delays in order to see the two-phase clock at 50 ns, as delays are reported in order from longest to smallest.

Also, if related clocks are used, the minimum period can be based upon a cross-clock domain path. To see the actual minimum period, run an Auto-Generated Path Report from Timing Analyzer or TRACE.

For more information, see (Xilinx Answer 4313) and (Xilinx Answer 6501).
AR# 7013
Date 12/15/2012
Status Active
Type General Article
Tools More Less
People Also Viewed