ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Debugging with your debug hardware unit8.5 Hardware breakpointsDepending on implementation options, most ARM processors contain dedicated hardwareresources, such as ARM EmbeddedICE ® logic, for matching against specific hardware events.Your debugger enables you to configure these resources to implement instruction and databreakpoints.NoteData breakpoints are also sometimes referred to as watchpoints.The resources available depend on the processor you are using. See the data sheet for yourprocessor for information.Hardware breakpoints might also provide additional matching capabilities. Examples of thisinclude matching on an external signal, and distinguishing between privileged andnon-privileged accesses. The Set Address/Data Breakpoint dialog box displays the capabilitiesof your hardware.Hardware instruction breakpoints do not require the instruction in memory to be changed. Thismeans that they can be used to debug code in Flash and ROM, and can be used withself-modifying code.8.5.1 See alsoConcepts• Software instruction breakpoints on page 8-9• Processor exceptions on page 8-10• 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-8ID021112Non-Confidential
Debugging with your debug hardware unit8.6 Software instruction breakpointsFor processors that do not support hardware instruction breakpoints, or in cases where you haveused up all the available hardware breakpoint resources, you can use software instructionbreakpoints. Software breakpoints modify the instruction in memory to create a special valuethat causes the processor to enter debug state when executed. The value written to memorydepends on the processor you are using. For ARM processors, one of the following schemes isused, depending on the architecture and processor revision:• An undefined instruction is written to memory, and a hardware breakpoint resource isused to spot this instruction being executed. The processor enters debug state when thehardware breakpoint unit spots the undefined instruction entering the execute pipelinestage.• An ARMv5 BKPT instruction is written to memory, and a hardware breakpoint resource isused to spot the instruction being executed. The processor enters debug state when thehardware breakpoint unit spots the BKPT instruction entering the execute pipeline stage.• An ARMv5 BKPT instruction is written to memory. When this instruction is executed, theprocessor automatically enters debug state.Where a hardware breakpoint unit is used to spot software instruction breakpoints, only a singlehardware resource is used, no matter how many software instruction breakpoints are set. If youhave difficulty setting software instruction breakpoints, you might have to free up a hardwarebreakpoint resource first.Software breakpoints cannot be used to debug code in Flash or ROM, and can be unreliable inself-modifying code.NoteWhen viewing memory or disassembly, debug hardware reports the actual contents of memory.Prior to running, any software breakpoints are written to memory. When the processor halts, thesoftware breakpoints are removed from memory. On a number of processors, it is not possibleto access memory while running. This means that if you disconnect debug hardware from theprocessor while the target is running, the breakpoints are left in memory. If the processorsubsequently executes one of the instructions, then (depending on the processor architecture)the processor either stops at the software breakpoint or causes the processor to take an undefinedexception.8.6.1 See alsoConcepts• Hardware breakpoints on page 8-8• Processor exceptions on page 8-10• 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-9ID021112Non-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: 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 135: 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

Create successful ePaper yourself

Delete template?

Save as template?