Specifications

Table Of Contents
ARM Debugger 68 ARM specific SYStem Commands
©1989-2014 Lauterbach GmbH
... .TraceID <id> Identifies from which component the trace packet is coming from.
Components which produce trace information (trace sources) for a
common trace stream have a selectable “.TraceID <id>”.
If you miss this SYStem.CONFIG command for a certain trace
source (e.g. ETM) then there is a dedicated command group for
this component where you can select the ID (ETM.TraceID <id>).
The default setting is typically fine because the debugger uses
different default TraceIDs for different components.
For a list of possible components including a short description
see Components and available commands.
CTI.Config <type> Informs about the interconnection of the core Cross Trigger
Interfaces (CTI). Certain ways of interconnection are common
and these are supported by the debugger e.g. to cause a
synchronous halt of multiple cores.
NONE: The CTI is not used by the debugger.
ARMV1: This mode is used for ARM7/9/11 cores which support
synchronous halt, only.
ARMPostInit: Like ARMV1 but the CTI connection differs from the
ARM recommendation.
OMAP3: This mode is not yet used.
TMS570: Used for a certain CTI connection used on a TMS570
derivative.
CortexV1: The CTI will be configured for synchronous start and
stop via CTI. It assumes the connection of DBGRQ, DBGACK,
DBGRESTART signals to CTI are done as recommended by
ARM. The CTIBASE must be notified. “CortexV1” is the default
value if a Cortex-R/-A core is selected and the CTIBASE is
notified.
QV1: This mode is not yet used.
DTM.Type [None | Generic] Informs the debugger that a customer proprietary Data Trace
Message (DTM) module is available. This causes the debugger
to consider this source when capturing common trace data.
Trace data from this module will be recorded and can be
accessed later but the unknown DTM module itself will not be
controlled by the debugger.
ETB.Size <size> Specifies the size of the Embedded Trace Buffer. The ETB size
can normally be read out by the debugger. Therefore this
command is only needed if this can not be done for any reason.
FUNNEL.Name <string> It is possible that different funnels have the same address for
their control register block. This assumes they are on different
buses and for different cores. In this case it is needed to give the
funnel different names to differentiate them.