Stats

  • Locked Locked
  • Replies 18
  • Subscribers 125
  • Views 19291
  • 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

Modelfile not loaded in ADE

HoWei

I transferred an existing project with PDK into our environment.

In .cdsinit it is set:

  envSetVal("spectre.envOpts" "modelFiles" 'string "/model_libraries/models/lvt_mos.scs;TT")

When verifying in the CIW via

 envGetVal("spectre.envOpts" "modelFiles")

I see it is set properly.

But when opening ADE and creating a netlist, it does not include this modelfile. It also does not show the modelfile in the ADE modelfile-popup-windows - its just empty.

This not only for existing cells, it is also for newly created cells.

WhenI select the modelfile in the ADE modelfile-popup-window, it is included in the netlist.

How can I make it to include the modelfile ?

What does prevent the modelfiles to be loaded ?

Parents
  • HoWei

    I further-more found, that the netlist includes a file "models.scs", and this file contains:

    "include "setupCornersIncludeFile.scs"

    and this included file contains:

     "include "importNetlist.scs"

    and this included file contains only commented lines, saying that in case of an non included modelfile do "Check&Save" or  "recreate netlist".

    These files are somehow coming from the PDK.

    Any idea ?

  • HoWei
    in reply to HoWei

    I found out that this problem exists only with already existing ADE-states and also when the default simulator was set to Eldo !

    Setting the default simulator from eldo to spectre will include the modelfiles for a new ADE state. 

    For existing states with spectre - the simulator has to be changed to another simulator (e.g. Eldo) and then changed back to spectre - then the modelfiles are shown in GUI.

    Is there a way to tell existing states, that they shall use the model-files defined by "envSetVal("spectre.envOpts" "modelFiles") automatically - without unset/set spectre in the ADE ?

  • Andrew Beckett
    in reply to HoWei
    HoWei said:
    Is there a way to tell existing states, that they shall use the model-files defined by "envSetVal("spectre.envOpts" "modelFiles") automatically - without unset/set spectre in the ADE ?

    T...here is an option when you load a state to not update the models from the state: envSetVal("asimenv.loadstate" "modelSetup" 'boolean nil)

    This only works with ADE L though (I think).

    Andrew.

Reply
  • Andrew Beckett
    in reply to HoWei
    HoWei said:
    Is there a way to tell existing states, that they shall use the model-files defined by "envSetVal("spectre.envOpts" "modelFiles") automatically - without unset/set spectre in the ADE ?

    T...here is an option when you load a state to not update the models from the state: envSetVal("asimenv.loadstate" "modelSetup" 'boolean nil)

    This only works with ADE L though (I think).

    Andrew.

Children
  • HoWei
    in reply to Andrew Beckett

    I am not sure, but I this sounds like I want to set this option to "true" to get it updated, right ?

    If its only for ADE-L this does not help, but I will give it a try ....

  • Andrew Beckett
    in reply to HoWei

    No. If you set it to t, it means that when you load a state it will use the model setup information stored in the state. If you set it to nil, it will use the "default" setting and not override it with the value saved in the state. 

    You can see the same thing that if you open a new ADE L session, and then use Load State, the "model setup" checkbox will be turned off when you have the env var set to nil. The default value of the env var is t.

    Andrew.

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.