| |||
| Home > Debug > Halting debug-mode debugging > Programming debug events | |||
In Halting debug-mode debugging you can program the following debug events:
For setting breakpoints, watchpoints, and vector catch debug events when in Halting debug-mode, the debug host has to use the same CP14 debug registers and the same sequence of operations as in Monitor debug-mode debugging (see Setting breakpoints, watchpoints, and vector catch debug events). The only difference is that the CP14 debug registers are accessed using the DBGTAP scan chains, see The DBGTAP port and debug registers.
A DBGTAP debugger can access the CP14 debug registers whether the processor is in Debug state or not, so these debug events can be programmed when the processor is in ARM state or, Thumb state.
To set a software breakpoint, the DBGTAP debugger must perform the same steps as the monitor target (described in Setting breakpoints, watchpoints, and vector catch debug events). The difference is that CP14 debug registers are accessed using the DBGTAP scan chains, see Chapter 14 Debug Test Access Port.
See Debug sequences for memory access sequences using the ARM1156T2-S Debug Test Access Port.