C5000 Debugger | 45
©
1989-2022
Lauterbach
…
PORT
<port>
Informs the debugger about which trace source is connected to
which input port of which funnel. A CoreSight trace funnel
provides 8 input ports (port 0-7) to combine the data of various
trace sources to a common trace stream.
Example
: SYStem.CONFIG STMFUNNEL2PORT 3
Meaning: The System Trace Module (STM) is connected to input
port #3 on FUNNEL2.
On an SMP debug session some of these commands can have a
list of
<port>
parameter.
In case there are dedicated funnels for the ETB and the TPIU
their base addresses are specified by ETBFUNNELBASE,
TPIUFUNNELBASE respectively. And the funnel port number for
the ETM are declared by ETMETBFUNNELPORT,
ETMTPIUFUNNELPORT respectively.
TRACE... stands for the ADTF trace source module.
For a list of possible components including a short description
see
Components and Available Commands
CTICONFIG
<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-A/R core is selected and the CTIBASE is
notified.
QV1: This mode is not yet used.
TIOCPTYPE
<type>
Specifies the type of the OCP module from Texas Instruments
(TI).
view
Opens a window showing most of the SYStem.CONFIG settings
and allows to modify them.