• 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 put Region/Fence out of core boundary?

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 3235
  • 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 put Region/Fence out of core boundary?

archive
archive over 17 years ago

How to put Region/Fence out of core boundary?

I want to put my Fence out of the core boundary, since I need to make a partition that includes IOs. I try to do this, but Encounter do not allow!

Need help.

BRs


Originally posted in cdnusers.org by eminemshow
  • Cancel
Parents
  • archive
    archive over 17 years ago

    Posted By BobD on 6/11/2008 6:15 AM
    Hello,

    When I've worked with designs like this in the past, I've found it best to define the floorplan such that the rows flood the entire die area. This can be achieved using Floorplan->Specify Floorplan->Specify By: Die/IO/Core Coordinates and settings all 3 boxes to be the size of the die area. If this approach is taken, then you should be able to create the fences as you desire, because the core area will effectively extend to where the IO cells are placed, and standard cells will not wander off into the IO area because there are fixed IO cells there obstructing the placeable area. I like this approach because it is more consistent with the long-standing First Encounter partitioning default whereby the partition/fence boundary nicely aligns with the standard cell rows vertically and m2 pitch horizontally.

    If you'd like to keep the floorplan defined as it is for some reason, you should be able to change the guide/region/fence snapping preference (Design->Preferences->Floorplan) to "Manufacturing Grid". This should allow you to create a fence outside of the core box. I tested this using 7.1.USR2 and see it working. Please post back if you don't see same- there may be a different approach needed in older software versions.

    Hope this helps,
    Bob


    Thank you for your constructive suggestion, bob.


    Originally posted in cdnusers.org by eminemshow
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    Posted By BobD on 6/11/2008 6:15 AM
    Hello,

    When I've worked with designs like this in the past, I've found it best to define the floorplan such that the rows flood the entire die area. This can be achieved using Floorplan->Specify Floorplan->Specify By: Die/IO/Core Coordinates and settings all 3 boxes to be the size of the die area. If this approach is taken, then you should be able to create the fences as you desire, because the core area will effectively extend to where the IO cells are placed, and standard cells will not wander off into the IO area because there are fixed IO cells there obstructing the placeable area. I like this approach because it is more consistent with the long-standing First Encounter partitioning default whereby the partition/fence boundary nicely aligns with the standard cell rows vertically and m2 pitch horizontally.

    If you'd like to keep the floorplan defined as it is for some reason, you should be able to change the guide/region/fence snapping preference (Design->Preferences->Floorplan) to "Manufacturing Grid". This should allow you to create a fence outside of the core box. I tested this using 7.1.USR2 and see it working. Please post back if you don't see same- there may be a different approach needed in older software versions.

    Hope this helps,
    Bob


    Thank you for your constructive suggestion, bob.


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