• 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 place an instance regardless of its SITE definit...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 91
  • Views 14487
  • 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 place an instance regardless of its SITE definition

jgentry
jgentry over 15 years ago

All,

  I have some instances that need to be rotated 90-degrees from their "normal" orientation.  However, when I try to placeInstance, dbPlaceInst and even set R90 from the attributes menu, it always tells me that it is reseting to R0 because the desired orient, R90, doesn't match the CORE site definition (the SYMMETRY line in the LEF is 'X Y R90' and, thus, isn't preventing the rotation itself).  Is there a way around this other than to create some DEF with the desired inst locations and R90 orients (which works by the way)?  

Thanks,
JG

  • Cancel
Parents
  • jgentry
    jgentry over 15 years ago

     Kari,

      Yes, it is a stdcell.  It's a filler cell actually.  We have sections in our chip where we put in a clean supply grid but it has to route orthogonal to the normal core power grid in order to provide adequate shielding for reference clock routes.  I was hoping there was some switch somewhere to tell the *place* commands to just do it (I was hopeful that dbPlaceInst was the command that would ignore any site definitions).

     

    Thanks,
    JG

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • jgentry
    jgentry over 15 years ago

     Kari,

      Yes, it is a stdcell.  It's a filler cell actually.  We have sections in our chip where we put in a clean supply grid but it has to route orthogonal to the normal core power grid in order to provide adequate shielding for reference clock routes.  I was hoping there was some switch somewhere to tell the *place* commands to just do it (I was hopeful that dbPlaceInst was the command that would ignore any site definitions).

     

    Thanks,
    JG

    • 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