
R0E417250MCU00 User
’s Manual
R20UT3587EJ0302 Rev.3.02
Page 105 of 232
Sep.01. 21
5.6 Using Software Breakpoints
5.6.1
Using Software Breakpoints
In a software break, the instruction code at a specified address is replaced with a BRK instruction, which causes the user
program to stop running by generating a BRK interrupt. In that sense, this is a pre-execution break function.
Up to 4096 breakpoints can be set.
If multiple software breakpoints are set, program execution breaks when it arrives at any of the breakpoints reached.
(1) When stopped at a software breakpoint
When the program you have created is run and arrives at an address you have set as a software breakpoint, the program stops
and the message “Software Break” is displayed on the Debug sheet of the Output window. At this time, the Editor or
Disassembly window is updated, and the position where the program has stopped is marked with an arrow [
] in the S/W
Breakpoints column.
CAUTION
When a break occurs, the program stops immediately before executing the line or instruction at which the software breakpoint
is set. If Go or Step is selected after the program has stopped at the breakpoint, the program restarts from the line marked with
an arrow.
5.6.2
Adding and Removing Software Breakpoints
Select either of the following ways to add or remove software breakpoints.
- From the Editor or Disassembly window
- From the Breakpoints dialog box (only for removal)
- From the command line