ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Configuring CoreSight systems6.4 How the debug hardware unit autodetects Serial Wire DebugSerial Wire Debug (SWD) does not support a scan chain in the same way that JTAG does. Whenautoconfiguring in SWD mode, the debug hardware unit:1. Adds the ARMCS-DP device to the scan chain configuration.2. Optionally reads the CoreSight ROM Table to add the remaining devices. This is done bydefault, but you can override this.NoteBe aware that if your target supports both JTAG and SWD, then you must enable Use SWJSwitching in the Advanced configuration settings before autoconiguring the scan chain.6.4.1 See alsoTasks• Setting up a CoreSight trace association file on page 6-11• Reading the CoreSight ROM table on page 6-3.Concepts• About CoreSight system configuration on page 6-2• CoreSight autodetection on page 6-4.Reference• Debug hardware Advanced configuration settings on page 5-33.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 6-5ID021112Non-Confidential
Configuring CoreSight systems6.5 About trace associationsTrace associations are stored in the debug hardware configuration file (.rvc). However, you cansave the associations in a separate file, if you want to provide the associations to other usersusing a similar development platform.Trace associations are required to describe the associations between the processors and thetrace-related devices in complex CoreSight systems. Examples of such associations are:• processor outputs into an ETM• ETM outputs into an ETB• ETM input from a particular processor• CoreSight ETM outputs into a Trace Port Interface Unit (TPIU)• TPIU input from a particular trace source• ETB input from a particular trace source.Your debug tools use the associations in the debug hardware configuration file to determine thecomponents that must be programmed for tracing a specific source in the systemAssociations have direction, and some are bi-directional. You must configure associationscorrectly to enable your debugger to associate trace output with the source of generated trace.NoteAlthough a trace association might be created for a non-CoreSight system, do not modify it.6.5.1 See alsoConcepts• Defining CoreSight trace associations on page 6-7• CoreSight topology and associations for the CoreSight DK11 on page 6-15• CoreSight topology and associations for the Cortex-R4 FPGA on page 6-17• CoreSight topology and associations for the Cortex-M3 FPGA on page 6-19• CoreSight topology and associations for multiple trace sources on page 6-21.Reference• CoreSight device names and classes on page 5-52• Trace Association Editor dialog box on page 6-9• Format of trace associations on page 6-8.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 6-6ID021112Non-Confidential
Page 1 and 2:
®ARMDS-5Version 5.9Using the Debug
Page 3 and 4:
Conformance NoticesThis section con
Page 5 and 6:
Contents4.6 Restarting the debug ha
Page 7 and 8:
Contents10.6 Auto Configure button
Page 9 and 10:
Conventions and feedback• the ser
Page 11 and 12:
Getting started with the debug hard
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Chapter 3Configuring network settin
Page 21 and 22:
Configuring network settings for yo
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Managing the firmware on your debug
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Chapter 5Creating debug hardware ta
Page 45 and 46:
Creating debug hardware target conf
Page 47 and 48:
Creating debug hardware target conf
Page 49 and 50: Creating debug hardware target conf
Page 97 and 98: Configuring CoreSight systems6.1 Ab
Page 99: Configuring CoreSight systems6.3 Co
Page 103 and 104: Configuring CoreSight systems6.7 Fo
Page 105 and 106: Configuring CoreSight systems2. Loc
Page 107 and 108: Configuring CoreSight systems• To
Page 109 and 110: Configuring CoreSight systems6.10.1
Page 111 and 112: Configuring CoreSight systemsName=T
Page 113 and 114: Configuring CoreSight systemsName=T
Page 115 and 116: Configuring CoreSight systems6.13.1
Page 117 and 118: Configuring CoreSight systems6.15 C
Page 123 and 124: Chapter 7Using TraceThe following t
Page 125 and 126: Using Trace7.2 Trace hardware captu
Page 127 and 128: Using TraceConcepts• About using
Page 129 and 130: Chapter 8Debugging with your debug
Page 131 and 132: Debugging with your debug hardware
Page 151 and 152:
Chapter 9Configuring debug hardware
Page 153 and 154:
Configuring debug hardware for GDB9
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Configuring debug hardware for GDBO
Page 181 and 182:
Configuring debug hardware for GDBR
Page 183 and 184:
Configuring debug hardware for GDB
Page 185 and 186:
Chapter 10Troubleshooting your debu
Page 187 and 188:
Troubleshooting your debug hardware
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199:
show all

ARM DS-5 Using the Debug Hardware Configuration Utilities

Create successful ePaper yourself

Delete template?

Save as template?