RE: [juno] timing report is different between tempus and innovus

 

Bokong,

 

I am doing n7 eco now, I will look into later.

 

Thanks

 

Ying

From: Bokong Chen
Sent: Monday, September 19, 2016 5:21 PM
To: Ying Li
Cc: Phoebus Chiou; David Li; bokongchen.58-do@blogger.com
Subject: [juno] timing report is different between tempus and innovus

 

Hi, Ying,

 

Report in the Innovus

---

Path 1: MET Setup Check with Pin inst_write_path_tb/inst_wrdq2_macro/inst_tsel_macro/inst_tsel_wr_macro/inst_tsel_wr_strt_wr_n/hic_dnt_out_reg/CP

Endpoint:   inst_write_path_tb/inst_wrdq2_macro/inst_tsel_macro/inst_tsel_wr_macro/inst_tsel_wr_strt_wr_n/hic_dnt_out_reg/D (^) checked with  leading edge of 'clk_wr_phase_7'

Beginpoint: inst_master_delay/inst_mstr_dly_control/bypass_reg/Q                                                            (v) triggered by  leading edge of 'clk_phase_0'

Path Groups: {clk_wr_phase_7}

Analysis View: func_ss0p72vm40c_cworst_CCworst_m40c_setup

Other End Arrival Time          0.717

- Setup                         0.038

+ Phase Shift                   0.000

+ CPPR Adjustment               0.009

+ Cycle Adjustment              0.749

- Uncertainty                   0.075

= Required Time                 1.362

- Arrival Time                  1.323

= Slack Time                    0.040

 

Report in the Tempus

---

Path 1: VIOLATED Setup Check with Pin inst_write_path_tb/inst_wrdq2_macro/inst_tsel_macro/inst_tsel_wr_macro/inst_tsel_wr_strt_wr_n/hic_dnt_out_reg/CP

Endpoint:   inst_write_path_tb/inst_wrdq2_macro/inst_tsel_macro/inst_tsel_wr_macro/inst_tsel_wr_strt_wr_n/hic_dnt_out_reg/D (^) checked with  leading edge of 'clk_wr_phase_7'

Beginpoint: inst_master_delay/inst_mstr_dly_control/bypass_reg/Q                                                            (v) triggered by  leading edge of 'clk_phase_0'

Path Groups: {reg2reg}

Other End Arrival Time          0.729

- Setup                         0.038

+ Phase Shift                   0.000

+ CPPR Adjustment               0.010

- Uncertainty                   0.075

= Required Time                 0.626

- Arrival Time                  1.301

= Slack Time                   -0.675

 

Which one is the correct timing report ?

 

The detail timing reports are as following.

Innovus) /proj/juno/work/bokong/cdn_hs_phy_data_slice/open6/OPENds/a

Tempus) /proj/juno/work/bokong/sta_signoff/phy/reports/cdn_hs_phy_data_slice/WCLcworstm40c_Func_setup/cdn_hs_phy_data_slice.timing.reg2reg.max.ets (Path 1)

 

 

Bokong