Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 12679
  • 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

Terminal is inherited in switch master XXX and not inherited in place master YYY

jjwikner

Hello,

I get the following error while trying to simulate an extracted view generated by PVS-Quantus. PVS19.1 and Quantus 20.1.
Passes LVS, etc. Running with extracted C-decoupled settings.

ERROR (OSSHNL-930): Netlisting failed because of an error in the design. Terminal 'XXX' is inherited
in switch master  'YYY/av_extracted_X' and not inherited in place master 'YYY/symbol

I understand the concept of inherited terminals, but not why the extractor assumes it is inherited.

Where should I start debugging? The extview.rul? PVS flow? Quantus? Or the ADE-L itself?

Parents

  • The pins from extracted views are copied across from the pins on the layout view, so check pin (terminal) XXX on the layout view. If this has a net expression on it, then you either need to remove the net expression from the layout pin, or add the net expression onto the symbol pin. As the message says, it needs the terminals to be consistent between the views - if the terminal exists in both views, then they must both have net expressions or neither have net expressions.

    Once you've fixed the layout view, when you generate the extracted view again, that should mean that the terminals on the extracted view are OK, and hence netlisting shouldn't give this error.

    You didn't mention which IC sub-version you're using; this error message was introduced because previously when this situation occurred, the wrong netlist would be created and this could slip through without being noticed. I don't remember off the top of my head when the error message was introduced, but it was in the last couple of years (I think).

    Regrds,

    Andrew.

  • in reply to Andrew Beckett

    Thanks Andrew,

    6.18 was the version, and the error was indeed the connectivity of that node. Pretty obvious when knowing what to look for I presume... 

    Uploading a properties window for future reference. The Net Expression fields (marked) should be empty (in my case). 

Reply
  • in reply to Andrew Beckett

    Thanks Andrew,

    6.18 was the version, and the error was indeed the connectivity of that node. Pretty obvious when knowing what to look for I presume... 

    Uploading a properties window for future reference. The Net Expression fields (marked) should be empty (in my case). 

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.