• 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. Encounter's "common timing library"

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 92
  • Views 1575
  • 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

Encounter's "common timing library"

mwb1
mwb1 over 7 years ago

From all the documentation that I see, it looks like "common timing library" in encounter's "import design" menu should point to the typical case library. Similarly to how the "max" and "min" libraries point to the worst and best case libraries. 

However, when I look at the log, it says that its overwriting the libraries. See below. 

Reading max timing library <my_wc_timing_lib>

................etc

Reading min timing library <my_bc_timing_lib>

................etc

Reading max timing library <my_tc_timing_lib> 

................etc

Reading min timing library <my_tc_timing_lib> 

................etc

Those last two messages seem to indicate the reading in of the common-timing library is over-writing my max and min timing libraries. Is this correct? Is this what I should see? 

Thanks

Matt 

  • Cancel
Parents
  • Kari
    Kari over 7 years ago

    what version are you using? the libraries should be set up using a MMMC file so that you can have as many analysis views as your design requires...

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Kari
    Kari over 7 years ago

    what version are you using? the libraries should be set up using a MMMC file so that you can have as many analysis views as your design requires...

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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