• 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. swapping cells with HVT or LVT cells

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 91
  • Views 20721
  • 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

swapping cells with HVT or LVT cells

spach
spach over 16 years ago

can any explain the flow in encounter to swap the cell with hvt or lvt cells?

design is time closed, to reduce the leakage power i need to swap the cells with hvt cell so that i should not get any timing violatios

if there are any violations i can swap with lvt cells to aviod violations

please explain me the flow in encounter to achieve that

regards

suresh 

 

  • Cancel
  • BobD
    BobD over 16 years ago

    The recommended way of optimizing leakage power concurrently with timing during the flow is as follows:

    setOptMode -leakagePowerEffort {-none | -low | -high}
    optDesign {-preCTS | -postCTS | -postRoute}

    However, if you've got a design that meets timing postRoute and you'd like to optimize just leakage power without disrupting timing:

    optLeakagePower -postRoute

    -or-

    setOptMode -leakagePowerEffort {-low | -high} -allowOnlyCellSwapping true
    optDesign -postRoute

    Hope this helps, Bob

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RahulRc
    RahulRc over 16 years ago

    Hi BobD,

     can we constrain encounter such that it will use  certain % of LVT cells?

    Thanks,

    Rahul

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • BobD
    BobD over 16 years ago

    Not that I'm aware of.  I believe the algorithm seeks to use as many HVT as possible while maintaining timing.  The level of aggressiveness can be controlled with setOptMode -leakagePowerEffort {low | high}.

    Is there a design rule or guideline that you're seeking to satisfy by controlling the percentage of LVT used?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • grasshopper
    grasshopper over 16 years ago

     Rahul,

     I would be curious to find out why you want to constrain the %LVT cells? There is no reason the tools and most respectable optmization engines should stop reclaiming power if it does not penalize your other design goals. This is a common practice that was used and it generally yields suboptimal results. The issue is that the end-goal of the user is a given power target and whether tool achieves the desired goal using fancy optmizations or any % of any VT cells is "generally" inconsequential. Some design flows and ASIC vendors have predicated such guidelines as rules of thumb but ultimately if your target power is 1W that is all your driving towards. Modern Low Power optimization techniques have made it such that there are many techniques beyond multiVT to address low power issues as well. I highly recommned the low power guide published by Si2 (specially since it is free ;) ). IBM has also published papers at CDNLive and at SNUG highlighting flow trade-offs / options when using multiple VT libraries. In a Cadence flow, the recommendation is to use concurrent multi-VT optimization in RTL Compiler during synthesis and the options described by BobD in Encounter during the P&R portion of the flow

     

    hope this helps,

    gh-

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidBD
    DavidBD over 14 years ago

     Hello,

    Can you provide a flow to run SVT -> HVT swapping when routing is freeze and only swap is enabled ?

     David

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 14 years ago

     Did you try the optLeakagePower flows already mentioned in this thread?

    • 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