• 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. Re-characterizing a tap-less cell library (Cadence Liberate...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 15345
  • 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

Re-characterizing a tap-less cell library (Cadence Liberate)

anurans
anurans over 6 years ago

Hi All,

I want to re-characterize the existing library to a lower supply voltage. I have been provided the extracted (with parasitics) netlist (.cir) of this tap-less cell library by the vendor. 

> I generated the cell template file from existing .lib in .tcl format which contains cell definitions, delay/power templates with slew/load indices.

> The provided netlist however contains the VBN/VBP contact ports (along with its parasitics) which are not available in generated template (I assume the earlier characterization was done by connecting well contacts to the supply rails accordingly / or atleast that's what I'd do if I create a lib for my custom made cells).

> In this condition, re-characterization is not possible as Liberate does not see VBN/VBP in cell definitions of the template. Is it possible to indicate "Liberate" that those well contacts should be connected globally to respective supply rails during the characterization ?

> When doing the characterization, are those slew values for the given loads automatically re-calculated for the new supply voltage ?

Thanks

Anuradha

  • Cancel
Parents
  • Guangjun Cao
    Guangjun Cao over 6 years ago

    1. if you want the new library to have exact the same arcs, use -verbose in the write_template command, and -user_arcs_only in char_library command;

    2. PG pins are not written out during write_template. users have to use set_vdd/gnd or set_pin_vdd/gnd to declare/define the PG pins and association of pin/PG-pins;

    3. if your reference library has normalized waveform, you can write out this and re-use it for re-characterisation. slew/load index tables are not necessarily related to supply for a give corner. If you want the tool to auto-calculate the index table, you need to specify the min/max_transition of your design and minimum input capacitance, which can all be corner dependent as your cells' behavior. -auto_index is also needed. you can also use -driver_waveform to include the normallized waveform in the generated library. Some STA tools use this information, which can improve the correlation between Spice simulation and STA analysis results.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Reply
  • Guangjun Cao
    Guangjun Cao over 6 years ago

    1. if you want the new library to have exact the same arcs, use -verbose in the write_template command, and -user_arcs_only in char_library command;

    2. PG pins are not written out during write_template. users have to use set_vdd/gnd or set_pin_vdd/gnd to declare/define the PG pins and association of pin/PG-pins;

    3. if your reference library has normalized waveform, you can write out this and re-use it for re-characterisation. slew/load index tables are not necessarily related to supply for a give corner. If you want the tool to auto-calculate the index table, you need to specify the min/max_transition of your design and minimum input capacitance, which can all be corner dependent as your cells' behavior. -auto_index is also needed. you can also use -driver_waveform to include the normallized waveform in the generated library. Some STA tools use this information, which can improve the correlation between Spice simulation and STA analysis results.

    • Cancel
    • Vote Up +1 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