Stats

  • Locked Locked
  • Replies 5
  • Subscribers 142
  • Views 14454
  • 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

Customize PDK library without changing it.

nosaj

Hi all,


I'm looking for a way to change the CDF default value that doesn't require user interaction and changes to the actual PDK library.

e.g.

By default, pmos A=1, and CDF value of pmos's x, y, z  depends on callback of A.

Normally when the user instantiate pmos, they will change A=2, and subsequently updating x, y, z.

What I want : When user instantiates the pmos, CDF is already set to A=2 and x, y, z already update accordingly and automatically

How can this be achieved?

 Thanks in advance.

Parents

  •  Hi,

    Yes, that is the situation I was describing.  A problem with this is that the "force-the-callbacks-to-run" code works on the instantiated devices, not the unplaced "form" device since it does not have an instance id nor instance CDF yet.  So you would somehow need to change the User CDF for all of the dependent parameters in exactly the same way that the PDK does so that the device parameters are all consistent with each other. This might work but you would need to be sure (by inspection I guess) that one of your changed-default devices matches a device where A was changed interactively from 1 to 2.

    How about placing the devices with A=1 and changing them all to A=2 later (needs some designer interaction to trigger this I would think)? This is where the callback code would come into play.  This fails your criteria on no user interaction.

    For automatically running this code I cannot think of a good triggering event - you would want something like a run-this-after-any-libInit.il  trigger (assuming you were going to use the method that creates the User CDF).  Perhaps you could have a userPostInstall trigger on the view in question?  Not ideal but it might work?

    Hmm, I'm running out of ideas and it is starting to sound messy.

    Regards,

    Lawrence.

Reply

  •  Hi,

    Yes, that is the situation I was describing.  A problem with this is that the "force-the-callbacks-to-run" code works on the instantiated devices, not the unplaced "form" device since it does not have an instance id nor instance CDF yet.  So you would somehow need to change the User CDF for all of the dependent parameters in exactly the same way that the PDK does so that the device parameters are all consistent with each other. This might work but you would need to be sure (by inspection I guess) that one of your changed-default devices matches a device where A was changed interactively from 1 to 2.

    How about placing the devices with A=1 and changing them all to A=2 later (needs some designer interaction to trigger this I would think)? This is where the callback code would come into play.  This fails your criteria on no user interaction.

    For automatically running this code I cannot think of a good triggering event - you would want something like a run-this-after-any-libInit.il  trigger (assuming you were going to use the method that creates the User CDF).  Perhaps you could have a userPostInstall trigger on the view in question?  Not ideal but it might work?

    Hmm, I'm running out of ideas and it is starting to sound messy.

    Regards,

    Lawrence.

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.