ARM DS-5 Using the Debug Hardware Configuration Utilities

Configuring debug hardware for GDB9.10 Connections to a target with a GDB stub (Target-GDB)These are connections to a target that is running an application with a GDB stub, and are referredto as Target-GDB connections. The GDB stub enables the target application to communicatewith a host application through debug hardware, using the DCC of an ARM architecture-basedprocessor. The DCC carries the GDB protocol packets between the target and the remote GDBsession over the TCP/IP ports 5000, 5001,... as shown in the following figure:Debug hostDebug unitConfigurationMechanismSet up JTAGscan chainTargetGDB5000, 5001,...Telnet(Serial over IP)Virtual TTYDCCApplicationGDB stubFigure 9-2 Target-GDB connections9.10.1 Target-GDB ScenariosUse the Target-GDB connection method to:• debug a target system that does not have an OS• debug a target system with an OS that supports GDB.9.10.2 PrerequisitesTo use the Target-GDB connection method, it is recommended that you compile the DCC driverand GDB stub into your target application using a GNU toolchain for ARM architectures. Youcan either:• link the example GDB stub into your target application or operating system• port your existing serial GDB stub to use the DCC driver.NoteOn the GDB connection to the target, it is recommended that you enable DCC and VirtualEthernet/TTY mode before starting the processor.9.10.3 ProcedureIf your application includes a target-resident GDB stub, it can communicate over DCC.To debug an application using a Target-GDB connection:1. Power-up your target hardware and debug hardware unit.2. Configure the processor using rvconfig, using either automatic or manual configuration.Save the rvc file in a convenient location.3. Run rvigdbconfig, specifying the rvc file that was created in step 2, and the appropriateDCC mode, for example mode 2: rvigdbconfig –f rvi.rvc -d 2:24. Start GDB, load the symbols if required, and connect to the second processor (forexample) to load and run your application in the usual way. This example uses port 4001of debug hardware:ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 9-13ID021112Non-Confidential