Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 14337
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Different OpCond for different libraries

archive

Hello,

I am using two different libraries for core and IO cells and the process variation range is different for these libraries. I think the way to avoid being pessimistic is to set different operating conditions for these libraries. Is it right?
Anyone can tell me how to set different operating conditions for different libraries in Encounter (6.2)?

Thanks,
Cristiano.

PS.: The command reference document (fetxtcmdref.pdf) is a little bit confuse explaining the -forceLibrary option for setOpCond command. It says "Do not use this parameter with the -min, -max, or -powerDomain parameters." but uses these parameters in its example. (?)


Originally posted in cdnusers.org by clsantos
Parents

  • Dear clsantos:

    I think your point is how to define Operating Corners when facing multi 'dot lib', for the bc-wc mode, you have to set 1 OC for the setup check, it means that you have to choose a OC in certain lib, although different libs may have different OC ( at the same corner), typically, all the libs (IO, Std Cell........) will have the same OC at 1 corner, like P 1.0 V 1.2 T 0. Hold analysis is the same. But at the OCV mode, things are different, you need to define derating factors, 0.9 (for example) for setup analysis, and 1.1 for hold analysis. These derating factors are offered by YOUR FOUNDRY, like TSMC, UMC or .........

    Hope this can help you! For Furthere reference, I think you'd better try seeing Prime Time user guide.


    Originally posted in cdnusers.org by eminemshow
Reply

  • Dear clsantos:

    I think your point is how to define Operating Corners when facing multi 'dot lib', for the bc-wc mode, you have to set 1 OC for the setup check, it means that you have to choose a OC in certain lib, although different libs may have different OC ( at the same corner), typically, all the libs (IO, Std Cell........) will have the same OC at 1 corner, like P 1.0 V 1.2 T 0. Hold analysis is the same. But at the OCV mode, things are different, you need to define derating factors, 0.9 (for example) for setup analysis, and 1.1 for hold analysis. These derating factors are offered by YOUR FOUNDRY, like TSMC, UMC or .........

    Hope this can help you! For Furthere reference, I think you'd better try seeing Prime Time user guide.


    Originally posted in cdnusers.org by eminemshow
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.