PPC600 Family Debugger | 44
©
1989-2022 Lauterbach
For an explanation of the TRACE32 concept of address spaces (zone spaces, MMU spaces, and machine
spaces), see “TRACE32 Glossary” (glossary.pdf).
Examples:
SYStem.Option.NoDebugStop Disable JTAG stop on debug events
Default: OFF.
On-chip debug events Breakpoint (instruction/data address), single step and branch trace can be configured
to cause one of two actions. If a JTAG debugger is used, the CPU is configured to stop for JTAG upon these
debug events.
If this option is set to ON, the CPU will be configured to not stop for JTAG, but to enter the breakpoint/trace
interrupt, like it does when no JTAG debugger is used.
Enable this option if the CPU should not stop for JTAG on debug events, in order to allow a target application
to use debug events. Typical usages for this option are run-mode debugging (e.g. with gdbserver) or setting
up the system for a branch trace via LOGGER (trace data in target RAM) or INTEGRATOR.
NOTE: SYStem.Option.MMUSPACES should not be set to ON if only one translation
table is used on the target.
If a debug session requires space IDs, you must observe the following
sequence of steps:
1. Activate SYStem.Option.MMUSPACES.
2. Load the symbols with Data.LOAD.
Otherwise, the internal symbol database of TRACE32 may become
inconsistent.
;Dump logical address 0xC00208A belonging to memory space with
;space ID 0x012A:
Data.dump D:0x012A:0xC00208A
;Dump logical address 0xC00208A belonging to memory space with
;space ID 0x0203:
Data.dump D:0x0203:0xC00208A
Format: SYStem.Option.NoDebugStop [ON | OFF]
To Next Page
Loading...
Need help?
General
