ARM DS-5 Using the Debug Hardware Configuration Utilities

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