ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Debugging with your debug hardware unit8.9 Interaction between breakpoint handling in the debug hardware and yourdebuggerThe following describe the interaction between breakpoint handling in the debug hardware andbreakpoint handling in your debugger:Break details or break capabilitiesYou can find out what hardware breakpoint resources are available by viewing thebreak details or break capabilities in your debugger.Memory mapsYour debugger enables you to define a memory map to describe the layout andtype of memory in your system. When you set a breakpoint, areas of memory thatare marked as read-only, such as Flash and ROM, automatically use hardwareinstruction breakpoints. All other types of memory use software instructionbreakpoints by default.SteppingWhen you step through code, the debugger usually sets a temporary breakpointon the destination address. If the code is in read-only memory, or if the softwarebreakpoint implementation requires hardware assistance, a hardware breakpointis used for this. If you are unable to step, you might have to free up a hardwarebreakpoint resource.Some processors, such as ARM9, provide dedicated single-step hardware. debughardware uses this hardware if it is available, but steps larger than a singleinstruction might revert back to using breakpoints, to improve efficiency.NoteFor ARM7, ARM9, ARM11 or Cortex-A8 processors, interrupts are disabledwhen single-stepping with debug hardware. For the Cortex-M3 processor,interrupts are enabled when single-stepping with debug hardware.Interrupt behavior applies only to debug hardware single-instruction stepping.Higher-level stepping depends on the strategy in your debugger, that is, whetheryou have used the place Breakpoint and run method, or the multiplesingle-instruction steps method.NoteWhen hardware single-step is used, debug hardware prevents the processor fromprocessing any pending interrupts.Resource allocationDebug hardware allocates hardware breakpoint resources as they are received,rather than allocating all the resources at the same time when the debuggingsession begins. Therefore, if you attempt to set a breakpoint when there areinsufficient resources available, debug hardware displays an error message assoon as you try to set the breakpoint, rather than waiting until debugging begins.8.9.1 See alsoConcepts• Semihosting on page 8-4• Hardware breakpoints on page 8-8• Software instruction breakpoints on page 8-9• Processor exceptions on page 8-10ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 8-12ID021112Non-Confidential
Debugging with your debug hardware unit• Breakpoints and the program counter on page 8-11• Problems setting breakpoints on page 8-14.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 8-13ID021112Non-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: 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 139: 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: Troubleshooting your debug hardware
Page 191 and 192:
Troubleshooting your debug hardware
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?