ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Debugging with your debug hardware unit8.12 Considerations when debugging processors with caches enabledWhen debugging a processor with caches enabled, you might have to provide the address of anarea of memory on the target that can be used exclusively by debug hardware. On some targets,the debug software downloads code sequences to this area to perform various tasks, such ascleaning the cache, and accessing the system registers. Debug hardware does not preserve thecontents of this area.A code sequence area is only required for certain processors where the required operationscannot be performed directly over JTAG. If debug hardware requires a code sequence area, andone has not been enabled, errors are displayed within the debugger. For example:• Error V28305 (Vehicle): Memory operation failed• Warning: Code sequence memory area size error• Unable to load code sequence into defined memory area.NoteThe code sequence area must be 128 bytes long and in a non-cacheable, readable and writeablearea.To set up a code sequence area, use the options for each specific processor in the DebugHardware Config utility. This provides access to configuration items for each processor for:• enabling code sequences• setting the address and size of the code sequence areas.NoteThese settings might also be available in your debugger Registers view. Any settings modifiedusing the Registers view in your debugger are only modified for the duration of the debugsession. Any settings modified using the Debug Hardware Config utility are persistent untilmodified again.8.12.1 See alsoTasks• Post-mortem debugging on page 8-2.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-16ID021112Non-Confidential
Debugging with your debug hardware unit8.13 Debugging applications in ROMSome of the issues involved with debugging applications in ROM using debug hardware aredescribed in the following:• Debugging from reset on page 8-18• Debugging systems with ROM at the exception vector on page 8-22.8.13.1 See alsoTasks• Post-mortem debugging on page 8-2.Concepts• Semihosting on page 8-4• Strategies used by debug hardware to debug cached processors on page 8-15.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 8-17ID021112Non-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: Creating debug hardware target conf
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 143: 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 195 and 196:
Troubleshooting your debug hardware
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?