Stats

  • Locked Locked
  • Replies 4
  • Subscribers 90
  • Views 14064
  • 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

Library preparation for the MultiVT libraries

archive

Hi,

I wanted to work on the "MultiVT" libraries in my design, can any one suggest me how to go about this ?

1. In normal flow we will just import lib files, is it same in case multvt libs? if yes then how to differentiate?

2. how to diffrentiate HVT & RVT cells in the design (ie how to calculate the % of HVT & RVT cells)

3. what will be PD Flow(physical design steps)

Please suggest.

Thanks & Regards,
kulprashant


Originally posted in cdnusers.org by kulprashant05
Parents

  • Hi Kulprashant,

    You really don't have to do anything different. Just load in the .lib of both libraries. The cells should have different names, like INV and INVTH, or INV_HVT and INV_RVT, or something similar. I don't know of an automatic way to get the % of HVT vs RVT, but it should be easy to write a script to parse the netlist or a summary report file. As for the flow, it will be pretty much the same, but check the docs for setOptMode -leakagePowerEffort and set it to what you think is best for your design goals.

    Hope that helps,

    - Kari


    Originally posted in cdnusers.org by Kari
Reply

  • Hi Kulprashant,

    You really don't have to do anything different. Just load in the .lib of both libraries. The cells should have different names, like INV and INVTH, or INV_HVT and INV_RVT, or something similar. I don't know of an automatic way to get the % of HVT vs RVT, but it should be easy to write a script to parse the netlist or a summary report file. As for the flow, it will be pretty much the same, but check the docs for setOptMode -leakagePowerEffort and set it to what you think is best for your design goals.

    Hope that helps,

    - Kari


    Originally posted in cdnusers.org by Kari
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.