ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Debugging with your debug hardware unit8.7 Processor exceptionsDepending on implementation options, most ARM processors provide dedicated hardware toenter debug state when a predetermined event occurs.Most recent ARM processors provide hardware for trapping exceptions. When enabled, theeffect is similar to placing a breakpoint on the selected vector table entry. This is called vectorcatch. However:• Some ARM processors, such as ARM7, do not provide vector catch hardware. For theseprocessors, debug hardware simulates vector catch using instruction breakpoints.• For Cortex-M3, this is equivalent to putting a breakpoint at the target of the vector.Cortex-M3 has a restricted set of vector catches available.• If the exception vectors are in ROM, debug hardware must use hardware breakpoints tosimulate vector catch. This reduces the number of resources available for other purposes,if the processor does not have vector catch support.When the debug hardware simulates vector catch on earlier ARM processors that do not havevector catch support, it uses a software breakpoint when the vector table is located in RAM.You must take care when debugging through a system reset. Some hardware targets alter thememory map after reset, so the location of in physical memory containing software breakpointmight not be in the correct reset position. The following warning is output to the your debuggerconsole if debug hardware simulates reset vector catch using an instruction breakpoint:Warning: A software breakpoint is being used to simulate reset vector catch.This may fail to be hit if the memory is remapped when a reset occurs.The exact behavior of the ARM vector catch hardware depends on the processor. ARM9processors enter debug state only when the specified exception occurs. Other processors, suchas ARM11 or older processors that use a breakpoint, enter debug state whenever the instructionat the exception vector is executed, regardless of whether the exception occurs or not.8.7.1 See alsoConcepts• Hardware breakpoints on page 8-8• Software instruction breakpoints on page 8-9• Breakpoints and the program counter on page 8-11• Interaction between breakpoint handling in the debug hardware and your debugger onpage 8-12• Problems setting breakpoints on page 8-14.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 8-10ID021112Non-Confidential
Debugging with your debug hardware unit8.8 Breakpoints and the program counter8.8.1 See alsoThe following events describe the value of the program counter when a breakpoint is taken:Hardware data breakpointsThe address of the program counter after hitting a hardware data breakpointdepends on the processor being used.For ARM processors, a skid of either one or two instructions occurs after a databreakpoint is hit. This means that the instruction that generated the breakpoint,and possibly the one after that, are both executed. The program counter shown inyour debugger might not be the address of the instruction that generated thebreakpoint.Hardware instruction breakpointsThe address of the program counter after hitting a hardware instructionbreakpoint depends on the processor being used.For ARM processors, no skid occurs after hitting a hardware breakpoint. Thismeans that the instruction that generated the breakpoint has not been executed,and the program counter is set to this address.Software instruction breakpointsThe address of the program counter after hitting a software breakpoint is alwaysthe address of the breakpoint. Unless the instruction is a BKPT instruction, theinstruction that generated the breakpoint is not yet executed.Processor eventsThe address of the program counter after a processor event is hit depends on theprocessor being used. For ARM processors, vector catch hardware stops with theprogram counter on exception vector, before the instruction at that address isexecuted.Concepts• Hardware breakpoints on page 8-8• Software instruction breakpoints on page 8-9• Processor exceptions on page 8-10• Interaction between breakpoint handling in the debug hardware and your debugger onpage 8-12• Problems setting breakpoints on page 8-14.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 8-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: 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 137: 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:
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?