Use hardware breakpoints to set execution or data breaks, or where your code is stored in ROM or Flash (see Breakpoints and memory map locations). The facilities available depend on the current debug target, that is both the target processor and the target vehicle.

To set hardware breakpoints, you must be connected to a debug target that supports these features, such as an ARM processor with EmbeddedICE logic (for example, an ARM966E-S), or simulator software that supports this feature (for example, RealView Simulator Broker connections to RVISS).

Menu options related to hardware breakpoints are grayed out if your target cannot support them. Similarly, RealView Debugger displays a message if you select an option from a drop-down list box that is not supported by your debug target. Check your hardware characteristics (see Viewing your hardware breakpoint support), and your vendor-supplied documentation, to determine the level of support for hardware breakpoints.

This section includes: