Stats

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

CDF ?storeDefault doesn't work after changing instance master

RVERP

I have a procedure where I replace an instantiated pcell with another pcell. This I do by changing the instance master (instance~>master = newMaster). The new master has the same cdf parameters, and adds additional ones.

I have noticed that for the instances I have changed this way, ?storeDefault doesn't work.

Now I make a mixed layout with updated instances (changed with my command) and intances of newMaster created with create instance. When I update the cdf default, the ones changed with my command take the new default, while the instantiated ones don't.



I hope this is a bit clear. It seems the cdf defaults are only stored when you create an instance. Replacing it doesn't store the default since there never was the instantiate step. Are there other ways to change the master of an instance? So I can test what this does with ?storeDefault.

  • Changing the master will not affect any of the user-defined properties on the instance. That means that whatever properties that were stored locally on the instance will remain (so anything that was placed in the editor with a CDF default value and storeDefault on will have the local property stored on the original device). The new device's CDF has no impact on the remastering.

    Is this layout or schematic? I think (I haven't checked) leRemasterInstances might handle this, but I'm not sure (and that remasters all instances of a given master, so may not be what you want).

    I think I might need a better understanding of how the CDF is different before and after - perhaps this is better handled via customer support?

    Andrew

  • in reply to Andrew Beckett

    This is layout.

    The CDF of the newMaster has the same parameters as the old instance, but includes additional ones. These are not stored yet on the instance as a parameter since there was never a command to instantiate. Maybe here dbCreateParamInstByMasterName is used. I the help it says specifically this command stores the cdf parmeters as a property on the instance.

  • in reply to Andrew Beckett

    leRemasterInstances doesn't seem to work.

  • in reply to Andrew Beckett

    I tried a different method. I replace the instance with a new one using the new master and using the prop of the original instance.

    First this didn't work and gave the same result (not storing the default), but if I instantiate a new instance (dbCreateParamInstByMasterName), run cdfUpdateInstParam to store the defaults and the update the parameters to match the old instance (dbReplacePropList), the defaults are stored and all is as expected.

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.