• 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 92
  • Views 14511
  • 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
  • Yemelya
    Yemelya over 14 years ago
    Oh! I have found it: dbTermLoc
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • turtlej9
    turtlej9 over 14 years ago

    Hi Boris,

    We've got a procedure we use that incorporates the dbTermLoc that you've already identified. After sourcing this proc, you'd just have to type "queryInstPin_loc myInstance/pin"


    proc queryInstPin_loc { { instPin "" } } {
      loguse procedures queryInstPin_loc
    # queryInstPin_loc: returns the location of the <inst>/<pin>
      if { $instPin == "" } {
        puts ""
        puts "   Usage:  queryInstPin_loc  <inst>/<pin>"
        puts ""
        puts "      returns the location of pin <inst>/<pin>"
        puts ""
      } else {
        set scale [pdsDBU2Micron 1]
        set numbFields [regsub -all "/" $instPin " " inst_pin]
        set pin [lindex $inst_pin $numbFields]
        regsub -all {[[$^?+*()|\\]} $pin {\\&} escPin
        regsub -all "/${escPin}$" $instPin "" inst
        set instPtr [dbGetInstByName $inst]
        if { $instPtr == "0x0" } {
          puts "Didn't find inst $inst"
        } else {
          set termPGPtr "0x0"
          set termPtr [dbGetTermByName $instPtr $pin]
          if { $termPtr == "0x0" } {
            set termPGPtr [dbGetPGTermByName $instPtr $pin]
          }
          if { $termPtr == "0x0"  &&  $termPGPtr == "0x0" } {
            puts "Didn't find signal or power pin named $pin on inst $inst"
          } else {
            if { $termPGPtr == "0x0" } {
              set pinLoc [dbTermLoc $termPtr]
              set dbXY  [dbTermLoc $termPtr]
             } else {
              set pinLoc [dbTermLoc $termPGPtr]
              set dbXY  [dbTermLoc $termPGPtr]
            }
            set dbX [lindex $dbXY 0]
            set dbY [lindex $dbXY 1]
            set x [expr $dbX * $scale]
            set y [expr $dbY * $scale]
            return "$x $y"
            return $pinLoc
          }
        }
      }
    }

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Yemelya
    Yemelya over 14 years ago

    Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • PradyK
    PradyK over 14 years ago

    Hi,

    Can I get Power ground pins metal gemoetries specified in lef using any command?

    I want to put Metal1 stripe over Metal1 Power ground Pins over each Instance of desig.

    Not able to get any command to get the geometries . 

    Appricate your help. 

    Thanks,

    Pradeep

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • 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
  • PradyK
    PradyK over 14 years ago

    Perfact Bob, was looking for exactly same soulution you mentioned. 

    Thanks a bunch. 

    Regards,

    Pradeep

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 14 years ago

     Hi Pradeep,

    Just wanted to chime in - sounds like you're trying to route the std cell pwr/gnd rails? Any reason you don't want to use sroute for that? Just curious, and thought I might be able to save you some work if that's what you were trying to do.

    - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • PradyK
    PradyK over 14 years ago

     Hi Kari,

    Partially yes, I am doing it to do connection of power ground pin to my global Power mesh , but instead of using sroute I am doing Power grid aware placement of few cells such that they come exactly under power grid and and the power pins wil get allign to middle of power mesh stripes to avoid any IR issues on these cells. These are Low power cells which has dual power rail. 

     Hope this will clearify my implementation requirements. 

    Thanks,

    Pradeep

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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