Technical data

Running command-line and batch-mode simulations
ModelSim EE/PLUS Reference Manual Tips and Techniques
-
533
During simulation a transcript file is created containing any messages to stdout. A
transcript file created in command-line mode may be used as a DO file if you
invoke the
transcript on
command (p378) after the design loads (see the example
below). The
transcript on
command will write all of the commands you invoke
to the transcript file. For example, the following series of commands will result in
a transcript file that can be used for command input if
top
is resimulated (remove
the
quit -f
command from the transcript file if you want to remain in the
simulator).
vsim -c top
library and design loading messages... then execute:
transcript on
force clk 1 50, 0 100 -repeat 100
run 500
run @5000
quit -f
Note:
Rename transcript files that you intend to use as DO files. They will be overwritten the next time
you run VSIM if you don’t rename them. Also, simulator messages are already commented out, but any
messages generated from your design (and subsequently written to the transcript file) will cause the simulator
to pause. A transcript file that contains only valid simulator commands will work fine; comment out anything
else with a "#".
Batch mode
In batch mode Model
Sim
behaves much as in command-line mode except that
there are no prompts, and commands from re-directed stdin are not echoed to
stdout.
Tcl user_hook variables (p226) may also be used for Tcl customization during
batch-mode simulation; see also, "Setting preference variables with the GUI"
(p211).