interfacetrace
Abstract
In a cosimulation, sets a trace on the specified interface. Interface traces consist of statements indicating Kernel Procedures and selected Simulation Kernel actions applied to the specified interface.
Syntax
interfacetrace <objref>
| Argument | Type | Description |
|---|---|---|
<objref> |
integer or string | numeric object ID or hierarchical name of the interface-of-interest An object ID for this argument can be obtained by using the ODB commands objmap or objid. |
Details
An event associated with traced KPs and actions is indicated by an event banner that precedes the trace messages. Multiple interface traces can be active at the same time. An interface trace is active from the time it is set until it is suspended or deleted. Traces can be suspended by susptrace, reactivated by acttrace, or deleted by deltrace.
Example
ODB> interfacetrace top.adder.adder.addend0
Added trace #1: trace on top.adder.adder.addend0
ODB> evstop +20
Added breakpoint #1: stop at nth event (38)
ODB> c
.
.
.
____________________________ (ODB 18.6.0: Event) ____________________________
* Time : 0.002 sec, [2ms]
* Event : execution ID (24), schedule ID (#28), type (stream intrpt)
* Source : execution ID (20), top.adder.adder_rx0 (pt-pt receiver)
* Data : instrm (0), packet ID (1)
> Module : top.adder.adder (esys module)
*- op_esys_interface_value_set (interface, schedule_time, value [, index])
| interface ID 30 (top.adder.adder.addend0)
| schedule time (0.002)
| value (62464)
| index (-1)
| event handle (36)
+------
.
.
.