ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Debugging with your debug hardware unit8.2 SemihostingSemihosting enables the ARM processor target to make I/O requests to the computer runningthe debugger. This means the target does not require a screen, keyboard, or disk during thedevelopment period. These requests are made as a result of calls to C library functions, forexample, printf() and getenv().8.2.1 See alsoTasks• Post-mortem debugging on page 8-2• Adding an application SVC handler when using debug hardware on page 8-5.Concepts• Cortex-M3 semihosting on page 8-7• 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-4ID021112Non-Confidential
Debugging with your debug hardware unit8.3 Adding an application SVC handler when using debug hardwareMany applications require their own SVC handlers in addition to semihosting SVCs. To ensurethat the application SVC handler cooperates with the debug hardware semihosting mechanism,use your debugger to:1. Install the application SVC handler into the vector table.2. Modify the value of SEMIHOST_VECTOR to point to a location that is only reached if yourhandler does not recognize the SVC, or recognizes it as a semihosting SVC.For example, a particular SVC handler might detect if it has failed to handle a SVC and branchto an error handler. An example of a basic exception handler is shown in the following example.Example 8-1 Basic SVC handler; r0 = 1 if SVC handledCMP r0, #1; Test if SVC has been handled.BNE NoSuchSVC; Call unknown SVC handler.LDMFD sp!, {r0}; Unstack SPSR...MSR spsr_cf, r0; ...and restore it.LDMFD sp!, {r0-r12, pc}^ ; Restore registers and return.You can modify this code for use in conjunction with debug hardware semihosting as shown inthe following example.Example 8-2 SVC handler with debug hardware link; r0 = 1 if SVC handledCMP r0, #1; Test if SVC has been handled.LDMFD sp!, {r0}; Unstack SPSR...MSR spsr_cf, r0; ...and restore it.LDMFD sp!, {r0-r12, lr} ; Restore registers.MOVEQS pc, lr; Return if SVC handled.Semi_SVCMOVS pc, lrYou must then set up the SEMIHOST_VECTOR with the address of Semi_SVC. The instruction at thisaddress is never actually executed because the debug software returns directly to the applicationafter processing the semihosted SVC. Using a normal SVC return instruction ensures that theapplication does not crash if the semihosting breakpoint is not set up.If the application is linked with the semihosted ARM C library, and therefore uses the C librarystartup code, you must change the contents of SEMIHOST_VECTOR before the application installs itsown handler, typically by setting a breakpoint in the main code. This is because, ifSEMIHOST_VECTOR is set to the fall-through part of the application SVC handler before theapplication starts execution, the semihosted SVCs that are called by the library initialization cantrigger an unknown breakpoint error. At this point, the SVC vector has not yet had theapplication handler written to it, and might still contain the software breakpoint bit pattern. Thistriggers a breakpoint that the debug software does not know about, because the SEMIHOST_VECTORaddress has moved to a place that cannot currently be reached.NoteIf semihosting is not used by your application, including the startup code, you can simplify thisprocess by setting SEMIHOST_ENABLED to zero.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 8-5ID021112Non-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: 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: Debugging with your debug hardware
Page 135 and 136: 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?