• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. update instance cdf properties after storeDefaults chan...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 16216
  • 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

update instance cdf properties after storeDefaults changed

annoyingGuy
annoyingGuy over 6 years ago

Hi,

We changed our PDK to set storeDefaults=yes for all parameters.  This works fine for new schematics and instances that are manually touched.  We tried using a skill script to go through a design library and run the PDK callbacks to force the individual instances to now store the default values on each instance.  However.... not all the parameter values were store, only about half.  The half not stored is of course the more critical values we need stored!  Poking around in the documentation I found a command cdfUpdateInstParam.  This will imprint ALL cdf parameters onto the device... but... it uses the effective cell CDF with turns out to override a lot of the manually set parameters (like gate length, width, number of fingers, etc).  

Is there a command to imprint the instance with the current cdf property values, even the default ones?  In other words, most of the values are default and thus not previously stored (schematics and layouts created before storeDefaults changed to yes).  If the device is touched/tickled appropriately, it should get imprinted with all property values since they all now have storeDefaults changed to yet.  How do I do this?

using IC6.1.7-64b.500.17

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    As far as I know, there's no simple built-in function to do this. Calling the callbacks won't help, because this is nothing to do with the callbacks. It should be as simple as looking through all the CDF parameters in the CDF object, checking if any have storeDefault=yes, and dbFindProp on the instance doesn't return anything, and then doing a dbCreateProp to create the property with the default value on the instance.

    I'll write a function (and an article) to do this once I'm back from vacation next week.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • annoyingGuy
    annoyingGuy over 6 years ago in reply to Andrew Beckett

    I was able to look these two functions up in the documentation (dbFindProp and dbCreateProp) and write a script that worked.  Although, it is very inefficient and slow.  I Look forward to seeing your script after you enjoy your vacation.  Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • annoyingGuy
    annoyingGuy over 6 years ago in reply to Andrew Beckett

    I was able to look these two functions up in the documentation (dbFindProp and dbCreateProp) and write a script that worked.  Although, it is very inefficient and slow.  I Look forward to seeing your script after you enjoy your vacation.  Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information