ARM® DS-5™ Using the Debug Hardware Configuration Utilities

Version 5

Table of Contents

About this book
Using this book
Typographic conventions
Other information
1 Getting Started with the Debug Hardware Configuration Utilities
1.1 About the debug hardware configuration utilities
1.2 About starting the debug hardware configuration utilities
1.3 Starting the Debug Hardware Config utility on Windows
1.4 Starting the Debug Hardware Config utility on Red Hat Linux
1.5 Accessing the Debug Hardware Config utility from your Debugger
1.6 Scanning for available debug hardware units
1.7 Identifying a debug hardware unit
1.8 Connecting to a debug hardware unit
2 Configuring Network Settings for your Debug Hardware Unit
2.1 About configuring network settings
2.2 Debug hardware network settings
2.3 The Configure Debug Hardware unit dialog box
2.4 The Configure new Debug Hardware unit dialog box
2.5 Debug hardware unit network settings
2.6 Configuring the network settings for a debug hardware unit
2.7 Modifying the network settings for a debug hardware unit
2.8 Restarting your debug hardware unit
2.9 Troubleshooting network settings for a debug hardware unit
3 Managing the Firmware on your Debug Hardware Unit
3.1 About templates and firmware files
3.2 Location of the firmware files in ARM® products
3.3 List of software version numbers
3.4 Saving software version information to a file
3.5 Installing a firmware update or patch release
3.6 Upgrading an LVDS probe
3.7 Restarting the debug hardware unit in RVI Update
4 Creating Debug Hardware Target Configurations
4.1 About creating debug hardware target configurations
4.1.1 Creating a debug hardware configuration file
4.1.2 Opening an existing debug hardware configuration file in Debug Hardware Config
4.2 About configuring a JTAG scan chain
4.2.1 Controls available to manage devices
4.2.2 Device context menu controls
4.2.3 Managing a platform file
4.3 About configuring a device list
4.3.1 About autoconfiguring a scan chain
4.3.2 About manually adding devices a scan chain
4.3.3 About autoconfiguring a scan chain for CoreSight™ development platforms
4.3.4 Autoconfiguring a scan chain
4.4 About the scan chain
4.4.1 Adding devices to the scan chain
4.4.2 Considerations when adding devices to a scan chain
4.4.3 Removing a device from the scan chain
4.4.4 Removing a device from the scan chain when a platform is assigned
4.4.5 Changing the order of devices on the scan chain
4.5 Select Platform dialog box
4.6 Export As Platform dialog box
4.7 Exporting a configuration to a platform file
4.8 About device properties
4.8.1 Device Properties dialog box
4.8.2 Device properties
4.9 Changing the properties of a device
4.10 About setting the clock speed
4.10.1 Setting a predefined clock speed
4.10.2 Setting a custom clock speed
4.11 About Adaptive clocking
4.12 About debug hardware device configuration settings
4.12.1 Processor device settings
4.12.2 Non-processor CoreSight™ device settings
4.12.3 Debug hardware Advanced configuration settings
4.12.4 Debug hardware Trace configuration settings
4.12.5 Debug hardware Advanced configuration reset options
4.13 Configuring SecurCore® processor behavior if the processor clock stops when stepping instructions
4.14 Errors when configuring TrustZone® enabled processor behavior when debug privileges are reduced
4.15 About platform detection and selection
4.15.1 Autodetecting a platform
4.15.2 Manually selecting a platform
4.15.3 Clearing a platform assignment from a debug hardware configuration
4.15.4 Adding new platforms
4.15.5 About adding autoconfigure support for new platforms
4.15.6 Configuring the debug hardware Advanced settings
4.15.7 Saving your changes
4.16 Disconnecting from a debug hardware unit
4.17 Configuring a target processor for virtual Ethernet
4.18 CoreSight™ device names and classes
5 Configuring CoreSight™ Systems
5.1 About CoreSight™ system configuration
5.2 Configuring CoreSight™ devices using a CoreSight ROM table
5.3 About CoreSight™ autodetection
5.4 Autodetection in Serial Wire Debug mode
5.5 Configuration items for processors in a CoreSight™ system
5.6 Configuration items available for ARM7™, ARM9™, and ARM11™ processors in a CoreSight system
5.7 Configuration items for CoreSight™ systems with multiple devices per JTAG-AP multiplexor port
6 Using Trace
6.1 About using trace hardware
6.2 Trace hardware capture rates
6.2.1 DSTREAM trace hardware capture rates
6.3 Configuring trace lines (DSTREAM unit only)
6.4 About configuring your debugger for trace capture
7 Debugging with your Debug Hardware Unit
7.1 Performing post-mortem debugging
7.2 Semihosting
7.3 About adding an application SVC handler when using debug hardware
7.4 Cortex®‑M3 semihosting
7.5 Hardware breakpoints
7.6 Software instruction breakpoints
7.7 Processor exceptions
7.8 Breakpoints and the program counter
7.9 Interaction between breakpoint handling in the debug hardware and your debugger
7.10 Problems setting breakpoints
7.11 Strategies used by debug hardware to debug cached processors
7.12 Considerations when debugging processors with caches enabled
7.13 About debugging applications in ROM
7.13.1 About debugging from reset
7.13.2 About debugging with a simulated reset
7.14 About debugging with a reset register
7.15 About debugging with a target reset
7.16 About debugging systems with ROM at the exception vector
8 Troubleshooting your Debug Hardware Unit
8.1 Situation when multiple programs are attempting to scan
8.2 The USB server is not accessible
8.3 Fixing connection time-out problems
8.4 The debug hardware unit has other active connections
8.5 Reasons why a debug hardware unit is not listed
8.6 Auto Configure button is disabled in the Debug Hardware Config utility
8.7 Remove button is disabled in the Debug Hardware Config utility
8.8 Troubleshooting firmware upgrade installations
8.8.1 Troubleshooting version problems
8.8.2 Troubleshooting errors during file operation on the host
8.9 Troubleshooting autoconfiguration of a scan chain
8.10 Log Client Utility

Release Information

Document History
Issue Date Confidentiality Change
A May 2010 Non-Confidential First release
B November 2010 Non-Confidential Second Release
C 30 April 2011 Non-Confidential DSTREAM and RVI v4.2.1 Release
D 29 July 2011 Non-Confidential Update 1 for DSTREAM and RVI v4.2.1
E 30 September 2011 Non-Confidential DSTREAM and RVI v4.4 Release
F 29 February 2012 Non-Confidential Update for DS-5 version 5.9
G 29 July 2012 Non-Confidential Update for DS-5 version 5.11
H 12 October 2012 Non-Confidential Update for DS-5 version 5.12
I 13 July 2015 Non-Confidential Update for DS-5 version 5.22
J 15 October 2015 Non-Confidential Update for DS-5 version 5.23

Non-Confidential Proprietary Notice

This document is protected by copyright and other related rights and the practice or implementation of the information contained in this document may be protected by one or more patents or pending patent applications. No part of this document may be reproduced in any form by any means without the express prior written permission of ARM. No license, express or implied, by estoppel or otherwise to any intellectual property rights is granted by this document unless specifically stated.
Your access to the information in this document is conditional upon your acceptance that you will not use or permit others to use the information for the purposes of determining whether implementations infringe any third party patents.
THIS DOCUMENT IS PROVIDED “AS IS”. ARM PROVIDES NO REPRESENTATIONS AND NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, SATISFACTORY QUALITY, NON-INFRINGEMENT OR FITNESS FOR A PARTICULAR PURPOSE WITH RESPECT TO THE DOCUMENT. For the avoidance of doubt, ARM makes no representation with respect to, and has undertaken no analysis to identify or understand the scope and content of, third party patents, copyrights, trade secrets, or other rights.
This document may include technical inaccuracies or typographical errors.
This document consists solely of commercial items. You shall be responsible for ensuring that any use, duplication or disclosure of this document complies fully with any relevant export laws and regulations to assure that this document or any portion thereof is not exported, directly or indirectly, in violation of such export laws. Use of the word “partner” in reference to ARM’s customers is not intended to create or refer to any partnership relationship with any other company. ARM may make changes to this document at any time and without notice.
If any of the provisions contained in these terms conflict with any of the provisions of any signed written agreement covering this document with ARM, then the signed written agreement prevails over and supersedes the conflicting provisions of these terms. This document may be translated into other languages for convenience, and you agree that if there is any conflict between the English version of this document and any translation, the terms of the English version of the Agreement shall prevail.
Copyright © [2010-2012, 2015], ARM Limited or its affiliates. All rights reserved.
ARM Limited. Company 02557590 registered in England.
110 Fulbourn Road, Cambridge, England CB1 9NJ.

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.
Unrestricted Access is an ARM internal classification.

Product Status

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

Web Address

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.
Non-ConfidentialPDF file icon PDF versionARM DUI0498J
Copyright © 2010-2012, 2015 ARM. All rights reserved.