NOTE: This step is NOT required if prebuilt executables for the GDB were installed and they meet your target interface requirements.
GDB supports many configurations but requires some means of communicating between the host computer and target board. This communication can be via a serial port, Ethernet, BDM, or ROM emulator. The communication protocol can be the GDB remote protocol or GDB can talk directly to a ROM monitor. This setup is target board specific. Some of the configurations that have been successfully used with RTEMS applications are:
GDB is currently RTEMS thread/task aware only if you are using the remote debugging support via Ethernet. These are configured using gdb targets of the form CPU-RTEMS. Note the capital RTEMS.
It is recommended that when toolset binaries are available for your particular host, that they be used. Prebuilt binaries are much easier to install but in the case of gdb may or may not include support for your particular target board.
The following example illustrates the invocation of configure
and make
to build and install gdb-<VERSION> for the
m68k-rtems4.9 target:
mkdir b-gdb cd b-gdb ../gdb-<VERSION>/configure --target=m68k-rtems4.9 \ --prefix=/opt/rtems-4.9 make all make info make install
For some configurations, it is necessary to specify extra options
to configure
to enable and configure option components
such as a processor simulator. The following is a list of
configurations for which there are extra options:
--enable-sim --enable-sim-powerpc --enable-sim-timebase --enable-sim-hardware
--enable-sim
After gdb-<VERSION> is built and installed the
build directory b-gdb
may be removed.
For more information on the invocation of configure
, please
refer to the documentation for gdb-<VERSION> or
invoke the gdb-<VERSION> configure
command with the
--help
option.
Copyright © 1988-2008 OAR Corporation