Stats

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

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??

Parents

  • In general you don't need the default values of each CDF parameter stored on the instance property list - that's not so efficient, and the point of CDF is that the default value comes from the CDF.

    There is a setting on each parameter in the CDF called "storeDefault" which can be set to "yes" - this means that it will then store an instance property on the instance whenever the create instance/edit properties form sets the value of that parameter to the default value. It won't do this if you create the instance with SKILL though. 

    However, as I said, there's no need to do this, and in general you should not do it (there are some occasional specific cases where it's useful or even necessary to set the default, such as when the CDF default is different from the pcell default but the general situation is that you should not need to do this).

    Regards,

    Andrew

Reply

  • In general you don't need the default values of each CDF parameter stored on the instance property list - that's not so efficient, and the point of CDF is that the default value comes from the CDF.

    There is a setting on each parameter in the CDF called "storeDefault" which can be set to "yes" - this means that it will then store an instance property on the instance whenever the create instance/edit properties form sets the value of that parameter to the default value. It won't do this if you create the instance with SKILL though. 

    However, as I said, there's no need to do this, and in general you should not do it (there are some occasional specific cases where it's useful or even necessary to set the default, such as when the CDF default is different from the pcell default but the general situation is that you should not need to do this).

    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.