Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 13250
  • 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

SPICE imported .SUBCKT requires different modelname than given in netlist

HoWei

I do have a PDK library with an nmos device with different device and model name

libname= <pdk lib>

cellname= nmos_1p5_dw

modelname= nmos_1p5   <-- this name is provided by the modelfile

That is working fine.

Now I need to import SPICE netlists (standard cells) and the SPICE subcircuit has the following code:

     .SUBCKT … … … 

     XM0 net1 net2  Vss Vss nmos_1p5_dw …  …

The import works well and the device "nmos_1p5_dw" (as found in the referenced PDK lib) is instantiated in the new schematic.

The problem now is, that the new schematic has an device instance with the following parameters:

libname= <pdk lib>

cellname= nmos_1p5_dw

modelname= nmos_1p5_dw   <-- this name is NOT provided by the modelfile

The problem is that the modelname is equal to the cellname and this model cannot be found in the modelfile.

The simulation fails.

Is there a way during import (or in the netlist file) to declare the modelname as "nmnos_1p5" ?

  • Apparently the only way is to edit the netlist file and add the model parameter explicitly:

         .SUBCKT … … … 

         XM0 net1 net2  Vss Vss nmos_1p5_dw model=nmos_1p5 …  …

    Then the import ofthe device parameter "model" works properly.

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.