ARM DS-5 Using the Debug Hardware Configuration Utilities

Configuring debug hardware for GDB9.16 Setting DCC parametersEthernet bridging works by examining incoming packets at debug hardware, then decidingwhich are destined for debug hardware itself and which are destined for the target. To do this,debug hardware must know the IP address, subnet mask and default gateway parameters for thetarget. These parameters are normally determined through DHCP, where the target asks for aconfiguration, and one is supplied by a server over the network. In this case, debug hardware isable to intercept the incoming DHCP packet containing the parameters and configure itselfappropriately. It is, however, possible to configure a target with a static IP address. In this casethere is no DHCP transaction to intercept, and debug hardware has no way of determining thetarget configuration. You must set these parameters in debug hardware for correct operation.You can configure DCC Ethernet bridging with the rvigdbconfig command, and you must setthe appropriate parameter when using DCC mode.If you use rviload, you must set the DCC mode to either VEC or VEP.NoteWhen Ethernet bridging is running, normal LAN services are accessible (including DHCP andNFS).9.16.1 Examples of setting DCC parametersrvigdbconfig –f rvi.rvc -d 1:2sets device 1 (the first device on the scan chain) to DCC mode 2.Additional devices are configured in a similar way. For example:rvigdbconfig –f rvi.rvc -d 1:2 -d 2:2configures devices 1 and 2 to mode 2.The IP parameters for static IP configurations are set up in the following way:rvigdbconfig –f rvi.rvc –d 1:2 –s 1:10.0.0.10:255.255.255.0:10.0.0.1This configures device 1 to use DCC mode 2 with IP address 10.0.0.10, subnet mask255.255.255.0, and default gateway 10.0.0.1. This format can be used to configure multipleprocessors if required. For example:rvigdbconfig –f rvi.rvc –d 1:2 –d 2:2 –s 1:10.0.0.10:255.255.255.0:10.0.0.1 –s2:10.0.0.11:255.255.255.0:10.0.0.19.16.2 See alsoTasks• Configuring a target processor for virtual Ethernet on page 5-51• Connections to a target with a GDB stub (Target-GDB) on page 9-13• Connecting to targets from GDB through debug hardware on page 9-22.Concepts• DCC and interrupts on page 9-25.Reference• Debug hardware TCP/IP port numbering on page 9-6• DCC modes on page 9-7• rvigdbconfig command syntax on page 9-27ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 9-23ID021112Non-Confidential