User guide

20-36
Using OpenVera Assertions
This dump file must contain, as a minimum, any signal referenced by
the OVA checkers to be post-processed. The signals used by the
OVA checkers must be included in a $dumpvars or $vcdpluson
dumped scope (an instance specified in one of these system tasks)
in order to be visible by the post-process checkers. Automated
dumping of OVA signals is not supported.
The runtime option -vcd filename can be used to name the VCD
file if there is a $dumpvars system task in the design. The +vpdfile
filename option and argument can be used to name the VPD file
if there is a $vcdpluson system task in the design.
If you include the signals referenced by the checkers in $vcdpluson
and -PP or $dumpvars, the referenced signals will be dumped at
compile time.
Note:
Do not use -ova_debug to generate dump files, since the
generated files will not contain all the right hierachies.
It is recommended that the dump files be explicitly named in all cases.
Both the simv executable and the ovapp executable use the same
default name for the dumpfile output. If you dump a VPD file by it's
default name in step 1 and use this file as the input to ovapp, it is
possible that the input dumpfile can be overwritten.
Note that the step 3 (
ovapp) waveform input file is specified with the
-vcd or -vpd options. The -vcd vcdfile option tells
ovapp to read
a VCD file, while -vpd vpdfile tells
ovapp to read a VPD file. This
-vcd option is NOT the same option used by VCS to name the output
waveform file. Caution in using this option is recommended.