The following changes have been made to this document.
Change history
DateIssueChange
December 2000AFirst release
Proprietary Notice
Words and logos marked with
as otherwise stated below in this proprietary notice. Other brands and names mentioned herein may be the
trademarks of their respective owners.
Neither the whole nor any part of the information contained in, or the product described in, this document
may be adapted or reproduced in any material form except with the prior written permission of the copyright
holder.
The product described in this document is subject to continuous developments and improvements. All
particulars of the product and its use contained in this document are given by ARM in good faith. However,
all warranties implied or expressed, including but not limited to implied warranties of merchantability, or
fitness for purpose, are excluded.
®
or ™ are registered trademarks or trademarks owned by ARM Limited, except
This document is intended only to assist the reader in the use of the product. ARM Limited shall not be liable
for any loss or damage arising from the use of any information in this document, or any error or omission in
such information, or any incorrect use of the product.
This book describes how to configure the RealMonitor host controller,
RealMonitor.dll
and how to debug RealMonitor-enabled applications using RMHost. This book
documents only the host-side functionality of RealMonitor. For complete details on the
target-side functionality, and how to prepare an RealMonitor-enabled application, see
the ARM RMTarget Integration Guide.
This book is written for programmers who want to debug a time-critical application or
RTOS using RMHost. It assumes that you are familiar with the process of debugging,
and that you understand how RMTarget has been integrated into your application.
This book is organized into the following chapters:
Chapter 1 Overview of RMHost
Read this chapter for an introduction to RMHost, and for a description of
the host-side functionality of RealMonitor, which is distinct from
RMTarget. This chapter also describes the system requirements for using
RMHost.
Chapter 2 Connecting to RMHost
Read this chapter to see the procedure for connecting to the debug target
using the ARM eXtended Debugger (AXD), and for details on selecting
and configuring the RMHost controller. It also describes the connection
messages you receive in AXD when you connect to RMHost.
,
Chapter 3 Debugging with RMHost
Read this chapter for a description of the debugging features you can use,
and the debugging restrictions you must be aware of, when connected to
RMHost. It also describes all RMHost-related error messages you can see
from within the debugger. It also describes the use of RMHost with Trace Debug Tools (TDT).
Typographical conventions
The following typographical conventions are used in this book:
bold Highlights interface elements, such as menu names. Also used for
This chapter introduces RMHost. It describes the host-side functionality of ARM
RealMonitor, and how it is distinct from RMTarget. It also describes the system
requirements for using RMHost.
RMHost is the host component of RealMonitor. It allows you to perform nonstop
debugging on a RealMonitor-enabled application in a real-time environment. That is,
when using RMHost, you can perform certain debugging operations on a foreground
application while the processor continues to run (and service interrupts) in the
background.
The functionality of RMHost is contained in the RMHost controller,
RealMonitor.dll
which provides a standard Remote Debug Interface (RDI) to the debugger. The
debugger communicates with the debug target using the RMHost controller, and
communication between RMHost and RMTarget is governed by the RealMonitor
protocol. These component parts of RealMonitor, and the connection between them, are
shown in Figure 1-1.
The RMHost controller converts RDI function calls into RealMonitor protocol packets,
and uses the chosen JTAG unit to send these over the Debug Communications Channel
(DCC) of the ARM processor. Additionally, RMHost uses the signals generated by the
JTAG unit to control operation of RMTarget. For these reasons, the software that drives
the JTAG unit must comply with RDI 1.5.1rt.
You must configure the RMHost controller when you first request connection to the
target, which must already be running. You must then choose the supported JTAG unit
to be used to communicate with, and control, the target. For complete details on the
procedure for selecting and configuring the RMHost controller, see Procedure for connecting to RMHost using AXD on page 22.