NAME

gdbterm - allow debugging a remote target using gdb DEPRICATED


SYNOPSIS

gdbterm <arguments>


Command-Line Arguments

Command-Line arguments are:

-b speed
Set the baud rate used when connected to a serial port. The speed should be specified as one of 9600, 19200, 38400, 115k.

-g socket
Set the TCP/IP socket gdbterm listens on. By default it listens on port 1042.

-h
Print help message

-m <MAC-address>
Connect using MAST, connecting to the target with the given MAC address. Optionally, the MAST port to use may be specified as well. For example:

gdbterm -m 00:20:AF:4A:B8:72 1089

-n
Do not do bit-8 multiplexing

-s serial-port
Connect to a serial port, e.g. -s /dev/ttyS0

-t host port
Connect via a terminal server with hostname host on port port, e.g -t spider1 2064

-v
Be verbose


DESCRIPTION

gdbterm is supplied BUT NOT supported. No ATMOS arm stub is currently available for the latest Helium chips

gdbterm acts as a proxy, sitting between gdb and a stub process running in an ATMOS target.

It talks to gdb using a TCP/IP connection (listening either on port 1042, or a port specified on the command line).

It talks to the target either via serial port (-s), via MAST (-m) or via a terminal server (-t).

When talking to the target via a serial port (or indirectly through a terminal server) console output from the target is multiplexed with gdb messages by setting or clearing bit 8 as appropriate. Gdbterm then writes console output to its standard output, and anything it receives on its standard input is passed to the target console.

This means that you can run gdbterm and use it for interacting with your target's console, while simultaneously debugging it.


SEE ALSO

Debugging Under ATMOS, DO-007065-TC

arm-elf-gdb