ARM ARM DUI 0137A manual Memory map forbids reading from location

Page 35

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 single-stepping.) For more details, see rm_MemoryMap in the API chapter of the ARM RMTarget Integration Guide.

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 target-to-host controller messages in the RealMonitor protocol chapter of the ARM RMTarget Integration Guide).

RealMonitor not compatible with RDI target

The RDI target (usually Multi-ICE) does not support the features necessary to run RMHost. Either an invalid target has been chosen, or the RDI target must be upgraded.

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

Page 34 Page 36
Image 35
Page 34 Page 36
Contents ARM RMHost User Guide ARM RMHostChapter Debugging with RMHost User GuideContents About this book on PrefaceTypographical conventions Using this bookAbout this book Intended audienceARM publications Further readingOther publications Feedback on this book FeedbackFeedback on RMHost ARM DUI 0137A About RMHost on RMHost requirements on Overview of RMHostApplication/RTOS About RMHostOverview of RMHost RMHost package RMHost requirementsConnecting to RMHost Procedure for connecting to RMHost using AXD Debuggers chapter of the Multi-ICE User Guide Configure interface dialog box Select Configure Interface from the Options menuDescribes how to do this RealMonitor Configuration dialog box Jtag controller search dialog box Deselect the the option Fetch module information from target No pc write access message CancelNo pc read access message Lines 2 AXD connection messages212 Debugging with RMHost Nonstop debug Debugging with RMHostBackground memory access Nonstop startup CPU register accessSemihosting ProfilingData messaging Debugging with RMHost RDI Error messagesTarget does not include an ARM processor Memory map forbids reading from location RMHost could not load the specified Jtag controller Yes Other messages from RMHost312 Asic Using RMHost with Trace Debug ToolsSelect Debugger Internals from the System Views menu Configuring AXD to enable tracing with RMHostPerformance of RMHost with TDT Rmoptsdminfo IndexRmoptdatalogging Rmoptgetpc
Top Page Image Contents