Stats

  • Locked Locked
  • Replies 3
  • Subscribers 124
  • Views 18181
  • 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

missing terminals in extracted netlist

PirateKing2008

Hi

I get the following error when netlisting a calibre extracted view;

ERROR (OSSHNL-913): Netlisting failed because terminal 'casc' of instance 'Mirror' in cellview 't55atpnonprd/mirrorMvsFinger_tb/schematic'
does not exist in switch master 't55atpnonprd/mirrorMvsFinger/calibre_Ronly'. To continue netlisting, either set
the 'simCheckTermMismatchAction' to 'ignore', or set the
'simCheckTermMismatchAction' to 'warning' and 'nlAction' to 'ignore' for the
missing terminal.

This error repeats for all the pins.

So it won't netlist. But if I use the simCheckTermMismatchAction="ignore"  trick then it netlists but when you display the netlist the subckt will have no terminals against it!  This is probably why when I try to update pin order of symbol to match extracted view it wants to remove all the pins on the symbol! What's has happened to my terminal in the extracted view?

  • Hi Lance,

    This is a Cadence forum but the question really seems to be about the extracted view that Calibre (Mentor's tool) produces. Have you looked at the extracted view?  I guess that the terminals are really missing there, and hence they will not exist in any netlist produced from it.  You will most likely need to investigate the step that produces the extracted cellview, probably with folks who are familiar with Calibre (probably not on a Cadence forum).

    Regards,

    Lawrence.

  • Thanks Lawrence but it could be a CDF data.dm problem as other extractions done by the same layout person netlist in my testbench with their full pin list except extractions done for my blocks. I still haven't solved it though.

  • Hi Lance,

    These types of questions would be better handled by customer support as that way we can always take a look at your data via a webex and better advise you where the problem lies - we should be able to identify whether it is an issue with what Calibre is producing or something else in the data which is under user control.

    Regards,

    Andrew.

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.