You can invoke xrun using the following ways:
- Single-step xrun invocation: The most basic way to use
xrunis to list the files that comprise the simulation on the command line, along with all command-line options. The syntax is:xrun [options] <source_files>
For example:% xrun -ieee1364 -v93 -access +r -gui verify.e top.v middle.vhd sub.v - Multi-step XRUN invocation: When using the xrun utility in multi-step invocation, Xcelium supports a flexible use model with the same behavior and feature set as traditional direct invocation. You can run the following options to perform the various steps independently:
- Compilation:
% xrun -compile [options] <source_files> -
Elaboration:
% xrun -elaborate [options] <source_files>Alternatively, you can use the two-step mode to compile and elaborate the design by using
xrun -c [options] <source_files>. -
Simulation:
% xrun -R
- Compilation:
For AMS simulation, the xrun command recognizes the following source file types (sourceFiles) by their file extensions:
|
Source File Type |
Valid Extensions |
|---|---|
|
Spectre or SPICE |
You can specify additional extensions for analog source files using |
|
Verilog-AMS |
You can specify additional extensions for Verilog-AMS source files using the |
|
SV-AMS |
|
|
VHDL-AMS |
You can specify additional extensions for VHDL-AMS source files using |
For complete information about the file extensions that are recognized by xrun and how to change the default set, see Customizing XRUN. You can also type xrun -helpfileext to see a list of file extensions.
You must not specify -ams on the xrun command line unless you want to force xrun to compile all Verilog and VHDL input files as AMS files.
While you can compile both SystemVerilog and AMS source files on the same command line, you cannot have a file that contains both SystemVerilog and AMS statements. See Using SystemVerilog Modules.
Related Topics
- Using xrun with Spectre and SPICE Input Files
- xrun Command-Line Options for Mixed-Signal Designs
- XRUN Options