Stats

  • Locked Locked
  • Replies 17
  • Subscribers 64
  • Views 21759
  • 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_AMS for .lib generation.

anandmohan

Hi,

I'm having Liberate_AMS for characterization of AMS blocks. Can I use the same for the characterization of a std cell library ? 

The main difficulty involved is in generating the input stimulus files which need to be given in the form of tables in Liberate_AMS whereas it can be included with the attribute -vector inside the template file (in case of Liberate).

Still I managed to manually create those table files for ** number of cells. After that I included those tables using the define_table command in the template file.  I had to give ** define table commands (1 for each cell) . But I'm getting an error regarding "delay_template" not defined.

After all , I wanted to know, if characterising multiple cells (by including multiple input stimulus files) is possible in Liberate_AMS ?  Or is it a futile attempt trying to do that ?

Is there an inherent limitation on the number of cells that can be characterized using Liberate_AMS in a single run ?  (other than the brute force way of characterising 1 cell at a time and merging all of them- as I have huge number of cells - typically the number of cells usually present in a std cell library).

Parents

  • Liberate_AMS does one cell characterisation in each run. It is for AMS/Analog block or large IO block characterisation. 

    For standard cell characterisation, Liberate is the right choice, which can automatically generate all valid arcs after pre-characterisation analysis by the tool using InsideView technology.  

Reply

  • Liberate_AMS does one cell characterisation in each run. It is for AMS/Analog block or large IO block characterisation. 

    For standard cell characterisation, Liberate is the right choice, which can automatically generate all valid arcs after pre-characterisation analysis by the tool using InsideView technology.  

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.