Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 3019
  • 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

eliminate "updated since last schematic save" warnings when netlisting with cells from basic/analogLib

NicolasCAD

 We recently switched to defining the artist primitive libraries that come with the IC61 installations:

DEFINE analogLib $(compute:THIS_TOOL_INST_ROOT)/tools/dfII/etc/cdslib/artist/analogLib

DEFINE basic $(compute:THIS_TOOL_INST_ROOT)/tools/dfII/etc/cdslib/basic

The old way was to freeze old versions of analogLib and basic libraries and rev them slowly over time. Since we use the latest ones from the virtuoso installations, Cadence continues to patch and update cells in their lib primitives, runs checkNSave on them, and gives the cellviews a recent lastExtraction/instancesLastChanged (which ever way it now gets stored internally in OA) property date stamp.

This makes it such that IP that is older than these patches needs check-and-save to avoid warnings such as:

*WARNING* (SCH-2159): "basic ipin symbol" updated since last schematic save.

*WARNING* (SCH-2159): "basic opin symbol" updated since last schematic save.

*WARNING* (SCH-2159): "basic iopin symbolr" updated since last schematic save.

*WARNING* (SCH-2159): "basic ipin symbol" updated since last schematic save.

This side effect also slows down netlisting when one has many cells to neltist.

I would like a solution to avoid these warnings. As a workaround, I tried some skill code that used to do the trick in IC51.41 by setting the instancesLastChanged property some 10 years in the past.  It seems that doesn't do the trick in IC615.

I suppose I could run some skill code (once I figure out the recipe in IC61) on the basic and analogLib everytime I install a fresh IC61 build, which makes this solution cumbersome. Anyone have a better idea?

thanks Nicolas

Parents

  • Nicolas,

    In OpenAccess, it no longer uses timeStamps to compare the up-to-dateness of symbols (or indeed whether something needs check-and-saving). This was for two reasons - one, the timestamp only had a 1 second resolution, and a lot can happen in a second, and two, it was relatively expensive to keep looking up the clock from the OS. So instead, openAccess uses counters to keep track of the number of database changes.

    The modifiedCounter attribute is what represents this in the database. However, whilst you can disable this from being updated (using dbDisableCellViewCounter), you cannot set the modifiedCounter to a value of your choosing.

    Cadence tries to ensure that cosmetic changes in the symbols in these libraries don't lead to a change in the modifiedCounter, and so in general keeping in sync with the released analogLib/basic should not lead to the warnings you're seeing. Of course, if you've not been using our libraries but a separate copy of them, maybe the change happened some time ago.

    There is the ability to turn off this check - using the checkSymTime cdsenv var (search in cdnshelp for details of this). Note the documentation is not quite up to date; it still references to instancesLastChanged, which is not what is currently done. However, I wouldn't really recommend disabling this check... it's mainly intended to alert you to symbol changes such as pin additions/deletions/move.

    Regards,

    Andrew.

Reply

  • Nicolas,

    In OpenAccess, it no longer uses timeStamps to compare the up-to-dateness of symbols (or indeed whether something needs check-and-saving). This was for two reasons - one, the timestamp only had a 1 second resolution, and a lot can happen in a second, and two, it was relatively expensive to keep looking up the clock from the OS. So instead, openAccess uses counters to keep track of the number of database changes.

    The modifiedCounter attribute is what represents this in the database. However, whilst you can disable this from being updated (using dbDisableCellViewCounter), you cannot set the modifiedCounter to a value of your choosing.

    Cadence tries to ensure that cosmetic changes in the symbols in these libraries don't lead to a change in the modifiedCounter, and so in general keeping in sync with the released analogLib/basic should not lead to the warnings you're seeing. Of course, if you've not been using our libraries but a separate copy of them, maybe the change happened some time ago.

    There is the ability to turn off this check - using the checkSymTime cdsenv var (search in cdnshelp for details of this). Note the documentation is not quite up to date; it still references to instancesLastChanged, which is not what is currently done. However, I wouldn't really recommend disabling this check... it's mainly intended to alert you to symbol changes such as pin additions/deletions/move.

    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.