
MMDSP Debugger
18
©1989-2019 Lauterbach GmbH
SYStem.CONFIG.CORE
Assign core to TRACE32 instance
Default
coreindex
: depends on the CPU, usually 1. for generic chips
Default
chipindex
: derived from CORE= parameter of the configuration file (config.t32). The CORE
parameter is defined according to the start order of the GUI in T32Start with ascending values.
To provide proper interaction between different parts of the debugger the systems topology must be mapped
to the debuggers topology model. The debugger model abstracts chips and sub-cores of these chips. Every
GUI must be connect to one unused core entry in the debugger topology model. Once the
is
selected a generic chip or none generic chip is created at the default
chipindex.
None Generic Chips
None generic chips have a fixed amount of sub-cores with a fixed CPU type.
First all cores have successive chip numbers at their GUIs. Therefore you have to assign the coreindex and
the chipindex for every core. Usually the debugger does not need further information to access cores in
none generic chips, once the setup is correct.
Generic Chips
Generic chips can accommodate an arbitrary amount of sub-cores. The debugger still needs information
how to connect to the individual cores e.g. by setting the JTAG chain coordinates.
Start-up Process
The debug system must not have an invalid state where a GUI is connected to a wrong core type of a none
generic chip, two GUI are connected to the same coordinate or a GUI is not connected to a core. The initial
state of the system is value since every new GUI uses a new
chipindex
according to its CORE= parameter
of the configuration file (config.t32). If the system contains fewer chips than initially assumed, the chips must
be merged by calling
SYStem.CONFIG.CORE
.
Format:
SYStem.CONFIG.CORE
<coreindex>
<chipindex>
SYStem.MultiCore.CORE
<coreindex>
<chipindex>
(deprecated)
<chipindex>
:
1
…
i
<coreindex>
:
1
…
k