User guide

19-24
Using the VCS / SystemC Cosimulation Interface
fprintf(stderr,"Error: stub for my_export_DPI is
used\n");
exit(1);
}
... more stubs for other export DPI function ...
gcc -c my_DPI_stubs.c
ar r my_DPI_stubs.a my_DPI_stubs.o
...
syscsim ... my_DPI_stubs.a ...
It is important to use an archive (file extension .a ) and not an object
file (file extension .o).
Specifying Runtime Options to the SystemC Simulation
You start a simulation with the simv command line. Command line
arguments can passed to just the VCS simulator kernel, or just the
sc_main() function or both.
By default, all command line arguments are given to sc_main() as
well as the simulator kernel. All arguments following
-systemcrun go only to sc_main(). All arguments following
-verilogrun or -vhdlrun go only to the VCS simulator kernel.
Argument -ucli is always recognized and goes only to the VCS
simulator kernel.
For example:
simv a b -ucli g -verilogrun c d -systemcrun e f
Function sc_main() receives arguments "a b e f g". The VCS simulator
kernel receives arguments "c d -ucli."