User guide

19-37
Using the VCS / SystemC Cosimulation Interface
Transaction Debug Output
Since the transaction information traveling back and forth between
SystemVerilog and SystemC along with the transaction timing is often
crucial information (for example, comparison of ref-model and design
for debugging and so on), the SystemC part of the TLI adapters are
generated with additional debugging output that can be enabled or
disabled, See “Instantiation and Binding” on page 19-38.
The transaction debug output can either be used as a terminal I/O
(stdout) or as a transaction tracing in DVE. In DVE, each TLI adapter
has an sc_signal string member with name
m_task_or_function_name_transactions that you can
display in the waveform viewer of DVE.
Sometimes, the next transaction begins at the same point in time
when the previous transaction ends. Prefixes "->" and "<-" are used
such that both transactions could be distinguished. The return values,
if any, for the previous transaction are displayed with a leading "<-".
The input arguments for the new argument are prefixed with "->".
If the default scheme how the debug output is formatted does not
match the debugging requirements, then do not change the
generated code in the TLI adapter. Instead, override the debug
methods m_task_or_function_name_transactions using a
derived class that defines only these virtual methods. You can copy
these methods from the generated adapter code as a starting point
and then modify the code according to the debugging requirements.
If the adapter is generated again, then the existing code is overwritten
and all manual edits are lost.