ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Troubleshooting your debug hardware unit• If some data has already been written to the compact flash when the error occurs, thedebug hardware unit must reboot to clean up the failed installation and revert to thebacked up state. The dialog box shown in the following figure appears:Figure 10-7 Error during writing to compact flashClick OK. The debug hardware unit reboots. You can then begin the installation again.10.8.3 See alsoTasks• Viewing software version numbers on page 4-4.Concepts• About templates and firmware files on page 4-2.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 10-10ID021112Non-Confidential
Troubleshooting your debug hardware unit10.9 Troubleshooting autoconfigation of a scan chainWhen autoconfiguring a scan chain, you might see one of the following errors:• If debug hardware detects any unpowered devices, it displays the error shown in thefollowing figure:Figure 10-8 Error shown when unpowered devices are detectedThis error message can also display if the target is connected by the JTAG ribbon cable ifdebug hardware is started when the Low Voltage Differential Signaling (LVDS) probe isconnected, or if the probe is connected and used after you started debug hardware.If you see this error:— Check the JTAG connection between the debug hardware unit and the targethardware.— Ensure that power is supplied to all your devices.• If debug hardware cannot identify any devices, it displays the error shown in the followingfigure:Figure 10-9 Error shown when no devices are detectedIf you see this error:— manually configure the scan chain if your target has unsupported devices— try auto-configuring again with a lower clock speed.NoteYou might have to power-cycle your target hardware when changing the clockspeed.• The Read ROM Table phase for a CoreSight system fails to find any devices. This mightbe because the ROM table is corrupt. Manually configure the scan chain.• If communication cannot be made with the debug hardware unit in your currentconfiguration, it displays the error shown in the following figure.Figure 10-10 Error shown when there is no communication with debug hardwareIf you see this error, it might mean that the debug hardware unit in your configuration fileno longer exists, or has been configured with different network settings.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 10-11ID021112Non-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:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144: 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 and 184: Configuring debug hardware for GDB
Page 185 and 186: Chapter 10Troubleshooting your debu
Page 187 and 188: Troubleshooting your debug hardware
Page 193: 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?