bdiGDB for BDI2000 (PowerPC 7440/7450/86xx) User Manual 24
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
WORKSPACE address The BDI needs a workspace of 256 bytes in target RAM for code sequenc-
es to flush the data cache and to access L3 private memory. See also
DCACHE and L3PM configuration parameter. If no workspace is defined,
DCACHE is not flused and you cannot access L3 private memory.
address the address of the RAM area
Example: WORKSPACE 0x00000000
BREAKMODE mode [V] This parameter defines how GDB requested breakpoints are implement-
ed. The current mode can also be changed via the Telnet interface.
The V option forces the setting of the IABR[TE] / DABT[BT] bit.
SOFT This is the normal mode. Breakpoints are implemented
by replacing code with a TRAP instruction.
HARD In this mode, the PPC breakpoint hardware is used.
Only 1 breakpoint at a time is supported (IABR).
Example: BREAKMODE HARD
STEPMODE mode This parameter defines how single step (instruction step) is implemented.
The alternate step mode (HWBP) may be useful when stepping instruc-
tions that causes a TLB miss exception.
TRACE This is the default mode. Single step is implemented by
setting the SE bit in MSR.
HWBP In this mode, a hardware breakpoint on the next instruc-
tion is used to implement single stepping.
Example: STEPMODE HWBP
VECTOR CATCH When this line is present, the BDI catches all unhandled exceptions.
Catching exceptions is only possible if the memory at address
0x00000000 to 0x00001FFF is writable.
Example: VECTOR CATCH ; catch unhandled exception
*DCACHE mode This parameter defines if the BDI flushes the caches before it accesses
memory. If the BDI does not flush the caches, it executes L1/L2 cache co-
herent memory accesses. If the L1/L2 cache is enabled and the appropri-
ate data is valid in the cache, data is read from the cache. For a write
access, the cache is updated and the data also written to external memo-
ry. If there is an enabled L3 cache, flushing the data cache is recommend-
ed. Otherwise the debugger may display wrong data and working with
software breakpoints may also fail. The following modes are supported:
NOFLUSH The caches are not flushed. L1/L2 cache coherent
memory accesses are used. Recommended if there is
no enabled L3 cache in the system.
FLUSH Before the BDI accesses any memory, the caches are
flushed and only external memory is accessed. This
mode needs a valid workspace for the flush code.
Example: DCACHE NOFLUSH ; do not flush caches
To Next Page
Loading...
