• 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. Will "OptDesign" respect the fences ?

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 91
  • Views 734
  • 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

Will "OptDesign" respect the fences ?

patrice06
patrice06 over 14 years ago

Hello,

In a 0.18um design, I have modules which should powered by two seperate power supplies (ex: module 1 by VDD1, module 2 by VDD2). In order to keep the SocEncounter implementation simple, I am trying to keep away of hierarchical partition or  CPF based flow.  I am using fences and globalNetConnect to instruct Sroute to make the right connection to each area.  So far, so good.  But I have not  run any optimization yet.

My question is:  Will the optimization process possibly insert cells without respecting the fences ?  (ie: buffer added for the module 1 netlist but physically ending up in the "module 2 VDD2  fence") Which I cannot afford.   Other possible issues with this methodology ?  Is it recommend to move to a CPF flow ?

Thanks a lot for your inputs.

Best regards

Patrice

  • Cancel
  • BobD
    BobD over 14 years ago

    There is a "setOptMode -honorFence true" option so be sure to assert that. Let us know how it goes!

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

    Thanks Bob for your quick and clear answer.

    That is working fine.

    And when the constraint cannot be met, the checkPlace clearly reports  a "fence placement violation" .

    • 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