Stats

  • Locked Locked
  • Replies 1
  • Subscribers 124
  • Views 12973
  • 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

adding simulator views to a PDK

archive

Is there a simple way to add simulator views of (eg:eldo or hspice) for the PDK cells, so that you could netlist in the format specified by these simulators.I would like to do this without disturbing the PDK or design kit as such.


Thanks
Amarnath


Originally posted in cdnusers.org by amarnath
Parents

  • Normally you need to add the simInfo section in the CDF for the particular simulator in question (e.g. eldoD or hspiceD). If you don't want to permanently modify the CDF, you should be able to do this in the effective CDF (easiest to modify the effective CDF interactively via the Tools->CDF->Edit form, and then use the SKILL cdfDump() function to dump the User CDF - see the manuals for more details). Then you can load the user CDF during each session to overwrite it in memory.

    The second requirement is usually to create a stopping view with the same name as the simulator integration, for each component. However, it doesn't _have_ to be called eldoD. So, you can modify the Setup->Environment->View list to include a view that is already there (e.g. "spectre") - and also put this in the Stop List. Similarly, if you're using a config, put the existing view in the view and stop lists in the hierarchy editor.

    Still, if you're doing this over and over again, it may just be best to bite the bullet and modify the PDK. With a bit of SKILL code, that could be automated, to make it easier to maintain.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
Reply

  • Normally you need to add the simInfo section in the CDF for the particular simulator in question (e.g. eldoD or hspiceD). If you don't want to permanently modify the CDF, you should be able to do this in the effective CDF (easiest to modify the effective CDF interactively via the Tools->CDF->Edit form, and then use the SKILL cdfDump() function to dump the User CDF - see the manuals for more details). Then you can load the user CDF during each session to overwrite it in memory.

    The second requirement is usually to create a stopping view with the same name as the simulator integration, for each component. However, it doesn't _have_ to be called eldoD. So, you can modify the Setup->Environment->View list to include a view that is already there (e.g. "spectre") - and also put this in the Stop List. Similarly, if you're using a config, put the existing view in the view and stop lists in the hierarchy editor.

    Still, if you're doing this over and over again, it may just be best to bite the bullet and modify the PDK. With a bit of SKILL code, that could be automated, to make it easier to maintain.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
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.