User guide

20-35
Using OpenVera Assertions
As you can see, in step1, we pass simv1 as the basename for the
intermediate output files. In step 2, we pass the vdb directory created
as a result of step1 as the argument of the -vdb_lib option and give
VCS a second basename, simv2, for the new intermediate file
directory. When VCS tries to locate a file in the simv2.vdb directory
(during step 2) and cannot find the file, it next checks the directory
specified by the -vdb_lib option. This way, you can run many
unique step 2 OVAPP compilations using the same base design
without running the risk of overwriting necessary files generated by
the base design compilation.
In addition to the -o and -vdb_lib options, other compile-time
options must be taken into consideration when running multiple
compilations, simulations, or post-process runs in the same directory.
The following sections describe in detail some of the issues to
consider.
Interactive Simulation
The initial compile can be used as an interactive/batch simulation,
with or without OVA checking. Simply add -PP or -I to the step 1
compile command line.
Waveform Dump Files
The post-processing run requires a waveform dump file. This file can
be either a VCD file or a VPD file. The file can be generated by any
simulation which is based on the same design as was compiled in
step1 (the -ova_PP step). The dump file can be generated by the
executable resulting from the Step1 compile, an earlier interactive
simulation of the same design, or some other simulation.