Page 2
This document is intended only to assist the reader in the use of the product. ARM 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.
Page 3
It is recommended that ESD precautions be taken when handling ARM RVI and RVT equipment. The ARM RVI and RVT modules generate, use, and can radiate radio frequency energy and may cause harmful interference to radio communications. There is no guarantee that interference will not occur in a particular installation.
Highlights interface elements, such as menu names. Also used for ® emphasis in descriptive lists, where appropriate, and for ARM processor signal names. Feedback on this product If you have any comments and suggestions about this product, contact your supplier and give: •...
Page 6
ARM also welcomes general suggestions for additions and improvements. ARM periodically provides updates and corrections to its documentation on the ARM Information Center, together with knowledge articles and Frequently Asked Questions (FAQs). Other information •...
Page 7
Introduction to the RVI components on page 2-9 • The RVI debug unit on page 2-10 • RVI hardware variants - end panel elements on page 2-12 • RVI hardware variants - v2 LVDS probe on page 2-13 • The RVI firmware on page 2-15 •...
™ contain the Embedded Trace Macrocell (ETM) logic. You can use RVI and RVT or RVT2 with systems that contain one or more ARM processors. ™ RVI also supports the Embedded Trace Buffer (ETB) for capturing small amounts of trace information at high processor clock speeds.
RVI product contents The ARM RVI product comprises: • An RVI debug unit that connects to your target board over a JTAG interface and to your PC using either USB or Ethernet. • Mains cables and a power supply that powers the RVI unit.
About RVI and RVT on page 2-2 • RVI product contents on page 2-3 • RVI and RVT availability and compatibility on page 2-5 • Introduction to EmbeddedICE logic and debug extensions on page 2-6 • Introduction to the RVI components on page 2-9.
The ability to access the target hardware. • Tools to configure your debugger so that it can connect to the target through RVI. Your debugger provides the user interface items, such as register windows and disassemblers, that make it possible to debug your application.
® The EmbeddedICE logic and the ARM processor debug extensions enable RVI to debug software running on an ARM processor. The basic principles of this operation are described in the following: • Debug extensions to the ARM processor on page 2-7 •...
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).
Introduction to RVI and RVT 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 •...
Figure 2-1 Ports for connecting to the host computer The RST button is used to reset the RVI unit when required, and returns RVI to its power-up state. Using the RST button in this way does not reset the target. This button must not be confused with the Reset button that might be implemented on your target, located on the target board itself.
Page 17
The RVI unit contains an internal cooling fan that operates to control the internal temperature when necessary. The ventilation panels on the top and bottom of the RVI unit and the RVT unit must not be obscured. 2.9.1...
In units used with software ealrier than RVI v3.0, the end panel elements of the unit for the host computer port connections are arranged as shown in the following figure:...
Flicker Flicker RVI v4.0 supports the SWD debugging protocol as an alternative to JTAG. SWD can only be used with the LVDS probe, and without using the JTAG ribbon cable. The probe must be a v2 type as described, and you might have to upgrade its firmware.
Page 20
The v2 LVDS probe is supplied as standard with RVI v3.1 and later units. The probe can also be used with a RVI v3.0 unit, if you update it with a firmware patch that provides support for the v3.1 probe.
Introduction to RVI and RVT 2.12 The RVI firmware The RVI firmware is located in the RVI debug unit. It receives commands from the RVI host software and translates them into JTAG accesses. The RVI firmware contains specific sections of code for each ARM ®...
JTAG control sequences for a particular processor. The RVI software provides support for debugging on a wide range of ARM processors. To see a list of supported processors, open the RVI Update application and expand the JTAG Templates and ARM trees. A list of templates for all supported processors is displayed.
The BUS LED indicates module initialization and RVI expansion bus power. It lights up when RVI is initializing the RVT unit, and remains lit while the RVI expansion bus is powered. The BUS LED flashes on a module connected to RVI through the expansion bus if an error is detected in trying either to identify the module or to provide power to it.
The PWR LED indicates that the RVT2 unit is powered up. This is always lit when the unit is powered from its own external power supply. When RVT2 is powered by RVI, the Power LED is lit only when RVI is initializing the RVT2 unit.
Page 25
™ The following topics describe the system requirements for ARM , and how to connect the RVI hardware to your host computer and target system. The topics also describe how to use some common parts of the RVI software: •...
System requirements for using RVI and RVT Host software requirements RVI software for the host computer runs under the following operating systems: • Windows XP Professional (Service Pack 2, or later) • Windows Vista Business Edition and Windows Vista Enterprise Edition •...
• a TCP/IP connection, if remote connection to the run control unit is required. To use the RVI software on Red Hat Linux, you require the following: • a minimum specification PC with a 1GHz Pentium III class processor and 512MB of memory.
You can use the installed Update utility to find out which processors are supported by the version of RVI that you are using. To do this, start the Update utility and select Version Info... from the RVI menu. 3.3.1...
To connect the RVI run control unit to your host computer and to the target hardware: Ensure the RVI software is installed on the host computer. Connect the host computer to the RVI run control unit, using either the USB port or an Ethernet connection, as required. The following figure shows connections using both the...
Page 30
You have only to do the network configuration once. If the RVI unit is powered up with only a USB connection, it uses an IP address of 127.0.0.0. However, if a network cable is also attached, the IP address associated with the USB connection is the IP address that you have assigned to the RVI unit, or that it obtains from a Dynamic Host Configuration Protocol (DHCP) server.
Page 31
System requirements for using RVI and RVT Warning Do not obstruct the ventilation grills on the top and bottom of the RVI unit, because doing so causes the unit to overheat. 3.4.3 See also Concepts • RVI product contents on page 2-3 •...
If you are not certain of the connection standard that your target hardware uses, you must check the reference manual for the target before you connect it to the RVI run control unit. This is especially important if you are using a target that has a 14-way IDC box header, or that is not manufactured by ARM.
You might want to do this if you have a target that is operating without a RVI run control unit connected and you want to examine the target to find out why it is behaving in a particular way.
Ensure that the RVI unit is disconnected from the power supply and from the target board. Warning Failure to remove the power from the RVI unit before connecting it to the RVT unit can cause damage to the hardware and/or personal injury.
Page 35
Figure 3-3 Profile view of connected units Clip the plastic ventilation grill that you removed from the RVI unit onto the top of the RVT unit. For up to 16-bit trace port widths, connect one end of the interface cable to the 60-way trace probe connector of the RVT unit, and the other end of the cable to the trace probe.
Page 36
Power up the RVI unit and the target board. The RVT unit is powered from the RVI unit, and does not require a separate power supply. Warning Do not obstruct the ventilation grills on the top of the RVT unit or the bottom of the RVI unit, because doing so causes the units to overheat. Note You can also use the following alternative connections: •...
Page 37
3.7.3 See also Concepts • RVT and RVT2 product contents on page 2-4 Reference RVI and RVT System and Interface Design Reference: • Dual-Mictor trace probe for RVT2 on page 6-9 • Dual-Mictor trace probe characteristics on page 6-11. ®...
When you install the RVIsoftware, it adds capabilities to your debugger to enable you to configure a RVI connection using the RVConfig utility. If you have to update the RVI firmware at a later date, for example to extend the capabilities of the RVI unit, you must use the RVI Update utility.