Product Documentation
Spectre AMS Designer and Xcelium Simulator Mixed-Signal User Guide
Product Version 22.09, September 2022

Migrating to Single-Step XRUN Invocation

You can run the AMS Designer simulator and the Xcelium simulator with the mixed-signal option using xrun in single-step mode or using the traditional direct invocation (three-step method) use model. It is recommended that you use xrun single-step mode for mixed-signal design verification. The following information can help you migrate from direct invocation mode to using single-step xrun.

File/Information for Three-Step

...for xrun

cds.lib (required)

Not required (remove or convert to xrun options)

worklib (required)

Not required (remove or convert to xrun options)

hdl.var (optional)

Not required (remove or convert to xrun options)

connect modules and connect rules

Use the ie statement in an amsd block

model path

Include device model files, optionally with a model section specifier, in a control file along with your amsd block For example:

* AMS control file -- amsdControl.scs
include "./source/design.scs"   //analog netlist
include "./models/model.scs"    //device model files
include "./models/diode.scs" section=dio
// diode.scs is the model file; "dio" is the section to use
include "./models/pmos1.scs" section=nom
// pmos1.scs is the model file; "nom" is the section to use
include "./analogControl.scs"   //analog control file

//amsd blockamsd{
      portmap subckt=pll_top autobus=yes
      config cell=pll_top use=spice
      ie vsup=2.0
      }

-propspath prop.cfg

Specifying a prop.cfg is no longer supported; therefore, you must convert to using an amsd block. See Migrating to an amsd Block from prop.cfg.

Alternatively, you can instruct the internal translator to convert your prop.cfg file to an amsd block file, prop.cfg.scs, by setting the AMSCB environment variable. 

Tcl probes

No change

analog control file

Specify the analog control file directly on the xrun command line; you do not need to use the -analogcontrol option; include one or more amsd blocks in this file.

discipline

Optional; if you do not specify a discipline (using the -discipline command-line option to xrun Command Syntax), the default discipline is logic ; see also the mode specifier on the ie statement.

timescale

No change

-ams option (required)

Not required (remove); xrun recognizes AMS input files by their extensions.

Here is an example of a three-step example that you can simplify using xrun:

Direct Invocation example

Single-step xrun equivalent

xmvlog -ams \
        -cdslib cds.lib \
        ./source/digital/*.v

xmelab worklib.testbench \
        connectLib.ConnRules_18V_full \
        -cdslib cds.lib \
        -hdlvar hdl.var \
        -snapshot top:snapshot \
        -amsf \
        -timescale 1ns/100ps \
        -discipline logic \
        amsd.scs \

xmsim top:snapshot \
        -cdslib cds.lib \
        -analogcontrol top.scs \
        -input probe.tcl \
        -simcompat hspice

xrun ./source/digital/*.v \
        ./amscf.scs \
        -amsf \
        -timescale 1ns/100ps \
        -input probe.tcl

Related Topics



 ⠀
X