• 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. How to optimize level shifter and isolation instances marked...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 92
  • Views 14328
  • 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

How to optimize level shifter and isolation instances marked dont touch in Encounter

fieldy
fieldy over 11 years ago

Hi All,

 

I am implementing a Low-power design with Power switches and Isolation cells. I have a CPF file that I commit and I can see that isolation cells and level shifters are inserted into the design correctly as I intended.

However, whenever I run optDesign, whether it be preCTS, postCTS or postRoute, Encounter seem to mark level shifters and isolation instances as don't touch instances and does not optimize them. As a result, the drive strength of the isolation instances are too small. I know that Encounter doesn't optimize clock nets but there is a ckECO option to take care of clock optimization. Is there a way to make Encounter optimize the level shifter and isolation instances and/or remove the dont touch marking on these instances?

 Below are the messages I get in the log file when I run optDesign :

*info: Marking 12 level shifter instances dont touch

*info: Marking 64 isolation instances dont touch 

 

I've tried to use set_dont_touch and set_interactive_constraint_mode options to override this but haven't succeeded so far. Has anybody gotten the same problem and does anybody know how to solve this?

 

Thanks

Saekyu 

  • Cancel
Parents
  • fitz
    fitz over 11 years ago

    setOptMode  -resizeShifterAndIsoInsts {true | false}
    Controls whether timing optimization resizes shifters and isolation instances. In default mode (false), shifters and isolations are considered "don't-touch" instances and are not changed during timing optimization.
    When this parameter is set to true, the shifters and isolation cells are resized for timing optimization by using optDesign.
    Note: When this parameter is set to true, all the shifters and isolation cells can be resized even if they are marked as dont_touch.
    Default: false

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • fitz
    fitz over 11 years ago

    setOptMode  -resizeShifterAndIsoInsts {true | false}
    Controls whether timing optimization resizes shifters and isolation instances. In default mode (false), shifters and isolations are considered "don't-touch" instances and are not changed during timing optimization.
    When this parameter is set to true, the shifters and isolation cells are resized for timing optimization by using optDesign.
    Note: When this parameter is set to true, all the shifters and isolation cells can be resized even if they are marked as dont_touch.
    Default: false

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