ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Configuring debug hardware for GDB9.8 Connection methods for each debugging modeHow you connect to a target determines the debugging mode. The following connectionmethods are available for each debugging mode:9.8.1 Halt-mode debuggingHalt-mode debugging is the simplest method of debugging a target with GDB. You directlyconnect to debug hardware, that then controls the starting and stopping of the processor. Thismethod of connecting is subsequently referred to as an RVI-GDB connection.9.8.2 Monitor-mode debugging9.8.3 See alsoMonitor-mode debugging requires that your target application communicate with GDB usingthe Debug Communications Channel (DCC) of an ARM architecture-based processor.However, if your target application includes an Ethernet feature, you do not have to use DCC.Different DCC modes are available depending on the requirements of your target.The connection methods for Monitor-mode debugging are:Target-GDB connectionsSemi-transparent connections to GDB stubs. The GDB stub communicates withthe GDB client using the DCC channel as a serial port. The debug hardware unitmakes this connection available on a TCP/IP port to which the GDB clinetconnects. The GDB stub must be compiled into the target application.Target-GDB-Virtual Ethernet connectionsAn extension to Target-GDB connections for standalone applications running anIP stack. The GDB stub communicates with the GDB client using the DCCchannel as an Ethernet channel. The debug hardware unit makes this connectionavailable on a TCP/IP port to which the GDB client connects.GDBserver connectionsAn alternative to Target-GDB-Virtual Ethernet connections where the target isrunning gdbserver running under an operating system (OS).GDB-NFS connectionsConnections to the root filesystem on the target OS that is mounted over NFS. Thedebug hardware unit acts as a bridge between the debug host and the target OS.Tasks• Connections to a target without built-in GDB support (RVI-GDB) on page 9-11• Connections to a target with a GDB stub (Target-GDB) on page 9-13• Connections to a target GDB stub using Virtual Ethernet/TTY mode (Target-GDB-VirtualEthernet) on page 9-15• Connections to a target OS using gdbserver (GDBserver) on page 9-17• Connections to a target OS using NFS (GDB-NFS) on page 9-19.Concepts• DCC modes on page 9-7.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 9-10ID021112Non-Confidential
Configuring debug hardware for GDB9.9 Connections to a target without built-in GDB support (RVI-GDB)These are connections to targets where no GDB stub has been built into the target application,or when you want to perform halt-mode debugging. Connections of this type use the built-inGDB protocol interpreter of debug hardware to control the CPU directly, and are referred to asRVI-GDB connections. When you want to examine the internal state of the CPU (such asregisters, memory, and variables), the image on the target stops executing. After examining therequired state, you must start the image again. The following figure shows the configuration:Debug hosttelnetDebug unitConfigurationMechanismSet up JTAGscan chainTargetGDB4000, 4001,...GDB protocolGDB protocolinterpreterJTAGrun controlApplicationFigure 9-1 RVI-GDB connectionsNoteGDB does not support Semihosting over JTAG. Therefore, any prompts and messages that areoutput by the application cannot be displayed in your debugger.9.9.1 RVI-GDB ScenariosUse the RVI-GDB connection method to:• perform run and stop debugging of a single ARM processor• perform run and stop debugging with GDB at the same time as debugging the application.That is, for example, if connecting to a target with a GDB stub (Target-GDB connections),or if your target application requires TCP/IP communication with the debug host(Target-GDB-Virtual Ethernet connections).NoteWhen the image stops, so does the handling of interrupt routines. This might not always bedesirable when debugging a real-time system.9.9.2 PrerequisitesTo use the RVI-GDB connection method, it is recommended that you compile your targetapplication using a GNU toolchain for ARM architectures.9.9.3 ProcedureIf your application does not have GDB support linked-in, you can use the GDB protocol builtinto the debug hardware unit to debug your application. However, this controls the CPU directly,and the CPU stops whenever you want to examine its internal state.To debug an application through a RVI-GDB connection:1. Power-up your target hardware and debug hardware unit.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 9-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:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
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 151 and 152: Chapter 9Configuring debug hardware
Page 153 and 154: Configuring debug hardware for GDB9
Page 159: 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 199: Troubleshooting your debug hardware
show all

ARM DS-5 Using the Debug Hardware Configuration Utilities

Create successful ePaper yourself

Delete template?

Save as template?