Skip to main content

IAR Embedded Workbench for RISC-V 3.40

GDB Server: Breakpoints

In this section:

The Breakpoints options specify the breakpoint behavior for the C-SPY GDB Server driver.

WTD_GDBServer_Bkpts_RISCV_01.png
Default breakpoint type

Selects the type of breakpoint resource to be used when setting a breakpoint. Choose between:

Auto

Uses a software breakpoint. If this is not possible, a hardware breakpoint will be used. The debugger will use read/write sequences to test for RAM—in that case, a software breakpoint will be used.

Hardware

Uses hardware breakpoints. If it is not possible, no breakpoint will be set.

Software

Uses software breakpoints. If it is not possible, no breakpoint will be set.

Restore software breakpoints at

Restores software breakpoints that were overwritten during system startup.

This can be useful if you have an application that is copied to RAM during startup and is then executing in RAM. This can, for example, be the case if you use the initialize by copy linker directive for code in the linker configuration file.

In this case, all breakpoints will be destroyed during the RAM copying when the C-SPY debugger starts. By using the Restore software breakpoints at option, C-SPY will restore the destroyed breakpoints.

Use the text field to specify the location in your application at which point you want C-SPY to restore the breakpoints. The default location is the label _call_main.