Debugging on Motorola m68k targets

GDB needs to know these things to talk to your Motorola m68k:

1. that you want to use one of the following:
   • `target rom68k', the rom monitor for the IDP board.
   • `target cpu32bug', the rom monitor for other Motorola boards, such as the Motorola Business Card Computer, BCC.
   • `target est', the EST Net/300 emulator.
   • `target remote', the remote debugging interface for the Motorola m68k microprocessor.
2. what serial device connects your host to your m68k board (the first serial device available on your host is the default).
3. what speed to use over the serial device.

Use these GDB commands to specify the connection to your target board:

target m68k port

To run a program on the board, start up GDB with the name of your program as the argument. To connect to the board, use the command `target m68k port', where port is the name of the serial port connected to the board. If the program has not already been downloaded to the board, you may use the load command to download it. You can then use all the usual GDB commands. For example, this sequence connects to the target board through a serial port, and loads and runs a program called prog through the debugger:

host$ m68k-coff-gdb prog
GDB is free software and ...
(gdb) target cpu32bug /dev/ttyb
...
(gdb) load
...
(gdb) run

target m68k hostname:portnumber

You can specify a TCP/IP connection instead of a serial port, using the syntax hostname:portnumber (assuming your board is connected so that this makes sense; for instance, to a serial line managed by a terminal concentrator).

GDB also supports:

set remotedebug n

You can see some debugging information about communications with the board by setting the remotedebug variable.