ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Configuring debug hardware for GDB9.23 Multiprocessor debugging with GDB and debug hardwareDebug hardware is capable of simultaneously and synchronously debugging multiple targets.However, GDB does not support multiprocessor debugging directly.NoteAlthough multiprocessor debugging is possible using GDB, it is recommended that you debugmultiple processors using higher level tools.9.23.1 How connections to multiple processors are allocatedWhen you make connections to multiple target processors, the connections on ports 5000,5001,... are allocated by debug hardware, that is, redirected virtual DCC is allocated a port foreach device in a similar way to GDB halt-mode debugging. The port range starts from port 5000,so virtual Ethernet or raw redirected DCC for the first device appears on port 5000, the seconddevice on port 5001, and this continues in the same way.9.23.2 Considerations when debugging multiple targets with GDBBe aware of the following if you are debugging multiple targets with GDB:• Multiprocessor debugging with GDB requires that you open multiple command windows(such as Xterms). You must have one GDB session for each target processor to which youwant to connect.• If you have multiple targets on the debug hardware scan chain, then:— the target processors are numbered consecutively, starting at one— the available bandwidth over DCC is shared between all target processors— communications to all target processors are through a single JTAG chain.9.23.3 See alsoTasks• Preparing your debug hardware for remote GDB connections on page 9-21• Loading and booting a complete system on page 9-26.Concepts• About configuring debug hardware for debugging with GDB on page 9-3• Methods of connecting from remote GDB sessions on page 9-9.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 9-34ID021112Non-Confidential
Chapter 10Troubleshooting your debug hardware unitIf you encounter problems when attempting to connect to a debug hardware unit or upgrade thefirmware, see the following topics:• Multiple programs attempting to scan on page 10-2• USB server not accessible on page 10-3• Connection times out on page 10-4• Other active connections on page 10-5• A debug hardware unit is not listed on page 10-6• Auto Configure button is disabled in the Debug Hardware Config utility on page 10-7• Remove button is disabled in the Debug Hardware Config utility on page 10-8• Troubleshooting firmware upgrade installations on page 10-9• Troubleshooting autoconfigation of a scan chain on page 10-11• Log Client Utility on page 10-13.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 10-1ID021112Non-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:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Configuring CoreSight systems6.1 Ab
Page 99 and 100:
Configuring CoreSight systems6.3 Co
Page 101 and 102:
Configuring CoreSight systems6.5 Ab
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 119 and 120:
Page 121 and 122:
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 133 and 134: Debugging with your debug hardware
Page 151 and 152: Chapter 9Configuring debug hardware
Page 153 and 154: Configuring debug hardware for GDB9
Page 179 and 180: Configuring debug hardware for GDBO
Page 181 and 182: Configuring debug hardware for GDBR
Page 183: Configuring debug hardware for GDB
Page 187 and 188: Troubleshooting your debug hardware
Page 199: Troubleshooting your debug hardware
show all

ARM DS-5 Using the Debug Hardware Configuration Utilities

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?