• 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. Inherited connection check

Stats

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

Inherited connection check

DaveZhang
DaveZhang over 4 years ago

Hi all,

  I want to check the terminal connection for some device, such as whether the BULK for PMOS is connected to VDD, by using schematic rule check engine. But I have no idea to describe the inherited connection from the top cell. Does anyone know how to do that? Any reply would be appreciated!

Thanks,

Dave

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    I'm not really sure how you are expecting to use the "schematic rule check engine" to do this?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    I'm not really sure how you are expecting to use the "schematic rule check engine" to do this?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • DaveZhang
    DaveZhang over 4 years ago in reply to Andrew Beckett

    Hi Andrew,

     The 'engine' is schRegisterCheckRule.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to DaveZhang

    Given that the checker is run on an individual cellView, I don't think you reliably would have the hierarchical context of the block. Even if you used the "de" (design editor) hierarchical path to where the editor is open, you'd only be checking the resolution for the current occurrence - there may be other occurrences where the PMOS Bulk nodes are resolved to something other than VDD - so I'm not sure this is the right way of solving your problem.

    Perhaps you should contact customer support to discuss the bigger problem you're trying to resolve?

    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