User guide

6-27
VPD and EVCD File Generation
File size is a direct result of circuit size, circuit activity, and the data
being saved. Test cases show that VPD file sizes can range from a
few megabytes to a few hundred megabytes. Many DVE users can
share the same VPD history file, which may be a reason for saving
all time value changes when you simulate a design. You can save
one history file for the design and overwrite it on each subsequent run.
Syntax:
+vpdfilesize+nn
Here nn is the file size in megabytes.
+vpdignore to Ignore $vcdplus Calls in Code
The +vpdignore command instructs VCS to ignore any
$vcdplusxx calls and license checking. By default, VCS checks out
a VPD PLI license if there is a $vcdplusxx task in the Verilog source.
In some cases, this statement is never executed and VPD PLI license
checkout should be suppressed. The +vpdignore command
performs the license suppression.
Syntax:
+vpdignore
+vpddrivers to Store Driver Information
By default, VPD records value changes only for the resolved value
for each net. To also report value changes for all the drivers when
there is more than one driver, use the +vpddrivers option during
simulation. The driver values, for example, enable the Logic Browser
to identify which drivers produce an undesired X on the resolved net.