Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 1263
  • 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

QRC dbCreateNet/dbCreateTerm warnings?

drdanmc

When trying to do a selected nets RC extraction using Quantus QRC, PVS for the input, and extracted view for the output, I get some complains in the spice2db output:

*WARNING* (DB-270000): dbCreateNet: Input name (or member): MYOUT(7:0) has improper paren syntax
*WARNING* (DB-270357): dbCreateTerm: invalid net specified

but when I generate a spectre netlist, things look ok.  Should I be worried about these at all?  I don't see the () in any of the files other than the log.  It seems to be <> everywhere else (netlist, cross ref files, etc)

Thanks

-Dan

Parents
  • Andrew Beckett

    Hi Dan,

    I can't find any records of similar messages. In general net names in extracted views will have () rather than <> (except the terminal names), mostly because the extracted view has a "flat" namespace compared with the original hierarchical database that the LVS was performed on. However, I wouldn't expect a bus  (only scalar nets) to appear. So something is a bit odd.

    Please contact customer support - I think we should look at this data to understand what is going on. I don't know whether it is benign or a cause for concern.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Hi Dan,

    I can't find any records of similar messages. In general net names in extracted views will have () rather than <> (except the terminal names), mostly because the extracted view has a "flat" namespace compared with the original hierarchical database that the LVS was performed on. However, I wouldn't expect a bus  (only scalar nets) to appear. So something is a bit odd.

    Please contact customer support - I think we should look at this data to understand what is going on. I don't know whether it is benign or a cause for concern.

    Regards,

    Andrew.

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.