ARM® DSTREAM™ and RVI™ Using the Debug Hardware Configuration Utilities

Version 4.2

List of Topics

Conventions and feedback
Getting started with the debug hardware configuration utilities
About the debug hardware configuration utilities
Starting the debug hardware configuration utilities
Scanning for available debug hardware units
Identifying a debug hardware unit
Connecting to a debug hardware unit
Configuring network settings for your debug hardware unit
About configuring network settings
Determining the correct network settings
The Configure debug_hardware device dialog box
The Configure new debug_hardware device dialog box
Debug hardware unit network settings
Configuring the network settings for a debug hardware unit
Modifying the network settings for a debug hardware unit
Restarting your debug hardware unit
Managing the firmware on your debug hardware unit
About templates and firmware files
Location of the firmware files in ARM products
Viewing software version numbers
Installing a firmware update or patch release
Upgrading an LVDS probe
Restarting the debug hardware unit in RVI Update
Creating debug hardware target configurations
About creating debug hardware target configurations
Creating a debug hardware configuration file
Opening an existing debug hardware configuration file in RVConfig
Configuring a JTAG scan chain
About configuring a device list
Autoconfiguring a scan chain
Adding devices to the scan chain
Removing devices from the scan chain
Changing the order of devices on the scan chain
Select Platform dialog box
Export As Platform dialog box
Exporting a configuration to a platform file
Device Properties dialog box
Changing the properties of a device
Setting the clock speed
About adaptive clocking
Device configuration settings
Debug hardware Advanced settings
Trace configuration settings
Configuring Reset options in debug hardware
Configuring SecurCore behavior if the processor clock stops when stepping instructions
Configuring TrustZone enabled processor behavior when debug privileges are reduced
About platform detection and selection
Autodetecting a platform
Manually selecting a platform
Clearing a platform assignment from a debug hardware configuration
Adding new platforms
Adding autoconfigure support for new platforms
Configuring the debug hardware Advanced settings
Saving your changes
Disconnecting from a debug hardware unit
Configuring a target processor for virtual Ethernet
CoreSight device names and classes
Configuring CoreSight systems
About CoreSight system configuration
Reading the CoreSight ROM table
CoreSight autodetection
Autodetecting Serial Wire Debug
About trace associations
Defining CoreSight trace associations
Format of trace associations
Trace Association Editor dialog box
Setting up a CoreSight trace association file
Loading a trace association file
CoreSight topology and associations for the CoreSight DK11
CoreSight topology and associations for the Cortex-R4 FPGA
CoreSight topology and associations for the Cortex-M3 FPGA
CoreSight topology and associations for multiple trace sources
Configuring CoreSight processors
Configuring ARM7, ARM9, and ARM11 processors in CoreSight systems
Configuring CoreSight systems with multiple devices per JTAG-AP multiplexor port
Using Trace
About using trace hardware
Trace hardware capture rates
Configuring trace lines (DSTREAM and RVT2 only)
Configuring your debugger for trace capture
Debugging with your debug hardware unit
Post-mortem debugging
Adding an application SVC handler when using debug hardware
Cortex-M3 semihosting
Hardware breakpoints
Software instruction breakpoints
Processor exceptions
Breakpoints and the program counter
Interaction between breakpoint handling in the debug hardware and your debugger
Problems setting breakpoints
Strategies used by debug hardware to debug cached processors
Considerations when debugging processors with caches enabled
Debugging applications in ROM
Debugging from reset
Debugging with a simulated reset
Debugging with a reset register
Debugging with a target reset
Debugging systems with ROM at the exception vector
Configuring debug hardware for GDB
About configuring debug hardware for debugging with GDB
Feature support when debugging with GDB
Debugging modes for GDB
Debug hardware TCP/IP port numbering
DCC modes
Building for standalone target platforms
Methods of connecting from remote GDB sessions
Connection methods for each debugging mode
Connections to a target without built-in GDB support (RVI-GDB)
Connections to a target with a GDB stub (Target-GDB)
Connections to a target GDB stub using Virtual Ethernet/TTY mode (Target-GDB-Virtual Ethernet)
Connections to a target OS using gdbserver (GDBserver)
Connections to a target OS using NFS (GDB-NFS)
Preparing your debug hardware for remote GDB connections
Connecting to targets from GDB through debug hardware
Setting DCC parameters
DCC and interrupts
Loading and booting a complete system
rvigdbconfig command syntax
rviload command syntax
RVIahbload command syntax
RVIvec command syntax
Multiprocessor debugging with GDB and debug hardware
Troubleshooting your debug hardware unit
Multiple programs attempting to scan
USB server not accessible
Connection times out
Other active connections
A debug hardware unit is not listed
Auto Configure button is disabled in RVConfig
Remove button is disabled in RVConfig
Troubleshooting firmware upgrade installations
Troubleshooting autoconfigation of a scan chain

List of Figures

1. RVConfig utility
2. RVConfig utility showing debug hardware units
3. The Configure debug_hardware device dialog box
4. The Configure new debug_hardware device dialog box
5. The Configure new debug_hardware device dialog box
6. The Configure debug_hardware device dialog box
7. Version information
8. RVI Update utility
9. Firmware details
10. Selecting the component file to install
11. Confirming that you want to install the component file
12. Warning message
13. Error when using an incompatible version of hardware
14. Progress during an installation
15. Progress when rebooting during an installation
16. Message showing a successful installation
17. Progress during probe update
18. RVConfig utility
19. The scan chain controls
20. Scan chain controls
21. Scan chain schematic diagram
22. Auto Configure Scan Chain dialog box
23. The Add Device dialog box
24. Scan chain devices with tooltip feature displayed
25. Select Platform dialog box
26. Export As Platform dialog box
27. The Device Properties dialog box
28. The Device Properties dialog box
29. The scan chain speed controls
30. Automatic platform configuration
31. Platform configuration and identification
32. List of supported platforms
33. Export As platform dialog box
34. Displaying the advanced controls
35. Displaying the connection controls
36. Warning when disconnecting with unsaved configuration changes
37. Read CoreSight ROM Table option
38. Trace Association Editor dialog box
39. Edit Association dialog box
40. Trace Association Editor dialog box
41. Edit Association dialog box
42. Devices with associations
43. Trace Association Editor dialog box
44. Devices with associations
45. CoreSight system topology diagram - CoreSight DK11
46. CoreSight system topology diagram - Cortex-R4 FPGA
47. Cortex-R4 FPGA Associations
48. CoreSight system topology diagram - Cortex-M3 FPGA
49. CoreSight system topology diagram - multiple trace source system
50. CoreSight device settings for a processor
51. Scan chain connected to a JTAG-AP
52. Trace node in RVConfig
53. RVI-GDB connections
54. Target-GDB connections
55. Target-GDB-Virtual Ethernet connections
56. GDBserver connections
57. GDB-NFS connections
58. Error message when another program is scanning
59. Error message when no USB devices present
60. Error when other connections are active
61. Error when installing a patch to uninstalled software
62. Message when installing a patch that has no new components
63. Error before data has been written to compact flash
64. Error during writing to compact flash
65. Error shown when unpowered devices are detected
66. Error shown when no devices are detected
67. Error shown when there is no communication with debug hardware

Proprietary Notice

Words and logos marked with ® or ™ are registered trademarks or trademarks of ARM® in the EU and other countries, except 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.

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.

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

This product includes software developed by the Apache Software Foundation (see

Confidentiality Status

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

Product Status

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

Conformance Notices

This section contains conformance notices.

Federal Communications Commission Notice

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

Class A

Important: This is a Class A device. In residential areas, this device may cause radio interference. The user should take the necessary precautions, if appropriate.

CE Declaration of Conformity

To view this graphic, your browser must support the SVG format. Either install a browser with native support, or install an appropriate plugin such as Adobe SVG Viewer.

The system should be powered down when not in use.

It is recommended that ESD precautions be taken when handling DSTREAM, RVI, and RVT equipment.

The DSTREAM, 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. If this equipment causes harmful interference to radio or television reception, which can be determined by turning the equipment off or on, you are encouraged to try to correct the interference by one or more of the following measures:

  • ensure attached cables do not lie across the target board

  • reorient the receiving antenna

  • increase the distance between the equipment and the receiver

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

  • consult the dealer or an experienced radio/TV technician for help


It is recommended that wherever possible shielded interface cables be used.

Revision History
Revision AMay 2010First release.
Revision BNovember 2010Second Release
Revision C30 April 2011DSTREAM and RVI v4.2.1 Release
Revision D29 July 2011Update 1 for DSTREAM and RVI v4.2.1 Release
Copyright © 2010-2011 ARM. All rights reserved.ARM DUI 0498D