• 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. db command to get power pin co-ordinates for a given Ma...

Stats

  • Locked Locked
  • Replies 11
  • Subscribers 93
  • Views 21449
  • 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

db command to get power pin co-ordinates for a given Macro

deeps
deeps over 16 years ago

 Hi,

    I am trying to get the power pin co-ordinate details for a given Macro, 

        Is there a way by using db commands we can get the exact co-ordinate details of the power pins that are present on the Macro.I am using dbGet command to get the co-ordinate details of the macro location.

 

thanks

deepak. 

  • Cancel
Parents
  • BobD
    BobD over 16 years ago

    Thanks JG,

    That's the way I'd do it too.  One additional command to be aware of is "dbTransform" that performs the translation you're referring to which converts the cell-level coords to chip-level.

    For example, if you have a cell that's instantated at 0, 884.82 with R270 orientation, you can translate each of the pgTerm rects to chip coordinates like this:

    encounter 26> dbGet selected.pt
    {0 884.82}
    encounter 27> dbGet selected.orient
    R270

    encounter 28>dbGet selected.cell.pgTerms.pins.allShapes.shapes.rect                                                                             
    {5.355 226.625 34.645 235} {5.355 226.625 34.645 235} {5.355 226.625 34.645 235} {5.355 226.625 34.645 235} {5.355 207.72 34.645 235} {5.355 207.72 34.645 235}

    encounter 29> foreach rect [dbGet selected.cell.pgTerms.pins.allShapes.shapes.rect] {puts "[dbTransform -localPt $rect -inst [dbGet selected]]"}
    {226.625 919.465} {235 890.175}
    {226.625 919.465} {235 890.175}
    {226.625 919.465} {235 890.175}
    {226.625 919.465} {235 890.175}
    {207.72 919.465} {235 890.175}
    {207.72 919.465} {235 890.175}

    Hope this helps,
    Bob

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • BobD
    BobD over 16 years ago

    Thanks JG,

    That's the way I'd do it too.  One additional command to be aware of is "dbTransform" that performs the translation you're referring to which converts the cell-level coords to chip-level.

    For example, if you have a cell that's instantated at 0, 884.82 with R270 orientation, you can translate each of the pgTerm rects to chip coordinates like this:

    encounter 26> dbGet selected.pt
    {0 884.82}
    encounter 27> dbGet selected.orient
    R270

    encounter 28>dbGet selected.cell.pgTerms.pins.allShapes.shapes.rect                                                                             
    {5.355 226.625 34.645 235} {5.355 226.625 34.645 235} {5.355 226.625 34.645 235} {5.355 226.625 34.645 235} {5.355 207.72 34.645 235} {5.355 207.72 34.645 235}

    encounter 29> foreach rect [dbGet selected.cell.pgTerms.pins.allShapes.shapes.rect] {puts "[dbTransform -localPt $rect -inst [dbGet selected]]"}
    {226.625 919.465} {235 890.175}
    {226.625 919.465} {235 890.175}
    {226.625 919.465} {235 890.175}
    {226.625 919.465} {235 890.175}
    {207.72 919.465} {235 890.175}
    {207.72 919.465} {235 890.175}

    Hope this helps,
    Bob

     

    • 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