Breakpoints in the C-SPY hardware debugger drivers
Using the C-SPY drivers for hardware debugger systems you can set various breakpoint types. If possible, the debugger will use software breakpoints for the breakpoints you set, unless you explicitly set a code hardware breakpoint. However, software breakpoints are not available for the OCD driver when using an S1 core. The amount of code hardware breakpoints you can set is limited and depends on the number of hardware breakpoints available on the target system.
This table summarizes the characteristics of breakpoints for the different target systems:
C-SPY hardware debugger driver | Code and Log breakpoints | Trace breakpoints | Data breakpoints |
|---|---|---|---|
The OCD driver | |||
using hardware breakpoints | Device-specific | Device-specific | Device-specific |
using software breakpoints | Unlimited | — | — |
Note
Data and Trace breakpoints can be set using the Edit Events dialog box. Code breakpoints can be set using either the Edit Events dialog box or the Code HW breakpoints dialog box.
Note
If you are using the E1, E2, E2 Lite/E2 On-Board, E20, EZ-CUBE, EZ-CUBE2, TK, or COM Port emulator, breakpoints are ignored in code during single stepping. See Breakpoints when single stepping using the OCD driver.