ARM ARM DUI 0137A manual Profiling, Data messaging, Semihosting

Page 31

Debugging with RMHost

3.1.5Background setting and clearing of breakpoints and watchpoints

When connected to RMHost, you can set and clear breakpoints and watchpoints without stopping your application. You can also set and clear breakpoints and watchpoints when your application is in a stopped state.

3.1.6Profiling

RMHost supports a low-intrusion code profiling mechanism. This mechanism works only if you enabled profiling when you built RMTarget (see the build option RM_OPT_GETPC in the building chapter of the ARM RMTarget Integration Guide). For details on how sample-based profiling is performed by the GetPC command, see the description of GetPC in the RealMonitor protocol chapter of the ARM RMTarget Integration Guide.

For details on code profiling using AXD, see the AXD facilities chapter of the AXD and armsd Debuggers Guide.

Note

The profiling interval specified by the debugger is ignored by RMHost. In AXD, the interval is specified in the Load Image dialog box.

3.1.7Data messaging

Your application can use RealMonitor to buffer and send messages to the debugger. RMHost passes these messages to the Debug Comms Channel processor view in AXD. This feature works only if you have enabled data messaging when you built RMTarget (see the build option RM_OPT_DATALOGGING in the building chapter of the ARM RMTarget Integration Guide).

For details on the Debug Comms Channel processor view, see the AXD facilities chapter of the AXD and armsd Debuggers Guide.

3.1.8Semihosting

RMHost supports the use of the ARM semihosting interface. This support works only if you have enabled the SWI handler when you built RMTarget (see the build option RM_OPT_SEMIHOSTING in the building chapter of the ARM RMTarget Integration Guide).

If you are using semihosting, and you stop your application, you might receive the following message:

Semihosting write call interrupted (data will be lost)

ARM DUI 0137A

Copyright © 2000 ARM Limited. All rights reserved.. All rights reserved.

35

Page 30 Page 32
Image 31
Page 30 Page 32
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 RMHost FeedbackFeedback on this book 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 accessData messaging ProfilingSemihosting 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 ToolsPerformance of RMHost with TDT Configuring AXD to enable tracing with RMHostSelect Debugger Internals from the System Views menu Rmoptsdminfo IndexRmoptdatalogging Rmoptgetpc
Top Page Image Contents