mongrainjr
Newbie level 1
set_clock_uncertainity
I use: set_clock_uncertainty 0.4 [get_ports CLK_PIN]
in DC and Primetime. When I write the timing report I see the 0.4ns is taken into account in the Flop-to-flop analysis. However, It is not taken into acount in the Flop-to-PAD analysis.
The set_clock_uncertainty is use to emulate the skew but also the Jitter on the clock. In a Flop-to-PAD analysis we need to take into account Jitter. Is there a way to emulate teh Jitter for Flop-to-PAD analysis ?
I use: set_clock_uncertainty 0.4 [get_ports CLK_PIN]
in DC and Primetime. When I write the timing report I see the 0.4ns is taken into account in the Flop-to-flop analysis. However, It is not taken into acount in the Flop-to-PAD analysis.
The set_clock_uncertainty is use to emulate the skew but also the Jitter on the clock. In a Flop-to-PAD analysis we need to take into account Jitter. Is there a way to emulate teh Jitter for Flop-to-PAD analysis ?