Stats

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

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

Parents
  • Quek

    Hi Trevor

    A cellname can be short (simply the cellname) or long (with view and lib info). Please see the section on "Representing Cell and Device Names" in the Assura Developer's Guide. Actually the correct cmd is :

    blackBox("cellName viewName libName")

    and not:

    ?blackBox ("cellName viewName libName")

    textPriOnly and textLevel need not be used if they are not necessary. I will think more about your question and update you again. Would you please uploaded your log, cls, csm and erc files? Total of 4 files.

    Thanks
    Quek

Reply
  • Quek

    Hi Trevor

    A cellname can be short (simply the cellname) or long (with view and lib info). Please see the section on "Representing Cell and Device Names" in the Assura Developer's Guide. Actually the correct cmd is :

    blackBox("cellName viewName libName")

    and not:

    ?blackBox ("cellName viewName libName")

    textPriOnly and textLevel need not be used if they are not necessary. I will think more about your question and update you again. Would you please uploaded your log, cls, csm and erc files? Total of 4 files.

    Thanks
    Quek

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.