• 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. pin location

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 93
  • Views 15168
  • 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

pin location

Yemelya
Yemelya over 14 years ago
Hello,

How can I find location of the pin/pins for particular instance? For example I can find the instance itself by dbInstLoc, but I am not sure how to locate pins of this cell.

Thanks!
-Boris

 

  • Cancel
Parents
  • BobD
    BobD over 14 years ago

    Although signal pins are made up of multiple geometries they are additionally stored in the db as "dbGet top.insts.instTerms.pt". When we want to get just a rough idea of where the pins are for troubleshooting distances between pins this simple xy is useful.

    However, if you want to access the detailed geometries that make up a pin - whether it's a signal pin or a pg pin - the key is querying the geometries off the cell master and then transforming it to the location the instance resides at with dbTransform.

    Have a look at this solution which can be discovered on support.cadence.com with a search for "pg pin coordinates":
    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11723882

    The key is to query the geometries off the cell master then use dbTransform to simplify translation of those coordinates to the chip-level.

    Here is a script to do just that :

    set inst [dbGetInstByName i0]

    foreach pgCellTerm [dbGet $inst.pgCellTerms] {

      puts "[dbGet $pgCellTerm.name]"

      foreach pin [dbGet $pgCellTerm.pins] {

        puts "[dbGet $pin.allShapes.layer.name] [dbTransform -localPt [dbGet $pin.allShapes.shapes.rect] -inst $inst]"

      }

    }

    Hope this helps,
    Bob

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

    Although signal pins are made up of multiple geometries they are additionally stored in the db as "dbGet top.insts.instTerms.pt". When we want to get just a rough idea of where the pins are for troubleshooting distances between pins this simple xy is useful.

    However, if you want to access the detailed geometries that make up a pin - whether it's a signal pin or a pg pin - the key is querying the geometries off the cell master and then transforming it to the location the instance resides at with dbTransform.

    Have a look at this solution which can be discovered on support.cadence.com with a search for "pg pin coordinates":
    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11723882

    The key is to query the geometries off the cell master then use dbTransform to simplify translation of those coordinates to the chip-level.

    Here is a script to do just that :

    set inst [dbGetInstByName i0]

    foreach pgCellTerm [dbGet $inst.pgCellTerms] {

      puts "[dbGet $pgCellTerm.name]"

      foreach pin [dbGet $pgCellTerm.pins] {

        puts "[dbGet $pin.allShapes.layer.name] [dbTransform -localPt [dbGet $pin.allShapes.shapes.rect] -inst $inst]"

      }

    }

    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