• 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. Invalid CDF choice

Stats

  • Locked Locked
  • Replies 11
  • Subscribers 143
  • Views 18110
  • 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

Invalid CDF choice

RVERP
RVERP over 8 years ago

I have been using some skill code where an instance (pcell) master is replaced with another pcell. The parameters are not the same, so I assumed all the cdf parameters are set to the default value of the new pcell.

I do this in combination with clones, doing following steps:

  • Generate all instances from a schematic
  • Select the group I want to clone, and generate synchronous copy clones
  • Descend in on of the clones, and replace the instance master.

These steps don't give any problems, in all the clones the master is replaced with my custom pcell.

But sometimes, while altering a parameter, I get an error message An invalid CDF choice "netlist" was specified for the CDF parameter "source".

My new pcell has a cdf parameter "source", a string. My original pcell doesn't have a cdf parameter "source", so I have no idea where this is coming from. This problem occurs on about 20% of the clonegroups I work on with above procedure.

I tried to do something with resetting or clearing cdf parameters, but with no succes. Any ideas??

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

    You know what, I should have checked in a real database, rather than just off the top of my head. I checked in the documentation too. The issue is that "source" is the name of a built-in attribute for instance objects in the database, and so you should never have a CDF parameter called that (it's asking for trouble).

    Every instance has the attribute (not user defined property) called "source". You can see that by doing instId~>? . Here's what he relevant section of the Virtuoso Design Environment SKILL Reference says (in the chapter on Database Access, in the section at the end of that chapter called Attribute Retrieval and Modification:

    source: (string) The different sources you can assign to an instance. Valid Values: netlist, timing, dist, test, user

    The default value is "netlist". I'm not sure anything really uses it any more (it was probably used by older place and route tools, like Block Ensemble, which are long gone). I may be wrong though! I'd never noticed that it existed though, mostly because I'm not aware of anything using it.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    You know what, I should have checked in a real database, rather than just off the top of my head. I checked in the documentation too. The issue is that "source" is the name of a built-in attribute for instance objects in the database, and so you should never have a CDF parameter called that (it's asking for trouble).

    Every instance has the attribute (not user defined property) called "source". You can see that by doing instId~>? . Here's what he relevant section of the Virtuoso Design Environment SKILL Reference says (in the chapter on Database Access, in the section at the end of that chapter called Attribute Retrieval and Modification:

    source: (string) The different sources you can assign to an instance. Valid Values: netlist, timing, dist, test, user

    The default value is "netlist". I'm not sure anything really uses it any more (it was probably used by older place and route tools, like Block Ensemble, which are long gone). I may be wrong though! I'd never noticed that it existed though, mostly because I'm not aware of anything using it.

    Regards,

    Andrew.

    • 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