Introduction to RVI and RVT
ARM DUI 0515B Copyright © 2010 ARM. All rights reserved. 2-7
ID111810 Non-Confidential
2.6 Debug extensions to the ARM processor
The debug extensions consist of several scan chains around the processor, and some additional
signals that are used to control the behavior of the processor for debug purposes. The most
significant of these additional signals are:
BREAKPT This processor signal enables external hardware to halt processor execution for
debug purposes. When HIGH during an instruction fetch, the instruction is tagged
as breakpointed, and the processor stops if this instruction reaches the execute
stage of the pipeline.
DBGRQ This processor signal is a level-sensitive input that causes the processor to enter
debug state when the current instruction has completed.
DBGACK This processor signal is an output from the processor that goes HIGH when the
processor is in debug state so that external devices can determine the current state
of the processor.
RVI uses these, and other signals, through the debug interface of the processor, for example by
writing to the control register of the EmbeddedICE logic. For more details, see the topic that
describes the debug interface support of the ARM datasheet or technical reference manual for
your processor (for example, the ARM7TDMI (Rev 4) Technical Reference Manual).
2.6.1 See also
Concepts
EmbeddedICE debug architecture and debug monitor differences on page 2-8.
Introduction to RVI and RVT
ARM DUI 0515B Copyright © 2010 ARM. All rights reserved. 2-8
ID111810 Non-Confidential
2.7 EmbeddedICE debug architecture and debug monitor differences
A debug monitor is an application that runs on your target hardware in conjunction with your
application, and requires target resources (for example, memory, access to exception vectors,
and timers) to be available.
The EmbeddedICE debug architecture requires almost no resources. Rather than being an
application on the board, it works by using:
additional debug hardware within the processor, to enable the host to communicate with
the target
an external run control unit that buffers and translates the processor signals into something
that is usable by a host computer.
The EmbeddedICE debug architecture enables debugging to be as non-intrusive as possible:
the target being debugged requires very little special hardware to support debugging
in most cases you do not have to set aside memory for debugging in the system being
debugged and you do not have to incorporate special software into the application
execution of the system being debugged is only halted when a breakpoint unit is triggered,
or you request that execution is halted.
2.7.1 See also
Concepts
Debug extensions to the ARM processor on page 2-7.
Introduction to RVI and RVT
ARM DUI 0515B Copyright © 2010 ARM. All rights reserved. 2-9
ID111810 Non-Confidential
2.8 Introduction to the RVI components
The following topics introduce the components of the RVI product, and describe how they fit
together:
The RVI debug unit on page 2-10
The RVI firmware on page 2-15
The RVI host software on page 2-16.
2.8.1 See also
Concepts
About RVI and RVT on page 2-2
RVI and RVT availability and compatibility on page 2-5
Introduction to EmbeddedICE logic and debug extensions on page 2-6.
Reference
Using the Debug Hardware Configuration Utilities:
Using Trace,
../com.arm.doc.dui0498b/I999867.html

RT200-KT-0179ALF

Mfr. #:
Manufacturer:
Description:
REALVIEW TRACE 2.0
Lifecycle:
New from this manufacturer.
Delivery:
DHL FedEx Ups TNT EMS
Payment:
T/T Paypal Visa MoneyGram Western Union

Products related to this Datasheet