RealView ® ICEand RealView Trace User Guide

Version 3.2

Table of Contents

About this document
Intended audience
Typographical conventions
Timing diagram conventions
Further reading
Feedback on RealView ICE and RealViewTrace
Feedback on this document
1. Introduction
1.1. About RealView ICE and RealView Trace
1.1.1. RealView ICE product contents
1.1.2. RealView Trace product contents
1.1.3. RealView Trace 2 product contents
1.2. Availability and compatibility
1.3. Introduction to EmbeddedICE logicand debug extensions
1.3.1. Debug extensions to the ARM core
1.3.2. The EmbeddedICE logic
1.3.3. How the EmbeddedICE debug architecturediffers from a debug monitor
1.4. Introduction to the RealView ICE components
1.4.1. The RealView ICE run control unit
1.4.2. The RealView ICE firmware
1.4.3. The RealView ICE host software
1.5. Introduction to GDB debugging withRealView ICE
1.5.1. GDB availability and compatibility
1.5.2. Supported debug host platforms
1.5.3. Recommended applications for debuggingwith GDB
2. Getting Started
2.1. System requirements
2.1.1. Host software requirements
2.1.2. Host hardware requirements
2.1.3. Target hardware requirements
2.2. Connecting the RealView ICE hardware
2.2.1. What you require
2.2.2. Connection instructions
2.2.3. Using nonstandard connectors
2.2.4. Hot plugging and unplugging the JTAGcable
2.3. Using RealView ICE and RealView Trace
3. Configuring RealView ICE Networking
3.1. Determining the correct network settings
3.1.1. Not using DHCP
3.1.2. Using DHCP
3.2. Starting and exiting the RealViewICE Config IP application
3.2.1. Starting the RealView ICE Config IPapplication
3.2.2. Exiting the RealView ICE Config IPapplication
3.3. Configuring the network settings
3.3.1. Configuring by scanning all run controlunits
3.3.2. Configuring using an Ethernet address
3.3.3. Configuring for connection with anEthernet cross-over cable
3.4. Restarting your RealView ICE run controlunit
4. Configuring a RealView ICE Connection
4.1. Changes to RealView Debugger
4.2. Using the RVConfig dialog
4.2.1. Opening the RVConfig dialog box fromRealView Debugger
4.2.2. Opening the RVConfig dialog box —standalone method
4.2.3. Connecting to a RealView ICE unit
4.2.4. Configuring a scan chain
4.2.5. CoreSight system configuration
4.2.6. Configuring CoreSight cores
4.2.7. Configuring devices
4.2.8. Advanced configuration
4.2.9. Saving your changes
4.2.10. Disconnecting from a RealView ICEunit
4.3. Connecting RealView Debugger to atarget using RealView ICE
4.4. Using the Debug tab of the RealViewDebugger Register pane
4.5. Configuration of static IP addressesfor virtual Ethernet
5. Debugging with RealView ICE
5.1. Post-mortem debugging
5.2. Semihosting
5.2.1. Enabling semihosting
5.2.2. Adding an application SVC handlerwhen using RealView ICE
5.2.3. Cortex-M3 semihosting
5.3. Breakpoints
5.3.1. Hardware Breakpoints
5.3.2. Software instruction breakpoints
5.3.3. Processor exceptions
5.3.4. Breakpoints and the program counter
5.3.5. Interaction with RealView Debugger
5.3.6. Problems setting breakpoints
5.4. Cached data
5.4.1. Debugging cores with caches enabled
5.5. Debugging applications in ROM
5.5.1. Debugging from reset
5.5.2. Debugging systems with ROM at theexception vector
6. Using RealView Trace and RealView Trace 2
6.1. About RealView Trace
6.1.1. The RealView Trace product
6.1.2. Front panel layout
6.1.3. Capture rates
6.1.4. Availability and compatibility
6.2. System requirements
6.2.1. Host software requirements
6.2.2. Host hardware requirements
6.2.3. Target hardware requirements
6.3. Installing RealView Trace
6.4. Connecting the RealView Trace hardware
6.4.1. What you require
6.4.2. Connection instructions
6.5. Configuring trace lines
6.6. Configuring RealView Debugger fortrace capture
7. Managing the RealView ICE Software
7.1. Starting the RVI Update application
7.2. Connecting to a RealView ICE unit
7.2.1. Scanning for RealView ICE units
7.2.2. Identifying your RealView ICE unit
7.2.3. Viewing the installedcomponents
7.2.4. RVI Update tasks
7.2.5. Disconnecting from the RealView ICEunit
7.2.6. Exiting the RVI Update application
7.2.7. Troubleshooting RealView ICE connections
7.3. Viewing software version numbers
7.3.1. Version information dialog box components
7.3.2. Saving the version information toa file
7.4. Installing an update or patch
7.4.1. Procedure for installing an updateor patch
7.4.2. Procedure for upgrading the LVDS probe
7.4.3. Troubleshooting firmware upgrade installations
7.5. Restarting the RealView ICE run controlunit
8. Configuring RealView ICE for GDB
8.1. About using RealView ICE for debuggingwith GDB
8.1.1. Features supported when debuggingwith GDB
8.1.2. Features not supportedwhen debugging with GDB
8.1.3. RealView ICE TCP/IP ports used
8.1.4. Building for standalone target platforms
8.2. Methods of connecting from remoteGDB sessions
8.2.1. Summary of the connection methodsfor each debugging mode
8.2.2. Connections to a target without built-inGDB support (RVI-GDB)
8.2.3. Connections to a targetwith a GDB stub (Target-GDB)
8.2.4. Connections to a target GDB stub usingVirtual Ethernet/TTY mode (Target-GDB-Virtual Ethernet)
8.2.5. Connections to a target OS using gdbserver(GDBserver)
8.2.6. Connections to a target OS using NFS(GDB-NFS)
8.3. Preparing RealView ICE for remoteGDB connections
8.3.1. About connecting to targets throughRealView ICE
8.3.2. Multicore debugging
8.3.3. DCC modes
8.4. Loading and booting a complete system
8.4.1. Requirements for using the rviloadutility
8.4.2. rviload command syntax
8.4.3. Using the rviload utilityfrom a Cygwin bash or Red Hat Linux shell
8.5. Multiprocessor debugging with GDBand RealView ICE
8.5.1. How connections to multiple processorsare allocated
8.5.2. Considerations when debugging multipletargets with GDB
8.6. The Eclipse Plug-in
8.6.1. Load using an existing Eclipse target configuration
8.6.2. Launching Eclipse in Red Hat Linux
9. System Design Guidelines
9.1. About the system design guidelines
9.2. System design
9.2.1. Using adaptive clocking to synchronizethe JTAG port
9.2.2. Reset signals
9.3. ASIC guidelines
9.3.1. ICs containing multiple devices
9.3.2. ICs containing CoreSight debug technology
9.3.3. Boundary scan test vectors
9.4. PCB guidelines
9.4.1. PCB connections
9.4.2. Target interface logic levels
9.5. JTAG signal integrity and maximumcable lengths
9.6. Compatibility with EmbeddedICE interfacetarget connectors
9.6.1. Adaptor to connect a RealView ICErun control unit to 14-way connectors
A. JTAG Interface Connections
A.1. JTAG interface pinouts
A.2. JTAG interface signals
A.2.1. JTAG interface signal details
A.3. JTAG port timing characteristics
B. User I/O Connections
B.1. The RealView ICE User I/O connector
C. RealView Trace Interface Connections
C.1. RealView Trace front panel components
C.1.1. LEDs
C.1.2. RealView Trace probe connectors
C.2. Trace signals
C.2.1. Signal levels
C.2.2. Clock frequency
C.2.3. Switching thresholds
C.2.4. Hot plugging
D. Designing the Target Board for Tracing
D.1. Overview of high-speed design
D.1.1. Avoid stubs
D.1.2. Minimize signal skew (balancing PCB track lengths)
D.1.3. Minimize crosstalk
D.1.4. Use impedance matching and termination
D.2. Termination
D.2.1. Example
D.2.2. Termination options
D.2.3. Rules for series terminators
D.2.4. PCB track impedance
D.3. Probes, dimensions and keep out areas
D.3.1. Delayed clock probe
D.3.2. Dual-Mictor trace probe
D.3.3. Dual-Mictor trace probe characteristics
D.4. Signal requirements
D.4.1. Data setup and hold
D.4.2. Switching Thresholds
D.4.3. Hot plugging
D.5. Probe modeling
E. Hardware Variants
E.1. RealView ICE hardware
E.1.1. End panel elements
E.1.2. Lead-free LVDS probe
F. Serial Wire Debug
F.1. Serial Wire Debug
F.1.1. Target interface
F.1.2. SWD timing requirements

List of Figures

1. Key to timing diagram conventions
1.1. Ports for connecting to the hostcomputer
1.2. Ports for connecting to the targethardware
2.1. Connecting the RealView ICE hardware
3.1. The RealView ICE Config IP application
3.2. Error message when another programis browsing
3.3. Error message when no USB devicespresent
3.4. Error when other connections areactive
3.5. The identification LEDs
3.6. The Configure RealView ICE devicedialog box
3.7. The Configure new RealView ICE devicedialog box
4.1. RVConfig dialog box
4.2. RVConfig application
4.3. Choose a file to open dialog
4.4. RVConfig dialog box
4.5. The RVConfig dialog box showing availableunits
4.6. The Identification LEDs
4.7. Error message when another programis browsing
4.8. Error message when no USB devicespresent
4.9. Displaying the scan chain controls
4.10. Auto Detect Scanchain
4.11. Error shown when unpowered devicesare detected
4.12. Error shown when no devices are detected
4.13. Error shown when there is no communicationwith RealView ICE
4.14. The Add Device dialog box
4.15. The Device Properties dialog box
4.16. The scan chain JTAG Clock Speed controls
4.17. JTAG scan chain connected to a JTAG-AP
4.18. Displaying the device controls
4.19. Displaying the advanced controls
4.20. Recommended settings for an ARM Emulatorboard
4.21. Displaying the connection controls
4.22. Warning when disconnecting with unsavedconfiguration changes
6.1. Trace system
6.2. The RealView Trace 2 data captureunit
6.3. Positioning of 16mm plastic spacers
6.4. Profile view of connected units
6.5. RealView Trace connections usingan Ethernet cable
6.6. RealView ICE connector on probe
6.7. RealView Trace 2 run control unitconnections
6.8. Trace node in RVConfig dialog
7.1. RVI Update application
7.2. RVI Update application showing availableunits
7.3. The identification LEDs
7.4. RVI Update application showing installedcomponents
7.5. Error message when another programis browsing
7.6. Error message when no USB devicespresent
7.7. Error when other connections areactive
7.8. Version information
7.9. Selecting the component file to install
7.10. Confirming that you want to installthe component file
7.11. Error message
7.12. Error when using an incompatibleversion of hardware
7.13. Progress during an installation
7.14. Progress when rebooting during aninstallation
7.15. Message showing a successful installation
7.16. Progress during probe update
7.17. Error when installing a patch touninstalled software
7.18. Message when installing a patch thathas no new components
7.19. Error before data has been writtento compact flash
7.20. Error during writing to compact flash
8.1. RVI-GDB connections
8.2. Target-GDB connections
8.3. Target-GDB-Virtual Ethernet connections
8.4. GDBserver connections
8.5. GDB-NFS connections
8.6. Debug dialog
8.7. Connection option field
9.1. Basic JTAG port synchronizer
9.2. Timing diagram for the Basic JTAGsynchronizer in Figure 9.1
9.3. JTAG port synchronizer for singlerising-edge D-type ASIC design rules
9.4. Timing diagram for the D-type JTAGsynchronizer in Figure 9.3
9.5. Example reset circuit logic
9.6. Example reset circuit using powersupply monitor ICs
9.7. TAP Controllers serially chainedwithin an ASIC
9.8. Typical PCB connections
9.9. Target interface logic levels
A.1. JTAG interface pinout
A.2. JTAG port timing diagram
B.1. User I/O pin connections
C.1. RealView Trace front panel layoutfor RVT 2
C.2. RealView Trace front panel layout forRVT
C.3. Clock waveforms
D.1. Track impedance
D.2. Probe dimensions
D.3. Delayed clock probe showing locationof switches
D.4. 32-bit dual-Mictor trace probe
D.5. RealView Trace 2 unit connections
D.6. Dual-Mictor probe with extender cables
D.7. Dual-Mictor pitch dimensions
D.8. Data waveforms
E.1. RVI v3.2 host computer ports endpanel
E.2. Pre-v3.0 host computer ports endpanel
E.3. RVI v3.2 target hardware portsend panel
E.4. Replaced target hardware ports endpanel
E.5. Lead-free LVDS probe LEDs and dimensions
F.1. SWD timing diagrams


Words and logos marked with ® or ™ are registered trademarks or trademarksof ARM Limited in the EU and other countries, except as otherwisestated below in this proprietary notice. Other brands and names mentionedherein may be the trademarks of their respective owners.

Neither the whole nor any part of the information containedin, or the product described in, this document may be adapted orreproduced in any material form except with the prior written permissionof the copyright holder.

The product described in this document is subject to continuousdevelopments and improvements. All particulars of the product andits use contained in this document are given by ARM in good faith.However, all warranties implied or expressed, including but notlimited to implied warranties of merchantability, or fitness forpurpose, are excluded.

This document is intended only to assist the reader in theuse of the product. ARM Limited shall not be liable for any lossor damage arising from the use of any information in this document,or any error or omission in such information, or any incorrect useof the product.

Where the term ARM is used it means “ARM or any of its subsidiariesas appropriate”.

This product includes software developed by the Apache SoftwareFoundation (see ).

Confidentiality Status

This document is Non-Confidential. The right to use, copyand disclose this document may be subject to license restrictionsin accordance with the terms of the agreement entered into by ARMand the party that ARM delivered this document to.

Product Status

The information in this document is final, that is for a developedproduct.

Conformance Notices

This section contains conformance notices.

Federal Communications Commission Notice

This device is test equipment and consequently is exempt frompart 15 of the FCC Rules under section 15.103 (c).

CE Declaration of Conformity

The system should be powered down when not in use.

It is recommended that ESD precautions be taken when handlingRealView ICE and RealView Trace equipment.

The RealView ICE and RealView Trace modules generate, use,and can radiate radio frequency energy and may cause harmful interferenceto radio communications. However, there is no guarantee that interference willnot occur in a particular installation. If this equipment causesharmful interference to radio or television reception, which canbe determined by turning the equipment off or on, you are encouragedto try to correct the interference by one or more of the followingmeasures:

  • ensureattached cables do not lie across the card

  • reorient the receiving antenna

  • increase the distance between the equipment andthe receiver

  • connect the equipment into an outlet on a circuitdifferent from that to which the receiver is connected

  • consult the dealer or an experienced radio/TV technicianfor help


It is recommended that wherever possible shielded interfacecables be used.

Revision History
Revision A December2002 First release
Revision B January2004 Updated for RealView ICE v1.1
Revision C August2004 Updated for RealView ICE v1.2
Revision D May2005 Updated for RealView ICE v1.4
Revision E November2005 Updated for RealView ICE v1.5
Revision F June2006 Updated for RealView ICE v3.0
Revision G May2007 Updated for RealView ICE v3.1
Revision H October 2007 Updatedfor RealView ICE v3.2
Copyright © 2002, 2004-2007 ARM Limited. All rights reserved. ARM DUI 0155H