ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Debugging with your debug hardware unit8.1 Post-mortem debuggingPost-mortem debugging enables you to examine the state of a system that has previously beenrunning but is currently not connected to debug hardware.8.1.1 PrerequisitesBefore you can examine a running target with debug hardware, you must configure the debughardware unit for that target. If you have a target that is operating without a debug hardware unitconnected, and you want to examine it to find out why it is behaving in a particular way, youmust power-up the debug hardware unit and configure the connection without disturbing thestate of the target. This requires that the debug hardware unit is powered before it is connectedto the target.The debug hardware unit includes power conditioning and switching circuitry that enables youto plug and unplug the JTAG cable without affecting the target.NoteThe voltage reference used by the debug hardware unit JTAG circuit is generated from theVTref signal present on the JTAG connector. If this signal is not connected at the target, youmust modify the target or the JTAG cable to supply a suitable reference. Connecting VTref toVsupply is usually sufficient.8.1.2 ProcedureTo connect to a running target:1. Ensure that the JTAG input lines TDI, TMS, nSRST, and nTRST have pull-up resistors(normal practice), and TCK has a pull-down resistor, so that when the adaptor isdisconnected from the target these lines are in their quiescent state.2. Plug the power jack into the debug hardware unit and wait for it to boot.3. Configure the debug hardware connection. You must do one of the following:• load a configuration that you have previously saved• manually configure the connection• autoconfigure using a separate test system.NoteDo not use autoconfigure on the target to be debugged, because doing so might reset theprocessor.4. If the target processor, such as an ARM7TDMI, does not have any system registers, youmust explicitly configure the endianness.NoteDo not automatically detect the endianness of target processors that do not have a systemregister. Doing so might disturb the state of the processor.5. Plug the JTAG cable into the target.CautionTo prevent unwanted resets during connection of the debug hardware, it is essential thateither:• the target and debug hardware are properly earthedARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 8-2ID021112Non-Confidential
Debugging with your debug hardware unit• the ground pins of the debug connector make contact before the signal pins.6. Start the debugger, and connect to the running target.In your debug hardware configuration, set the Post Reset State to Running.In your debugger, connect using the Connect (Connection Modes) of No Reset / NoStop.7. To get a high-level (source code) view of the problem, load the symbol table for yourtarget program into the debugger.8. If the processor stopped during debugging, then in your debugger:a. Clear any breakpoints that you have set.b. Start the processor runningc. Disconnect from all targets to which the debugger is connected on yourdevelopment platform.If the processor is still running, then in your debugger disconnect from all targets to whichthe debugger is connected on your development platform.9. Unplug the JTAG connector from the development platform.8.1.3 See alsoTasks• Configuring the debug hardware Advanced settings on page 5-47.Concepts• Semihosting on page 8-4• Strategies used by debug hardware to debug cached processors on page 8-15• Debugging applications in ROM on page 8-17.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 8-3ID021112Non-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: Creating debug hardware target conf
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 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: Chapter 8Debugging with your debug
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 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

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

Delete template?

Save as template?