Filter
Top Products
Debugging with RMHost
ARM DUI 0137A Copyright © 2000 ARM Limited. All rights reserved.. All rights reserved. 35
3.1.5 Background 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.6 Profiling
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.7 Data 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.8 Semihosting
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)