Evening, everyone, sincerely hoping for your help for the given troubles:
I have done the signoff STA for my design, for which the result shows no timing violation, however, the post simulations fails. and I have reported the timing_path which shows violations during post_simulation, and found no violations in the STA report.
where does this result from?
given below is the detailed info:
A.the post simulation log:
Timing violation in testbench.u_design_1.u_design_top1.u_encodingT.u_tmp.\enc_out_shifter_reg[56]
$setuphold( posedge CK &&& (vcond2 == 1'b1):3189300120, negedge D:3189300120, limits: (10,10) );
B.the STA report for the path above
****************************************
Report : timing
-path_type full
-delay_type min
-max_paths 1
Design : design
Version: E-2010.12-SP3
Date : Tue Sep 20 21:14:28 2011
****************************************
Startpoint: u_design_top1/u_encodingT/u_tmp/enc_out_shifter_reg[56]
(rising edge-triggered flip-flop clocked by encodingT_clk)
Endpoint: u_design_top1/u_encodingT/u_tmp/enc_out_shifter_reg[56]
(rising edge-triggered flip-flop clocked by encodingT_clk)
Path Group: encodingT_clk
Path Type: min
Point Incr Path
------------------------------------------------------------------------------
clock encodingT_clk (rise edge) 0.00 0.00
clock network delay (propagated) 2.90 2.90
u_design_top1/u_encodingT/u_tmp/enc_out_shifter_reg[56]/CK (SDFPNSRBQQB1)
0.00 2.90 r
u_design_top1/u_encodingT/u_tmp/enc_out_shifter_reg[56]/QB (SDFPNSRBQQB1)
0.57 & 3.47 r
u_design_top1/u_encodingT/u_tmp/U64/YN (OAI22D1) 0.14 & 3.61 f
u_design_top1/u_encodingT/u_tmp/enc_out_shifter_reg[56]/D (SDFPNSRBQQB1)
0.00 & 3.61 f
data arrival time 3.61
clock encodingT_clk (rise edge) 0.00 0.00
clock network delay (propagated) 2.90 2.90
clock reconvergence pessimism 0.00 2.90
clock uncertainty 0.60 3.50
u_design_top1/u_encodingT/u_tmp/enc_out_shifter_reg[56]/CK (SDFPNSRBQQB1)
3.50 r
library hold time -0.19 3.31
data required time 3.31
------------------------------------------------------------------------------
data required time 3.31
data arrival time -3.61
------------------------------------------------------------------------------
slack (MET) 0.30