Technical data

Saving and viewing waveforms
ModelSim EE/PLUS Reference Manual Tips and Techniques
-
535
window will not display internal variables. In addition, none of the hidden objects
may be accessed through the Dataflow window or with VSIM commands.
Even with the data hiding of
-nodebug
, there remains some visibility into models
compiled with
-nodebug
. The names of all design units comprising your model
are visible in the library, and the user may invoke
vsim
(p91) directly on any of
these design units and see the ports. To restrict visibility into the lower levels of
your design you can use the following
-nodebug
switches when you compile.
Note:
Don’t use the
=ports
switch on a design without hierarchy, or on the top level of a hierarchical
design, if you do no ports will be visible for simulation. To properly use the switch, compile all lower portions
of the design with -nodebug=ports first, then compile the top level with -nodebug alone.
Also note the =pli switch will not work with vcom (the VHDL compiler). PLI functions are valid only for
Verilog design units.
Saving and viewing waveforms
You can run VSIM as a batch job, but view the resulting waveforms later.
1
When you invoke VSIM the first time, use the
-wav
option to rename the log file, and
redirect stdin to invoke the batch mode. The command should look like this:
vsim -wav wavesav1.wav counter < command.do
Within your
command.do
file, use the
log
command (p325) to save the waveforms
you want to look at later, run the simulation, and quit.
When VSIM runs in batch mode, it does not write to the screen, and can be run in
the background.
Command and switch Result
vcom -nodebug=ports makes the ports of a VHDL design unit invisible
vlog -nodebug=ports makes the ports of a Verilog design unit invisible
vlog -nodebug=pli prevents the use of PLI functions to interrogate the individual module
for information
vlog -nodebug=ports+pli
(or =pli+ports)
combines the functions of -nodebug=ports and -nodebug=pli