An question about set_clock_uncertainty ???

Status
Not open for further replies.
P

pengfan

Newbie level 5
Joined
Jul 10, 2005
Messages
8
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,352
set_clock_uncertainty

DC constraint has the following constaint statement:

set_clock_uncertainty -setup 1.5 [get_clocks clk]

set_clock_uncertainty -hold 0.5 [get_clocks clk]　，

To setup time analysis ,why set_clock_uncertainty is 1.5 ?
but to hold time analysis,why the value of the set_clock_uncertainty is 0.5?

why the value of the set_clock_uncertainty is different ?
 

set_clock_uncertainty

that is ur company standard
each company has it's own constraint policies.

regards
srinivas
 

about set_clock_uncertainty

Hi,

In general,

The variation u see in the constraints is due to "setup" check done by slow library and "hold" check done by fast library.

Regards,
dcreddy
 

set_clock_uncertainty pll actel


setup check is between two different clock edges. So cycle to cycle jitter from clock source is also added to uncertainity in addition to jitter due to clock path.

In hold, the check is against the same edge, hence cycle to cycle jitter doesn't matter. Hence you account only for jitter due to clock path. Hence uncertainity is much less.
 

Status
Not open for further replies.

Similar threads

Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…