Debugging with RMHost
Memory map forbids reading from location
Either you or the debugger attempted to read a location, but the memory map on the target forbids the reading of locations in that region.
Memory map forbids setting of breakpoint/watchpoint
Either you or the debugger attempted to set a breakpoint or watchpoint, but the memory map on the target forbids the setting of watchpoints or breakpoints on that region. (The debugger might attempt to set a breakpoint when
Note
For details on memory maps, see the ARM RMTarget Integration Guide for a description of rm_Memory in the API chapter, and the pointer to memory descriptor block in the RealMonitor protocol chapter.
Memory map forbids writing to location
Either you or the debugger attempted to write a location, but the memory map on the target forbids the writing of locations in that region.
Message received from target was not handled by RMHost
The RealMonitor protocol includes messages sent from the target to the controller, such as RM_Msg_HardBreak (RealMonitor has stopped at a breakpoint). This error message indicates that the target sent a message, but the controller did not understand it, and usually indicates an error in RMTarget (see the section on
RealMonitor not compatible with RDI target
The RDI target (usually
Remote target is not executing
The target processor is in debug state, and therefore, it cannot be debugged by RMHost.
RMHost buffer overflow
An internal buffer inside the RMHost controller has overflowed. As with an internal error, this error must be reported to your supplier.
ARM DUI 0137A | Copyright © 2000 ARM Limited. All rights reserved.. All rights reserved. | 39 |
