• 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. connections to abstract not verified by Assura LVS - what...

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 128
  • Views 5071
  • 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

connections to abstract not verified by Assura LVS - what's wrong?

TrevorB
TrevorB over 15 years ago

Hi,

We are using an IP block from our foundry in our chip.  The IP block is located below the top level of the hierarchy.  And, the IP block is presented as an empty layout block, containing only pins and boundary shapes.

Currently, as we run Assura LVS with the default options, our outside connections to the IP block's pins are not verified. We can swap connections - even leave connections open - but LVS does not complain!  That's no good...

What do I need to do differently to make Assura LVS verify our connections to the IP block's pins?

Thanks!

Trevor

  • Cancel
Parents
  • TrevorB
    TrevorB over 15 years ago

    I spoke with our foundry's support team, and I experimented some more.  I finally got it working.  Here's what I learned:

    1. The black box's schematic cannot be empty.  It must contain at least one device (cds_thru, presistor, some transistor, etc.).  If it does not, Assura LVS will prune it from the netlist, despite the blackBoxCell statement.  We also included the pins.
    2. Any global signals that are pinned out on the layout must also be pinned out on the black box's symbol.  If they are not, then them must be tied to some non-trivial device (cds_thru, presistor, some transistor, etc.) inside the black box's schematic; otherwise, they will not appear on the definition of the black box's pin boundary.
    3. The dummy devices used inside the black box's schematic are of no consequence, since they will be discared as the ignored guts of a "black box".
    4. I ultimately used "blackBoxCell" instead of "blackBox", although I imagine "blackBox" could be used somehow too...

    As an example, here are the guts of our dummy schematic for the black box:

    Dummy Schematic for Black Box block

    Thanks again for the help, Quek!

    HTH,

    Trevor

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • TrevorB
    TrevorB over 15 years ago

    I spoke with our foundry's support team, and I experimented some more.  I finally got it working.  Here's what I learned:

    1. The black box's schematic cannot be empty.  It must contain at least one device (cds_thru, presistor, some transistor, etc.).  If it does not, Assura LVS will prune it from the netlist, despite the blackBoxCell statement.  We also included the pins.
    2. Any global signals that are pinned out on the layout must also be pinned out on the black box's symbol.  If they are not, then them must be tied to some non-trivial device (cds_thru, presistor, some transistor, etc.) inside the black box's schematic; otherwise, they will not appear on the definition of the black box's pin boundary.
    3. The dummy devices used inside the black box's schematic are of no consequence, since they will be discared as the ignored guts of a "black box".
    4. I ultimately used "blackBoxCell" instead of "blackBox", although I imagine "blackBox" could be used somehow too...

    As an example, here are the guts of our dummy schematic for the black box:

    Dummy Schematic for Black Box block

    Thanks again for the help, Quek!

    HTH,

    Trevor

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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