RealView Debugger RTOS Guide: 7.1.2. More on breakpoints

7.1.2. More on breakpoints

With OS support enabled, any breakpoint can also be a conditional breakpoint. RSD breakpoints can take the same qualifiers as HSD breakpoints and it is possible to link a counter or an expression to an RSD breakpoint.

You can also set hardware breakpoints in RSD mode but the availability of such breakpoints is determined by the debug target, that is the target processor and the Debug Agent. Hardware breakpoints are not integrated with the Debug Agent and so behave the same way in both HSD and RSD mode, their effect being to stop the target. When this occurs the communications with the Debug Agent is unavailable, and so RSD becomes inactive.

Viewing breakpoint support

To see your support for breakpoints:

Select Debug → Breakpoints → Hardware → Show Break Capabilities of HW... from the Code window main menu to open an information dialog box describing the support available for your target processor.
Select Properties from the Process tab context menu to open an information dialog box describing the Debug Agent support for breakpoints.

Memory maps and breakpoints

Where the memory map is disabled, RealView Debugger always sets a software breakpoint where possible. However, if the target is running in RSD mode, RealView Debugger sets a system breakpoint.

Where the memory map is enabled, RealView Debugger sets a breakpoint based on the access rule for the memory at the chosen location:

a hardware breakpoint is set for areas of no memory (NOM), Auto, read-only (ROM), or Flash.
if the memory is write-only (WOM), or where an error is detected, RealView Debugger gives a warning and displays the Create Breakpoint dialog box for you to specify the breakpoint details.

Copyright © 2006-2011 ARM. All rights reserved.	ARM DUI 0323G
Non-Confidential	ID052111
PDF version

7.1.2. More on breakpoints

Viewing breakpoint support

Memory maps and breakpoints

See also