ModelSim SE User's Manual - Electrical and Computer Engineering

Code modification examples
Compiling SystemC files UM-165
Removing calls to sc_initialize()
vsim calls sc_initialize() by default at the end of elaboration, so calls to sc_initialize() are
unnecessary.
Exporting all top level SystemC modules
For SystemC designs, you must export all top level modules in your design to ModelSim.
You do this with the SC_MODULE_EXPORT() macro. SystemC
templates are not supported as top level or boundary modules. See "Templatized SystemC
modules" (UM-171). The sc_module_name is the name of the top level module to be
simulated in ModelSim. You must specify this macro in a C++ source (.cpp) file. If the
macro is contained in a header file instead of a C++ source file, an error may result.
For HP-UX: Explicitly naming signals, ports, and modules
Important: Verify that SystemC signals, ports, and modules are explicitly named to avoid
port binding and debugging errors.
Example 1
The following is a simple example of how to convert sc_main to a module and elaborate it
with vsim.
Original OSCI code #1 (partial) Modified code #1 (partial)
int sc_main(int argc, char* argv[])
{
sc_signal mysig;
mymod mod("mod");
mod.outp(mysig);
}
sc_start(100, SC_NS);
The run command equivalent to the sc_start(100, SC_NS) statement is:
run 100 ns
SC_MODULE(mytop)
{
sc_signal mysig;
mymod mod;
};
SC_CTOR(mytop)
: mysig("mysig"),
mod("mod")
{
mod.outp(mysig);
}
SC_MODULE_EXPORT(mytop);
ModelSim SE User’s Manual