Hi Chris
Is your clock path delay computed? Can you please put in a snippet of the timing report? Is your clock propagated?
Hi Jeevan,
Here is the header of report from Talus, pls note clock period is 5000ps while output_delay is 2000ps
Reference arrival time ******************** 0
+ Cycle adjust (clk:R#1 vs clk:R#2) ********5000
- Setup time************************ -2000
------------------------------------------ -------
End-of-path required time (ps) ***********3000
Starting arrival time **********************0
+ Clock path delay *********************1368
+ Data path delay ********************* 2010
------------------------------------------ -------
End-of-path arrival time (ps) ************* 3378
As above, the setup check of reg2out path failed distinctly, but it is not true as clock latency of capture path is not added, I think.
ICC/PT really account for capture path clock latency, thus setup in ICC/PT is met.