• 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 SKILL
  3. Check for terminals display property

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 15583
  • 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

Check for terminals display property

HDar
HDar over 8 years ago

Hi,

I am writing a skill script to check if all the terminals in a symbol has their display property turned on or not. And return all the terminals for which the display property is off. 

What I realized, there are two different type of terminals that exist based on number of display property that exist.

For the terminal on left (pin A) there exist 4 options for Display property. Whereas for the one on the right side, there are only 2.

Thanks,

Himanshu 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Himanshu,

    This is a little bit complicated. Normally when symbol pins are created, they have an associated label object. If you select the pin shape itself, you'll see this by looking at car(geGetSelSet())~>children - and if you look at car(geGetSelSet())~>children~>objType you'll see they're labels. Label objects can then have the ~>isVisible attribute set to t or nil to control whether they are displayed - this is what you see in the second case.

    If the label wasn't created (or was subsequently deleted), the first form appears. If the display is initially off, there may not even be an object to display the name or value, but what happens when  you first change the display to value, name or both, it creates a textDisplay object and attaches it to the pin figure (so car(geGetSelSet())~>children~>objType would show a textDisplay object). These textDisplay objects have a ~>isVisible attribute, but also a ~>isNameVisible and ~>isValueVisible attribute which allow you to control the name, value, both parts. Once the textDisplay is created, if you set the display off again, it keeps the textDisplay (it doesn't delete it).

    So, to control this (if you want to fix it) you'd have to see if there's an existing attached label or textDisplay (labels are fixed, textDisplays are linked to a database attribute) and then control the display attributes appropriately. If there's no label or textDisplay you'd need to create one and attach it (by setting the ~>parent attribute of the new label or textDisplay). Note that when you create a textDisplay with dbCreateTextDisplay you have to say which object it is owned and associated with (this would be the terminal object, not the pin or the pin figure) and the name of the parameter that is displayed (which would be "name" in this case as it's the name of the terminal you want to display).

    Hope that's not too complicated!

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • HDar
    HDar over 8 years ago
    Hi Andrew,

    Thanks for all the explanation. And apologies for responding late.

    I tried to query the terminal's children properties (by doing this : geGetSelSet()~>children~>??). Down this hierarchy there is "isVisible" attribute, from which I can track if the display is "on" or not.

    However, I was wondering, is there a way to select an object (say a terminal itself) without opening the symbol gui? I am to test thousands of standard cells for this property check. Opening and closing each schematic would be a pain and clearly not a good idea. I tried using geSelectPoint, but it doesn't have an option as to which symbol to select the object from. I was hoping a command that would take the db pointer of the symbol as input.

    Thanks,
    Himanshu
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Himanshu,

    Assuming you've opened the cellView with cv=dbOpenCellViewByType(...) then:

    foreach(term cv~>terminals
      printf("Terminal: %s\n" term~>name)
      foreach(pin term~>pins
        foreach(pinFig pin~>figs
          if(pinFig~>children then
            foreach(child pinFig~>children
              case(child~>objType
                ("label"
                  printf("Attached object is a label - do label-specific changes here\n")
                )
                ("textDisplay"
                  printf("Attached object is a textDisplay - do textDisplay-specific changes here\n")
                )
              )
           )
           else
             printf("No attached label/textDisplay\n")
           )
         )
       )
    )

    This is a bit of thrown together code just to iterate over all the pin figures and look at their attached objects - but hopefully this gives a clue where to start.

    Regards,

    Andrew.

    • 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