Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 15029
  • 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

Error during the traversal of the config myLib myCell config

twen

When I do "Add Bind to Open (skip cell)" in the Hierarchy Editor to try to skip some cells which are not critical but slow down the simulation, the netlister spits out the following errors. If I remove all the UNBOUND cells and instances, then no such errors are produced.  Does anyone know what this error is and how to get rid of it? If click either the OK or the Cancel button, the netlister continues and the simulation does produce the expected results but this is very annoying.

getVersion
"@(#)$CDS: virtuoso version 6.1.6-64b 12/07/2015 20:18 (sjfbm186) $"
>

generate netlist...
no risk of models double definition
ams import netlist enabled
*WARNING* ddGetObj: invalid libId (0x(nil)).
*WARNING* ddGetObj: invalid libId (0x(nil)).
*WARNING* ddGetObj: invalid libId (0x(nil)).
*WARNING* Object: .() pc.db cannot be opened
UART-ERROR:Can't open pcdb for lib: cell: view:
>
hiDBoxOK(G457)
t
UART-ERROR:Error during the traversal of the config myLib myCell config.
*WARNING* ddGetObj: invalid libId (0x(nil)).
*WARNING* ddGetObj: invalid libId (0x(nil)).
*WARNING* ddGetObj: invalid libId (0x(nil)).
*WARNING* Object: .() pc.db cannot be opened
UART-ERROR:Can't open pcdb for lib: cell: view:
UART-ERROR:Error during the traversal of the config myLib myCell config.
config default switch and stop view lists aligned with the design kit
INFO (AMS-2142): The AMS Unified Netlisting (AMS UNL) flow has been enabled.


TJ

Parents
  • Andrew Beckett

    The UART-ERROR messages are not Cadence error messages - they are coming from the Process Design Kit you're using. I've found two reports of this, both using PDKs from the same foundry. In general bind to open should work, but there must be something in that PDK customisation which is breaking things.

    You should report this to the supplier of the PDK - it's possible they've fixed it in the meantime? (both reports I saw were from the same customer, and both about 16-18 months ago). In both cases there was nothing Cadence could do to fix it, as it's related to the PDK customisation.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    The UART-ERROR messages are not Cadence error messages - they are coming from the Process Design Kit you're using. I've found two reports of this, both using PDKs from the same foundry. In general bind to open should work, but there must be something in that PDK customisation which is breaking things.

    You should report this to the supplier of the PDK - it's possible they've fixed it in the meantime? (both reports I saw were from the same customer, and both about 16-18 months ago). In both cases there was nothing Cadence could do to fix it, as it's related to the PDK customisation.

    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.