Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Timing problem in cts

Status
Not open for further replies.

cyrax747

Full Member level 3
Joined
Nov 8, 2012
Messages
167
Helped
13
Reputation
26
Reaction score
11
Trophy points
1,298
Location
Bangalore
Activity points
2,494
Hi

My question is i am using 2 scenarios func worst and func best.my default scenario is func worst .i did placement and it worked fine.i did cts too in default scenario and after that if i do report timing clock is propagated by default with out set propagated clocks command in icc

When i change to func best the clock is not propagated it is showing idle.what is the reason? If i give the command set propagated clocks then in the report for hold it is taking propagated clocks but with huge clk network delay.this is my main problem.why it is taking so huge values for hold when it is taking value for setup? Why clock is not propagated for hold scenario?

I have main clocks and also virtual clocks in the design.another issue is report timing to any clock path for both setup and hold also is giving path unconstrained? Why is it so??

Please clarify i am specifying all the required files sdc scenario info and all.

This is my show stopper.please give me a solution ASAP.
 

Why are you doing one mode at a time? You should do something like MMMC (multi mode multi corner).
 

Hi are you saying to active all scenarios instead of one scenario at a time ? what is the benifit ? how it is going to help my issue?
 

Hi are you saying to active all scenarios instead of one scenario at a time ? what is the benifit ? how it is going to help my issue?

you should because MMMC is the industry standard for years. BC/WC is still ok. But what you are doing is WC THEN BC. This is not helpful and in many instances will be a nightmare for timing closure. Of course you will see hold issues when everything suddenly became faster!
 

so i have to put active all scenarios and give a run ? cts by default taking worst only.how to do for best also???
 

so i have to put active all scenarios and give a run ? cts by default taking worst only.how to do for best also???

that depends on your tool. I use mostly cadence, and CCOPT takes all scenarios into consideration.
 

even though there is more tran my clk network delay is more when i am doing hold analysis.setup is fine...only one net is bringing more cap and tran.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top