Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 1001
  • 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

SKILL code to parameterize a property(e.g. w,l) of an instance in schematic which reflects in the netlist

Atul Dwivedi

Hi all,

As the subject suggests, I want to insert parameters in a design to run further analisis (with the netlist). For the ease of the user, it is more instructive to somehow insert the parameters at the schematic level and get those parameters in the netlist ((IC6.1.5.500.132).  

I have done the following progress till now :

selectedObject=geGetSelSet()

selectedObject~>w="1.00*param1" ;;;;1.00 is mandatory scaling factor

However, this approach is not always working. While doing "check and save", I do get many errors of some parameters getting out of range (not the ones I have perturbed). Can anyone else suggest a more elegant and safe approach? 

Regards,
Atul 

  • theopaone

     Hi Atul

    Can you explain what you are doing better?

    Where does param1 get set?

    Is w a CDF parameter on the instance masters and what is its type?

    Can you give examples of the errors your getting with C&S ?

    Thanks

     Ted

  • Atul Dwivedi
    Hi Ted, Thanks for taking interest in such an old thread. However I recently realized that the errors which I was getting were due to some mistake in my script itself which I overlooked earlier. 'w' is the CDF parameter denoting width of MOS. param1 gets a value in the netlist. I add a few lines like .param param1=10u at the end before launching the simulator. The above approach selObj~>w="1*param1" is working perfectly fine for me now, except for the warning while netlisting: "param1 not set". (the catch was perhaps 'w' is a float, but is stored as a string!) Anyways, thanks for taking interest. Regards, Atul

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.