With memory mapping enabled, RealView Debugger sets a breakpoint based on the access rule for the memory at the chosen location. Table 4.1 shows the different types of location that you can define in a memory map with RealView Debugger, and the type of breakpoint that RealView Debugger sets by default.

If you have to, you can set a hardware breakpoint in RAM. To do this, you must use one of the methods described in Setting hardware breakpoints explicitly.

RealView Debugger cannot determine the type of default breakpoint to set in WOM memory, and displays the Set Address/Data Breakpoint dialog box (see Displaying the Set Address/Data Breakpoint dialog box). This dialog box is also displayed if an error occurs when you attempt to set a breakpoint.

If you attempt to set a software breakpoint at an address in Flash, ROM, NOM, or Auto memory, a hardware breakpoint is set instead. If the target vehicle informs RealView Debugger that a hardware breakpoint is being used, RealView Debugger warns you that this has happened:

Warning: Failed to set Software Break - used Hardware Break instead (read-only memory?).

For more details about memory mapping, see Chapter 5 Memory Mapping.