道歉，有那麼難嗎？

某人很篤定的說：在跨年夜。
還要別人回去認真地看一下某人安排的行程。
結果，打臉了，一句道歉也沒有。
啊！不是很厲害！都不會忘！都不會記錯！
（這就是我今天臉臭，不爽的原因，說完。）

2016 生日快樂

原本是想給自己一個「一日竹嘉」的生日禮物，
就在著好裝，上好補給品，準備開門出發的時候，
這時，還陰暗的天空突然泛著光，
天上的娘娘下凡了。

經過娘娘一番開導後，
最後決定開車南下，
但是單車的魂還燃燒著，
只好載著它南下，
雖然不曉得何時可以騎？

所幸，沒有真的在梅山換裝，騎上36彎。

真的要相信：凡事都是老天爺最好的安排！

表裏不一

我說：當初的承諾是，大藍班的正規活動，只要有壽星家庭舉辦，我們一定參加。（除非我們有重大事情）
你說：那是我給的承諾！
（當初確實沒有白底黑字，認了！）
我說：大藍班當初成立的宗旨，是要延續沒有利害關係的友誼，並不是為你而設計的。

你說：現在都變成家長聯誼會。
（So what，變成家長聯誼會又如何？小朋友還是可以相處在一起；大朋友也可以找到舒壓的管道。管他叫什麼名字！）

竟然，你不想參加，就直接明講，不要編個理由，結果理由不成立，就說：我當初就沒有說要去。
當初沒有想參加，就直接說不去，不要編理由。（又是沒有白底黑字，但，這是正常人都有的默契。）
兩個標準，怎麼說都是你說了算，這，我不喜歡。

會長，他媽的會長頭銜，是我爭取來的ㄛ∼能吃啊！誰要啊！不要像政客的嘴臉一樣，道理說不過人家，就在這種無關痛癢的地方進行意識形態的爭辯。歹戲拖棚∼

讚美

我們都太久沒有讚美彼此了，

久到快遺忘了彼此曾經是戀人∼

對？錯！

有一種對，

就是你對，我錯，總是！

有一種道歉，

就是你不會，永遠！

有一種叨念，

就是我錯了，你念！你錯了，還是你念！

這是甚麼世界！

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

Hi, Bokong

 

I think innovus is right. It should be MCP2.

 

set_multicycle_path 2 -end -setup -from [get_cell inst_master_delay/inst_mstr_dly_control/bypass_reg]

set_multicycle_path 1 -end -hold -from [get_cell inst_master_delay/inst_mstr_dly_control/bypass_reg]

 

I don’t know why tempus is wrong.

 

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

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