• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. using Low Vth and Mid Vth library

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 90
  • Views 12993
  • 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

using Low Vth and Mid Vth library

archive
archive over 17 years ago

Hi,

In my  design, i have to use low Vth library for one particular Block B1 alone for better timing.
The other block B2 should use only Mid Vth library cells.

But i found that Soc encounter is picking up Low Vth cells for the block B2 also, during Timing optimiztion, which is not expected.

How to restrict the usage of Low Vth cells and Mid Vth cells for blocks B1 and B2 respectively?


thanx
sundar


Originally posted in cdnusers.org by sundaresan
  • Cancel
  • archive
    archive over 17 years ago

    If the requirements are so stringent - then perhaps a hierarchical flow would be a way to do it. Are your constraints all clean?

    Sanjay


    Originally posted in cdnusers.org by ssunder@sioptical.com
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    For my understanding on the way Encounter works , there is no real way to do what you want, optDesign will use all available cells to fix timing issues, all means all available VT cells.
    optLeakage goal is to work on DB trying to switch lowVT cells to highVT cells.
    Please try it after optDesign -setup.
    Personnaly I use it and the gain of leakage is very good (The CPU runtime is not negligeable...).
    Another impact of this command, it help Hold fixing, so I use it just before optDesign -hold.

    Pat.


    Originally posted in cdnusers.org by bougantp
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information