ARM ARM DUI 0137A Manuale Utente
Debugging with RMHost
32
Copyright © 2000 ARM Limited. All rights reserved.. All rights reserved.
ARM DUI 0137A
3.1
Debugging with RMHost
When connected to RMHost, the AXD user interface is identical to that when connected
to other debug targets such as Multi-ICE. (For details on connecting to RMHost, see
Chapter 2 Connecting to RMHost.) You can display, for example, memory windows,
register contents, and variables.
to other debug targets such as Multi-ICE. (For details on connecting to RMHost, see
Chapter 2 Connecting to RMHost.) You can display, for example, memory windows,
register contents, and variables.
This section describes the standard debugging features you can use when connected to
RMHost, and how to use these features when connected to RMHost as the debug target:
RMHost, and how to use these features when connected to RMHost as the debug target:
•
•
•
•
•
•
•
•
Note
The debugging features supported by RMHost are supported by any debugger that is
RDI 1.5.1-compliant (see RMHost requirements on page 14).
RDI 1.5.1-compliant (see RMHost requirements on page 14).
3.1.1
Nonstop debug
When you are debugging with Multi-ICE, for example, and you stop the target using
breakpoints, the processor is halted, and no application can run in the foreground or
background.
breakpoints, the processor is halted, and no application can run in the foreground or
background.
Nonstop debug, which is available when connected to RMHost, refers to when the
foreground application stops when a breakpoint is hit, and the processor continues to
run. This allows system-critical tasks, such as IRQ and FIQ handlers, to continue to run
as you debug your foreground application.
foreground application stops when a breakpoint is hit, and the processor continues to
run. This allows system-critical tasks, such as IRQ and FIQ handlers, to continue to run
as you debug your foreground application.