• 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. Getting the list of metal layers connected to a selected...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 18179
  • 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

Getting the list of metal layers connected to a selected metal layer

Mallikarjun032
Mallikarjun032 over 6 years ago

Hi,

I have a layout having only ("M1" "drawing") metal layers, and for a metal layer given as input, I need to get the list all the metal layers which are connected and forming a single net with it.

I have checked using the 'dbGetOverlaps()' function, but this is not giving me the desired output, because this function returns the metal layers whose 'bBox's overlap with the 'bBox' of the selected metal layer. Although the 'bBox's overlap, they may not be connected.

Please let me know if there's a way to get the list of all the metal layers which are connected to a selected metal layer.

Thanks,
Mallikarjun

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    Are you using Virtuoso Layout Suite XL? Does this need to involve connections to other layers throughout the hierarchy?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Mallikarjun032
    Mallikarjun032 over 6 years ago in reply to Andrew Beckett

    Hi Andrew,

    The layout I am working on, has only one hierarchy and it has only ("M1" "drawing") layers in it.
    Yeah, I am using Virtuoso Layout Suite XL, but I have to get this done through a SKILL code.

    Thanks,
    Mallikarjun

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to Mallikarjun032

    The reason I was asking was because then the shapes have connectivity, and so you can then see if they are on the same net. The dbGetOverlaps could work, but that would only find overlapping shapes - you could then look at the ~>net attribute on each shape to see if they are on the same net as the starting point.

    Or you could use the "mark net" functionality (leMarkNet is the non-interactive function to do this) and then use leSaveMarkNet to save the shapes to a temporary cellView (which was opened in "w" mode initially to ensure it's blank) and then inspect the shapes you end up with the temporary cellView to find out the layers used.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Mallikarjun032
    Mallikarjun032 over 6 years ago in reply to Andrew Beckett

    Hi Andrew, 

    Thanks for your suggestions.

    I took the help of leMarkNet() and leSaveMarkNet() functions to get the list of all connected metal layers. I couldn't get much help from the '~>net' attribute for metal layers, because if the net name is 'nil', then the '~>net' attribute will be empty.

    Thanks,
    Mallikarjun

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to Mallikarjun032

    Rather surprising that the net would be nil if you're using VLS XL, but anyway, you have a solution...

    Note, I wasn't talking about using ~>net with the results of leSaveMarkNet because that wouldn't have connectivity - I was talking about using it on the original shapes - but either way, you have a way forward.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Mallikarjun032
    Mallikarjun032 over 6 years ago in reply to Andrew Beckett

    Hi Andrew,

    I am using VLS XL, and I used the '~>net' attribute on the original layout. Also, the original layout does not have net names assigned to the ("M1" "drawing") metal layers; this may be the reason why the '~>net' attribute is 'nil'.

    Thanks,
    Mallikarjun

    • 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