• 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. Mixed-Signal Design
  3. Doubt reg a .lib file parameter

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 14802
  • 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

Doubt reg a .lib file parameter

anandmohan
anandmohan over 7 years ago

Hi ,

In the above shown snapshot of a .lib file generated using Liberate, the 'when' conditions are coming from the tempate file, but from where does "sdf_cond:adacond0" come from ? I havent specified anything of that kind in the template file...and also what does it mean ?...pls help...thanks in advance...

  • Cancel
  • Guangjun Cao
    Guangjun Cao over 7 years ago

    It's probably the sdf condition found by the tool is too long. You can define sdf_cond attribute yourself with either define_arc or set_attribute or using a user data post processing file. Please refer to liberate manual for details.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • anandmohan
    anandmohan over 7 years ago in reply to Guangjun Cao

    Hi Guangjun,

    Thanks for the reply. On checking the manual, its mentioned the sdf_cond is by default adacond0,adacond1,adacond2....etc for unique 'when' conditions. But in my .lib file its adacond0 for 2 unique 'when' conditions,where it should be adacond0 and adacond1

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Guangjun Cao
    Guangjun Cao over 7 years ago in reply to anandmohan

    please use -sdf_cond option in define_arc command to ensure it is correct in .lib. you can also use set_attribute command to change this as a post process step.

    • 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