• 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. Necessary to cover pin in hierarchical layout?

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 9398
  • 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

Necessary to cover pin in hierarchical layout?

kenc184
kenc184 over 3 years ago

Why is it necessary to touch the pin in a sub-block in VXL for "show incomplete nets" to recognize the connection?  The tool recognizes the net as being connected to the pin, so why isn't simply connecting to the net rather than the pin good enough?  Below is an example, the circuitry to the left of the purple prBoundary line is a sub cell, the signal "blank" is connected in M1 to an M1 path in the sub-block but does not touch the pin. The connection is not recognized as complete.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    This is because the extract depth is set to 0, so it only extracts the connectivity in top level shapes, and so the only lower-level shapes it considers are pins. Usually, in well-formed layout this is sufficient and is more efficient as a result. You can however increase the extract depth to more than 0 if needed to address this.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • kenc184
    kenc184 over 3 years ago in reply to Andrew Beckett

    Given this, how would I assign two pins (e.g.) to one net on different layers?  I often have a cell which is used in multiple locations. It would be nice to be able to assign a pin to (e.g.) M1 and M2 in two different locations on the same net without it being a global.  So far, i haven't found a property on the pin to allow this.

    • 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