• 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. Custom IC Design
  3. Pin searching in the layout top

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 126
  • Views 16348
  • 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 searching in the layout top

mfyee
mfyee over 13 years ago

Hi there,

 I am planning to find the pin in my top layer using Skill in IC5141 following is my simple skill

 pinLayerList = list (list (MEAL1 "PIN") (METAL5 "PIN"))

and i am using the following to capture my pin

 foreach (pinLay pinLayerList

allPins = appened (allPins leSearchHierarchy(cvId cvId~> bBox 0 "rectangle" list(list("layer" "==" pinLay))))

)

However instead of return Metal1 and Metal5 pins it returns all my other drawinig layer in the top, please kindly point out what is wrong with my scripts. Thank you very much.

 Regards,

 

  • Cancel
  • Quek
    Quek over 13 years ago

    Hi mfyee

    You had not specified to only search for pins in leSearchHierarchy. That's why you got all the shapes. The following cmd should have been used:

    leSearchHierarchy(cvId cvId~> bBox 0 "pin" list(list("layer" "==" pinLay)))

    If it is just top level pins, you can also use this:

    procedure( CCSfindPins()
       prog( (cv pinLayerList allPins targetPins)
          cv=geGetWindowCellView()
          pinLayerList=list( '("Metal1" "PIN") '("Metal5" "PIN") )
          allPins=list()
          foreach( pinLay pinLayerList
             targetPins=setof(x cv~>shapes x~>pin && x~>lpp==pinLay)
             allPins=append(allPins targetPins)
          ) ;foreach
          return(allPins)
       ) ;prog
    ) ;procedure

    I prefer to use "prog+return" instead of just using "let" to return the last value. Just a personal preference. : )

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mfyee
    mfyee over 13 years ago

    Hi Quek,

    Great to hear from you again, its been a long time. i have tried to use "pin" as your first suggestion but the problem is, it returns nothing but nil. i have also check on the user guide itself where i don't see "pin" as one of the option in leSearchHierarchy function. i will try on your second suggestion, although i hope to get the 'leSearchHierarchy' done as this scripts might also need to search the pin down to more hierarchy.

     Thank you for your suggestion very much.

     Best regards,

    MF

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 13 years ago

    Hi MF

    "pin" is one of the object types listed in IC61x layout SKILL reference manual. It is not listed in IC51 layout SKILL manual.

    Best regards
    Quek

    • Noname.gif
    • View
    • Hide
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mfyee
    mfyee over 13 years ago

    Dear Quek,

     I am not sure if this is applicable in IC5, since i need the code to deal with the old library where id cdb format and it is not possible to migrate to IC6. I have tried your script using Prog but its also grep all the elements on the top instead of just pin. would this be i specified the datatype wrongly?

    Thanks for all the help.

     Best regards,
    MF

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 13 years ago

    Hi MF

    I just tested the script on IC5141-500-6-150. It seems to be working fine. It returns only the pinIDs. 

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mfyee
    mfyee over 13 years ago

    Dear Quek,

    I have found the problem on the scripts, i have tried running the leSearcHierarchy function as before by defining the correct layer e.g. "METAL5" "pin" it returns only the pin ID but the problem is once the particular layer is not found or group together with other layers like

     pinLayerList = list (list("M1" "pin") list("METAL5" "pin")

    where M1 is not exist in the technology(but i need this to be the universal program which use on different technology). in this scenario the leSearchHierarchy will grep all the metal layer on the top, but it is fine when i define as below,

     pinLayerList = list (list("METAL1" "pin") list("METAL5" "pin")

    I wonder why is this goes wrong, should leSearchHierarchy only return the value that exist?

     Many thanks.

     Regards,MF

     

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 13 years ago

    Hi MF

    I can reproduce your observations. It seems that leSearchHierarchy will return all pins instead of nil when a non-existent LPP is used. How about adding a check for the LPP? E.g.

    procedure( CCSfindPins()
       prog( (cv tf pinLayerList allPins)
          cv=geGetWindowCellView()
          tf=techGetTechFile(ddGetObj(cv~>libName))
          pinLayerList = list( '("METAL1" "PIN") '("METAL5" "PIN") )
          allPins=list()
          foreach (pinLay pinLayerList
             if( techGetLP(tf pinLay) then
                allPins = append(allPins leSearchHierarchy(cvId cvId~>bBox 0 "pin" list(list("layer" "==" pinLay))))
             else
                printf("LPP %L not found in techfile\n" pinLay)
             ) ;if
         ) ;foreach
          return(allPins)
       ) ;prog
    ) ;procedure


    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mfyee
    mfyee over 13 years ago

    Dear Quek,

    Thanks for giving me the instruction to get the metal layer that available on the Tech file only, and now it works great. Thanks so much and it is always please to work with you all the while.

     Best regards, MF

    • 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