The Debug Sprite is invoked as follows:
> m68k-linux-gnu-sprite [options
]device-url
board-file
The device-url
specifies the
debug device to use to communicate with the board. It follows the
standard format:
scheme
:scheme-specific-part
[?device-options
]
Most device URL schemes also follow the regular format:
scheme
:[//hostname
:[port
]]/path
[?device-options
]
The meanings of hostname
,
port
, path
and device-options
parts depend on the
scheme
and are described below. The
following schemes are supported in Sourcery G++ Lite for ColdFire GNU/Linux:
pe
Use a P&E Microcomputer Systems debugging device. Refer to Section 5.4, “P&E Devices”.
ccs
Use a debugging device controlled by the Command Converter Server (CCS) utility, such as a CodeWarrior Ethernet TAP or USB TAP. Refer to Section 5.5, “Command Converter Server Devices”.
tblcf
Use a Turbo BDM Light ColdFire (e.g. Axiom AxBDM) debugging device. Refer to Section 5.6, “Turbo BDM Light ColdFire Devices”.
osbdm
Use an Open Source BDM debugging device. Refer to Section 5.7, “Open Source BDM Devices”.
The optional
?
portion is
allowed in all schemes. These allow additional device-specific
options of the form
device-options
.
Multiple options are concatenated using
name
=value
&
.
The board-file
specifies an XML
file that describes how to initialize the target board, as well as
other properties of the board used by the debugger. If
board-file
refers to a file (via a
relative or absolute pathname), it is read. Otherwise,
board-file
can be a board name, and the
toolchain's board directory is searched for a matching file.
See Section 5.10, “Supported Board Files” for
the list of supported boards, or invoke the Sprite with the
-b
option to list the available board files.
You can also write a custom board file; see
Section 5.11, “Board File Syntax” for more information about
the file format.
Both the device-url
and
board-file
command-line arguments are
required to correctly connect the Sprite to a target board.