RSpice

RSPICE / DOCS / MODELS AND PDKS

Models and PDKs.

Point RSpice at the model libraries a design needs, choose the model each instance runs with, edit a project copy of a model, and attach a technology to the project.

WORKSPACE
Models, Alt+6
LIBRARY PATHS
Tools › PDK and model paths…
PER INSTANCE
Tools › Model browser…
PER RUN
Simulate › Setup › Models & sections

01 / WHERE MODELS COME FROM

Built-in devices, the foundation library, and your own files.

  • Built-in device models: the classic SPICE elements and native compact models such as BSIM3, BSIM4, BSIM-SOI, VBIC and EKV, selected by a .model card's type and LEVEL. A MOSFET level RSpice does not list is refused rather than approximated.
  • Generated Verilog-A models: 43 compact models generated from their Verilog-A sources, in builds made with the generated-veriloga-catalog feature. See Verilog-A.
  • The foundation library: a small, generic SPICE model library that every product build ships.
  • Your model files: libraries on disk that RSpice scans, and model sources a project imports. A deck reaches them with .INCLUDE, .LIB and .MODEL.

02 / MODEL LIBRARY PATHS

Tell RSpice where the model files are.

Tools › PDK and model paths… opens Model library paths:

  • Sources lists the library paths. Each can be included in or excluded from scans and edited in place; add one by typing a path or with Browse…, or bring one in with Import bundle….
  • Environment holds variables to use inside those paths.
  • The selected source's model files are listed with their type and sections, with a filter and an option to scan subdirectories.
  • Rescan reads the sources again; Save keeps the changes.

Tools › Rescan model libraries rescans without opening the dialog.

03 / THE MODELS WORKSPACE

Six pages over the loaded libraries.

The Models workspace (Alt+6, or Tools › Library manager) has six pages:

PAGESHOWS
Library managerThe loaded models, with which schematic instances use each and which instances name a model nothing provides, and the signed model packs this machine and project hold.
Symbols & CDFProject and technology symbols with their pins and device forms; pin order is netlist order. Create or import a symbol here, or open the form designer.
Corners & sectionsThe corner bindings from a sectioned model library, or from a section map imported from a SPICE source whose .lib sections define it.
Bins & geometryBinned model cards, whose L, W and NFIN bounds the simulator evaluates from the imported source.
Include graphThe model sources' include graph, with a manifest export and a way to resolve sources that have drifted.
Model qualificationWhich model families a release may be signed against, and on what evidence, per analysis domain.

04 / CHOOSE AN INSTANCE'S MODEL

Tools › Model browser…

Select an instance on the schematic and open the model browser. It lists every model a loaded library offers that the instance can take, under its library, with the card's level and key values on each row. A model the instance cannot take is not listed. A model whose name another library also uses stays listed but cannot be chosen, with the reason when you point at it.

05 / EDIT A MODEL

Edit a project-owned copy.

  1. Select a library model and choose Tools › Create editable project copy. The copy belongs to the project; the library is not changed.
  2. Tools › Edit model… opens the device-model editor on the project's definition. Its toolbar saves a model revision, validates the model, runs its qualification tests and compares it with a release.

Tools › Measurement correlation… compares a model with measured reference datasets kept in the project, plotting residuals at the measured points.

06 / TECHNOLOGY AND CORNERS

Bind the project to a technology, then pick a corner per run.

The Project workspace's Dependencies page shows the project's Technology & simulator binding: the technology, its model library, the root source and the source files it pins. Attach model technology… changes it. The project is saved before the binding changes, so an abandoned or failed change leaves a recoverable project, and a technology that would break pinned model sources is shown with the sources it would break. Model paths… on the same page opens Model library paths.

For a run, Simulate › Setup › Models & sections shows which corner section each loaded library will use and whether its source is pinned well enough to reproduce. Process corners across several sections are set up in the run set; see Verification.

07 / COMMAND LINE

Model packs from rspice.

rspice models lists the shipped SPICE model packs and looks up parts in them.