Qorivva MPC5xxx/SPC5xx Debugger and NEXUS Trace
41
©1989-2021 Lauterbach GmbH
It is also possible to show more than one core context at the same time, using the option /Core
<logical_core_index>
. All windows with core-dependent information support this option.
Example scripts for SMP debugging can be found in the demo folder, e.g.
•
~~/demo/powerpc/hardware/mpc56xx/mpc5643l-dualcore/smp_demo.cmm
•
~~/demo/powerpc/hardware/mpc56xx/mpc5676r-dualcore/smp_demo.cmm
•
~~/demo/powerpc/hardware/spc56xx/spc56ap/smp_demo.cmm
Further demo scripts available for download and upon request.
AMP Debugging
In AMP debugging mode, a separate PowerView instance is started for each core. The individual instances
are completely independent of each other, but it is possible to synchronize run-control and system mode
changes (see
).
An easy way to start multiple PowerView instances is to use
T32Start
. It is also possible to start further
instances from a PRACTICE script.
The following steps demonstrate the setup for AMP debugging, assuming that the application is already
programmed to FLASH:
1.
Select the target processor, or use automatic CPU detection.
2.
Assign target cores to the individual instances. Look up the core-index of each core in
Use either
SYStem.CONFIG.CORE
<core_index>
<chip_index>
<core_index>
. The parameter
<chip_index>
must be the same for all cores on the same chip.
3.
SYStem.CONFIG.SLAVE must be OFF for the core that starts running right form reset. Set to
ON for all other cores (that are released later by the first core).
Register /CORE 0
Register /CORE 1
List /CORE 0
List /CORE 1
;core_0 setup script:
;core_1 setup script:
SYStem.CPU MPC5517
SYStem.CPU MPC5517
SYStem.CONFIG.CORE 1. 1.
SYStem.CONFIG.CORE 2. 1.
SYStem.CONFIG.SLAVE OFF
SYStem.CONFIG.SLAVE ON
