• 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. ELC: liberty file output capacitance index different from...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 91
  • Views 13668
  • 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

ELC: liberty file output capacitance index different from simulation

Brian Harrison
Brian Harrison over 15 years ago

When generating a liberty dotlib for a bi-directional buffer, I have noticed that the cap index differs from what was used in the simulation.  This only affects the PAD of the buffer and not the internal output.  It appears to add the capacitance of the ouput pin(PAD) to the simulated value.

Example:

 Using this in my setup file:

Index    CLASS_A  {

        load =  3.0000p   4.1667p   5.3333p   6.5000p   7.6667p   8.8333p   10.0000p  ;

 I get the following from the generated liberty file.  Not capacitance of pin is listed in the dotlib as 2.124p

        index_2 ("5.12392, 6.29062, 7.45722, 8.62392, 9.79062, 10.9572, 12.1239");    p

 

 When the bi-buf is simulated as an input, the core output pin cap index match my internal index load, also noted that core output pin cap is 0.

 

Is there a way to turn this off to not add the total net capacitance of the pin and index load.  I'm trying to compare modifications to an IO cell and see if they affect timing, however because the PAD ouput has changed slightly I get different indexes.

 

Thanks.

 

  • Cancel
  • archive
    archive over 15 years ago

    Hi Brian,

    Please file a SR or CCR.

    Wilson 

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Brian Harrison
    Brian Harrison over 15 years ago

     It appears that the alf2lib function is what is causing the problem.  The data tables and indexes are correct in the alf file. 

    This is what I'm using:

    alf2lib -alf IO.alf  -lib .IO.lib -max_load -supply VCC -slew_derate 1.0 -def IO.prop -state
     

    I have project restrictions from the customer on the data, but I'll see what I can do.  Any other switches I can add to the alf2lib ?

    • 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