• 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. Moving two instances together during placement

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 92
  • Views 15646
  • 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

Moving two instances together during placement

zamzam
zamzam over 10 years ago

Hi,

I have a placement question.

1) Is there a command/constraint that can be set for moving an instance and a desired unconnected spare cell together during placement?

2) Is there a command/constraint that can be set for moving an instance and a desired unconnected spare module (containing multiple spare cells) together during placement?

I have a workaround where I add some padding to the first instance and then move the desired spare modules/cells in that padding region after the initial placement. But it would make my life  alot easier if I can somehow use some constraints that allow them to move together as the design is placed.

Thanks,

Zaman.

  • Cancel
Parents
  • fitz
    fitz over 9 years ago

    ZamZam:

    Input tie-hi / tie-lo connected spare cells are by definition "floating", Placement efficiency demands spare cells migrate to the least offensive routing location, and ultimately the most useless ECO corner locations. If you are truly anticipating an ECO connect your first guesstimate spare inputs to the  real logic. that way it is already local and the extra ip pin cap is just noise.

    setPlaceMode -moduleAwareSpare might work with user created groups

    OR let the far more useful  placeSpareModule  evenly distribute spares.

    OR better still backfill with programmable gate-array-ish  DeCap cells.

    Shawn; Spare cells? Spare cells ? Who needs stinking Spare cells : )

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

    ZamZam:

    Input tie-hi / tie-lo connected spare cells are by definition "floating", Placement efficiency demands spare cells migrate to the least offensive routing location, and ultimately the most useless ECO corner locations. If you are truly anticipating an ECO connect your first guesstimate spare inputs to the  real logic. that way it is already local and the extra ip pin cap is just noise.

    setPlaceMode -moduleAwareSpare might work with user created groups

    OR let the far more useful  placeSpareModule  evenly distribute spares.

    OR better still backfill with programmable gate-array-ish  DeCap cells.

    Shawn; Spare cells? Spare cells ? Who needs stinking Spare cells : )

    • 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