• 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. Custom IC Design
  3. [liberate] FAILED TO GET MOS MODEL FOR 'XMP32_0'!

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 969
  • 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

[liberate] FAILED TO GET MOS MODEL FOR 'XMP32_0'!

sherryshe
sherryshe over 1 year ago

I am trying to characterize a standard cell library, but liberate gives me the following errors. The point is that some of the standard cells can pass while the other such as MUX4D8 can not. As shown in the blow, MUX4D8 can pass the timing test ( can be checked in the deck ), when it comes to power, error occurred.

*Error*

The model they used is the same (same type NMOS and PMOS) and been set in the char.tcl.

Do you have any suggestions for this problem?

Thank you in advance!

  • Cancel
  • Guangjun Cao
    Guangjun Cao over 1 year ago

    Hi Sherryshe,

    Which Libeate version are you using?

    Do you have -extsim spectre in char_library command?

    Is the line for instance XMPM32_0 complete and correct in syntax?

    Did you run the saved deck for the failed arc? Please use extsim_flatten_netlist=0, ski_enable=0, extsim_save_passed/failed=deck for this debug. 

    Regards,

    Guangjun

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sherryshe
    sherryshe over 1 year ago in reply to Guangjun Cao

    Hi Guangjun,

    The problem was solved by setting extsim_flatten_netlist and ski_enable = 0.

    Thank you for your help!!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Guangjun Cao
    Guangjun Cao over 1 year ago in reply to sherryshe

    Neither of the two is recommended for production flow.

    If you are using latest Liberate release, and either or both parameters must be used to avoid the issue, please contact customer support for furtehr investigation.

    Guangjun 

    • 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