Connection methods for each debugging mode

How you connect to a target determines the debugging mode. The following connection methods are available for each debugging mode:

Show/hideHalt-mode debugging

Halt-mode debugging is the simplest method of debugging a target with GDB. You directly connect to debug hardware, that then controls the starting and stopping of the processor. This method of connecting is subsequently referred to as an RVI-GDB connection.

Show/hideMonitor-mode debugging

Monitor-mode debugging requires that your target application communicate with GDB using the 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 connections

Semi-transparent connections to GDB stubs. The GDB stub communicates with the GDB client using the DCC channel as a serial port. The debug hardware unit makes this connection available on a TCP/IP port to which the GDB clinet connects. The GDB stub must be compiled into the target application.

Target-GDB-Virtual Ethernet connections

An extension to Target-GDB connections for standalone applications running an IP stack. The GDB stub communicates with the GDB client using the DCC channel as an Ethernet channel. The debug hardware unit makes this connection available on a TCP/IP port to which the GDB client connects.

GDBserver connections

An alternative to Target-GDB-Virtual Ethernet connections where the target is running gdbserver running under an operating system (OS).

GDB-NFS connections

Connections to the root filesystem on the target OS that is mounted over NFS. The debug hardware unit acts as a bridge between the debug host and the target OS.

Show/hideSee also

Copyright © 2010-2012 ARM. All rights reserved.ARM DUI 0498G
Non-ConfidentialID071612