How To: Convert Simulator Commands

Modified on Thu, 19 Dec at 6:24 PM

How To: Convert Simulator Commands

To aid you in migrating from other simulators to the Altair® DSim™ simulator, their commands can be converted to DSim commands.

There is not necessarily a one-to-one mapping of other simulator commands to DSim commands, but the following mappings are applicable:

Description	Siemens ModelSim/ Questa	Cadence Xcelium	Synopsys VCS	Altair DSim	DSim Examples
Analyze/Compile Verilog / SV code	`vlog`	`xmvlog`	`vlogan`	`dvlcom`	`dvlcom ../../project/gw_i2c_master/src/gowin_rpll/gowin_rpll.v` `dvlcom -lib libB +incdir+../../src -F filelist.txt`
Analyze/Compile VHDL code	`vcom`	`xmvhdl`	`vhdlan`	`dvhcom`	`dvhcom -vhdl93 -lib fifo_generator_v13_2_7 ../wavegen.ip_user_files/ipstatic/hdl/fifo_generator_v13_2_rfs.vhd` `dvhcom -vhdl2008 -lib libA ../file1.vhd ../../file2.vhd`
Elaborate a design Simulate a design	`vsim`	`xmelab` `xmsim` `xrun`	`vcs` `simv`	`dsim`	`dsim -genimage image -top work.my_module -timescale 1ns/1ps +acc+b` `dsim -image image -run-until 10us -waves file.mxd`
Manage design libraries	modelsim.ini `vlib` `vmap`	cds.lib hdl.var	`-libmap`	`dlib`	`dlib ls -lib my_lib`

For more information about the DSim commands, see DSim Cloud CLI simulator commands.

For more information about the other simulator commands, see their respective user manuals.

Since DSim scripts are run on the user's local machine, scripts will have to be of a format compatible with their operating system. For Windows, the format is a PowerShell (*.ps1) script, while for Linux, the format is a Shell (*.sh) script. The DSim commands can be inserted into the scripts directly, paying attention to how environment variables are parsed by the different operating systems.