Stats

  • Locked Locked
  • Replies 2
  • Subscribers 63
  • Views 14947
  • 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

spectre , multiple model files and mixed section names

marcelpreda

Hi there,

We have a case where we have to use multiple model files in spectre simulation.

I want to avoid situation where by mistake different section names are used in the simulation.

E.g.

...
include "/home/predamar/tests/spectre/my_models/include.scs" section=fast
include "/home/predamar/tests/spectre/basic/include.scs"
include "/home/predamar/tests/spectre/my_models_2/include.scs" section=nom
...

In one place is used "fast", in other is "nom".

 I want to have the possibility to provide an error message and to stop the simulation.

The include lines which have no "section" will be ignored.

So, all the included files should have the same section name.

The only solution that I see now is to trigger a script before starting spectre simulation,and to parse the top netlist file.

I want to know if spectre has something builtin that may help.

 

Best Regards,

Marcel

  • Marcel,

    A few possibilities for doing this in spectre. One is to include a dummy parameter in each section:

    parameters includedMoreThanOnce=1

    Another is to define a dummy subckt in each section (with the same name). Unless the option redefinedparams has been changed (in the first case) or duplicate_subckt (in the second case) then it will fail. See "spectre -h options" for more details on these.

    The other approach would be to alter the flowchart (examples in this forum and on support.cadence.com) to trigger a check post-netlisting (say) to look at the output of asiGetModelLibSelectionList(asiSessionId) to check for duplicates. That would be cleaner than parsing the input.scs

    Regards,

    Andrew.

  •  Hi Andrew,

     There are just too many options :D

     I fully understood the 3rd one, but for the 1 and 2 I'll need some time to digest it.

    Thanks,

    Marcel

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.