ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Configuring debug hardware for GDBThe TCP/IP port number you specify here is the port number you must use with the GDBtarget remote command from subsequent GDB sessions. Also, make sure the port numberis not in use by another service.9.12.4 See alsoTasks• 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 NFS (GDB-NFS) on page 9-19.Concepts• Connection methods for each debugging mode on page 9-10• Setting DCC parameters on page 9-23• Loading and booting a complete system on page 9-26.Other information• ARM downloads, http://www.arm.com/productsARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 9-18ID021112Non-Confidential
Configuring debug hardware for GDB9.13 Connections to a target OS using NFS (GDB-NFS)This is useful for developing software on deeply embedded systems, and also for debuggingbrand new targets where only the CPU and RAM are initially known to work. Connections ofthis type are referred to as GDB-NFS connections. The following figure shows the GDB-NFSconnection method:Debug hosttelnetrviloadDebug unitConfigurationMechanismTargetOSfilesystemtelnetGDB5000, 5001,...Bridged EthernetVirtualEthernetDCC(IP over DCC)ApplicationFigure 9-5 GDB-NFS connectionsFor example, the minimum I/O support that Linux requires is a system console and a root filesystem. You can connect the console to a GDB command-line console and, with the appropriatedriver, you can mount the root file system over NFS with debug hardware acting as a bridge.Alternatively, you might have a file system and kernel loaded into memory and booted, and anNFS file system mounted to be shared later.NoteThis network connection is not as fast as an office LAN, because of the limited bandwidth ofDCC.9.13.1 ProcedureIf your target has a complete operating system, you can mount a file system over NFS. In thiscase, debug hardware acts as a bridge.To debug a target using a GDB-NFS connection:1. Power-up your target hardware and debug hardware unit.2. Load the Linux kernel and uBoot image using rviload. For example:./rviload --host=rvi5 -j1000000 -mVEC -a0 7fc0:uImage 1000000:u-boot.binPress Return. Messages appear showing u-boot loading and running the Linux kernel.NoteThis is similar for rviload.exe for MSDOS users.3. Mount the directory exported by NFS using the following command:~ # mount -t nfs -n client_IP_address:/exported_directory /mnt9.13.2 See alsoTasks• 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-13ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 9-19ID021112Non-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 167: 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

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

Delete template?

Save as template?