ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Debugging with your debug hardware unit8.14 Debugging from resetYou can debug systems running in ROM. A typical embedded system has the applicationprogrammed in non-volatile memory, such as ROM or Flash. When target hardware is poweredup, the application starts running. When connecting the debugger to a target already running theapplication, the application stops at an arbitrary point in the code. The default behavior of thedebugger is to stop the target on connection. Loading the image symbols gives you source codeview of the current location.This means that you can examine the state of the system and restart execution from the currentplace. In some cases, this is sufficient. However, in many cases it is preferable to restartexecution of the application as if from power-on. There are three ways to do this:• debugging with a simulated a reset• debugging with a reset register• debugging with a target reset.When you debug code that is running from ROM, you must ensure that at least one breakpointunit remains available so that you can set breakpoints on code in ROM, because you cannot usesoftware breakpoints for this purpose. On a processor without vector catch hardware, you mustdisable semihosting and vector catching as soon as possible after starting up the debugger. Thiscan reduce the chances of the debugger taking these units for its own use.On ARM processors that use a breakpoint resource to implement software breakpoints, such asthe ARM7TDMI, you must remove all software breakpoints if you are out of breakpointresources. This enables you to place a single hardware breakpoint in ROM.Another factor in debugging a system in ROM is that the ROM image does not contain anydebug information. When debugging, symbol or source code information is available by loadingthe relevant information into the debugger from the ELF image on the host.8.14.1 See alsoTasks• Post-mortem debugging on page 8-2.Concepts• Debugging with a simulated reset on page 8-19• Debugging with a reset register on page 8-20• Debugging with a target reset on page 8-21• Debugging systems with ROM at the exception vector on page 8-22.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 8-18ID021112Non-Confidential
Debugging with your debug hardware unit8.15 Debugging with a simulated resetYou can, where supported, simulate a reset from within the debugger by setting:• the pc to the address of the reset vector• the CPSR to change into Supervisor mode with interrupts disabled.This simulates the state of the ARM processor at power-on or reset, but it does not performpost-reset tasks such as resetting the memory map, or initializing any target-specific featuressuch as peripheral registers. It is recommended that you modify these target-specific features toresemble their startup state before executing the application again, if possible. You can automatethis procedure using the scripting facilities of your debugger.8.15.1 See alsoTasks• Post-mortem debugging on page 8-2.Concepts• Debugging from reset on page 8-18• Debugging with a reset register on page 8-20• Debugging with a target reset on page 8-21• Debugging systems with ROM at the exception vector on page 8-22.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 8-19ID021112Non-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: 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 and 130: Chapter 8Debugging with your debug
Page 131 and 132: Debugging with your debug hardware
Page 145: 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 197 and 198:
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?