Qorivva MPC5xxx/SPC5xx Debugger and NEXUS Trace
135
©1989-2021 Lauterbach GmbH
NEXUS.HTM
Enable branch history messaging
Control program trace messaging mode.
HTM can reduce the amount of program trace messages to about 10% of the classical branch trace
messaging. Use this option to increase trace recording time or to prevent overflows of the on-chip nexus
message fifo.
NEXUS.OFF
Switch the NEXUS trace port off
If the debugger is used stand-alone, the trace port is disabled by the debugger.
If the debugger is used together with a calibration tool (SYStem.Option ETK / SYStem.Option GSI), any
writes to trace registers (by the debugger) are suppressed. Use this setting if the calibration tool makes use
of the data trace (e.g. XETK-V2 in data trace configuration). The debugger will continue to record the trace
as a slave (i.e. trace configuration is exclusively done by calibration tool).
Format:
NEXUS.HTM
[
ON
|
OFF
]
SYStem.Option HTM
[
ON
|
OFF
]
(deprecated)
OFF
(default)
The core generates a program trace message for every taken direct or
indirect branch (i.e. branch trace messaging).
ON
The core generates only program trace messages for taken indirect
branches. For all direct branches, only the information taken/not take in
generated (branch history trace messaging).
NOTE:
The debugger can reconstruct the full program flow with BTM as well as when
using HTM. The only drawback of HTM is that runtime statistic results will be
less accurate because of the lower amount of messages (fewer messages and
therefore fewer timestamps per instruction). To some degree, the longer
recording time will compensate the loss of accuracy.
When supported by the processor, enable program trace correlation messages
at branch-and-link occurrence (
) together with HTM.
Doing so will achieve the same accuracy as BTM for run-time measurements on
function level.
Format:
NEXUS.OFF
