|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Installing <productname>eCos</productname>
|
Installing <productname>eCos</productname>
|
|
|
|
|
|
|
|
|
System Requirements
|
System Requirements
|
|
|
|
|
|
|
|
|
Standard Intel architecture PC running
|
Standard Intel architecture PC running
|
Linux (tested on recent Red Hat, SuSE and Debian distributions),
|
Linux (tested on recent Red Hat, SuSE and Debian distributions),
|
Microsoft Windows NT (no earlier than 4.0 + SP6a), Windows 2000 and
|
Microsoft Windows NT (no earlier than 4.0 + SP6a), Windows 2000 and
|
Windows XP. Linux distributions from other vendors may also work, but
|
Windows XP. Linux distributions from other vendors may also work, but
|
are currently untested.
|
are currently untested.
|
|
|
|
|
|
|
Enough disk space for the installed
|
Enough disk space for the installed
|
distribution. The eCos installation process
|
distribution. The eCos installation process
|
will detail the various components of eCos
|
will detail the various components of eCos
|
and the compiler toolkit that can be installed, and their disk space
|
and the compiler toolkit that can be installed, and their disk space
|
requirements.
|
requirements.
|
|
|
|
|
|
|
64MB of RAM and a 350MHz or faster Pentium processor.
|
64MB of RAM and a 350MHz or faster Pentium processor.
|
|
|
|
|
|
|
|
|
If you are downloading the eCos
|
If you are downloading the eCos
|
release distribution from
|
release distribution from
|
URL="http://sources.redhat.com/ecos">sources.redhat.com/ecos,
|
URL="http://sources.redhat.com/ecos">sources.redhat.com/ecos,
|
you will also need space to store that image and to compile the
|
you will also need space to store that image and to compile the
|
toolchain and eCos from source.
|
toolchain and eCos from source.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Installation on Linux
|
Installation on Linux
|
|
|
|
|
Full instructions for the
|
Full instructions for the
|
URL="http://sources.redhat.com/ecos/getstart.html">downloading and
|
URL="http://sources.redhat.com/ecos/getstart.html">downloading and
|
installation of eCos on Linux hosts are provided on the eCos
|
installation of eCos on Linux hosts are provided on the eCos
|
website.
|
website.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Installation on Windows
|
Installation on Windows
|
|
|
|
|
Full instructions for the
|
Full instructions for the
|
URL="http://sources.redhat.com/ecos/getstart.html">downloading and
|
URL="http://sources.redhat.com/ecos/getstart.html">downloading and
|
installation of eCos on Windows hosts are provided on the
|
installation of eCos on Windows hosts are provided on the
|
eCos website.
|
eCos website.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Target Setup
|
Target Setup
|
|
|
While eCos supports a variety of
|
While eCos supports a variety of
|
targets, communication with all the targets happens in one of four
|
targets, communication with all the targets happens in one of four
|
ways. These are described in general below. Any details or variations
|
ways. These are described in general below. Any details or variations
|
from these descriptions will be found in the
|
from these descriptions will be found in the
|
eCos documentation for a specific target,
|
eCos documentation for a specific target,
|
in the appendix.
|
in the appendix.
|
|
|
|
|
<!-- <index></index> -->Connecting Via Serial Line
|
<!-- <index></index> -->Connecting Via Serial Line
|
|
|
Most targets will have RedBoot or GDB Stubs installed.
|
Most targets will have RedBoot or GDB Stubs installed.
|
These normally waits for GDB to connect at 38400 baud, using 8 data
|
These normally waits for GDB to connect at 38400 baud, using 8 data
|
bit, no parity bit and 1 stop-bit and no hardware flow control. Check
|
bit, no parity bit and 1 stop-bit and no hardware flow control. Check
|
the documentation for your target to ensure it uses this speed. If not,
|
the documentation for your target to ensure it uses this speed. If not,
|
adjust the following instructions accordingly.
|
adjust the following instructions accordingly.
|
|
|
The following instructions depend on your having selected
|
The following instructions depend on your having selected
|
the appropriate serial port on the host. That is, the serial port
|
the appropriate serial port on the host. That is, the serial port
|
which connects to the target's (primary) serial port. On
|
which connects to the target's (primary) serial port. On
|
Linux this could be /dev/ttyS0,
|
Linux this could be /dev/ttyS0,
|
while the same port on Windows would be named COM1.
|
while the same port on Windows would be named COM1.
|
Substitute the proper serial port name in the below.
|
Substitute the proper serial port name in the below.
|
|
|
Connect to the target by issuing the following commands in
|
Connect to the target by issuing the following commands in
|
GDB console mode:
|
GDB console mode:
|
|
|
|
|
(gdb) set remotebaud 38400
|
(gdb) set remotebaud 38400
|
(gdb) target remote /dev/ttyS0
|
(gdb) target remote /dev/ttyS0
|
|
|
|
|
In Insight, connect by opening the File->Target
|
In Insight, connect by opening the File->Target
|
Settings window and enter:
|
Settings window and enter:
|
|
|
|
|
Target: Remote/Serial
|
Target: Remote/Serial
|
Baud Rate: 38400
|
Baud Rate: 38400
|
Port: /dev/ttyS0
|
Port: /dev/ttyS0
|
|
|
|
|
Set other options according to preference, close the window
|
Set other options according to preference, close the window
|
and select
|
and select
|
Run->Connect to target.
|
Run->Connect to target.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<!-- <index></index> -->Connecting Via Ethernet
|
<!-- <index></index> -->Connecting Via Ethernet
|
|
|
Some targets allow GDB to connect via Ethernet - if so, it will
|
Some targets allow GDB to connect via Ethernet - if so, it will
|
be mentioned in the document describing the target. Substitute the
|
be mentioned in the document describing the target. Substitute the
|
target's assigned IP address or hostname for <hostname> in the
|
target's assigned IP address or hostname for <hostname> in the
|
following. Depending on how RedBoot has been configured, it will
|
following. Depending on how RedBoot has been configured, it will
|
either have this address allocated statically, or will acquire it via
|
either have this address allocated statically, or will acquire it via
|
BOOTP. In both cases RedBoot will report the IP address it is
|
BOOTP. In both cases RedBoot will report the IP address it is
|
listening on in its startup message printed on the serial port. The
|
listening on in its startup message printed on the serial port. The
|
<port> is the TCP port which RedBoot is listening on, usually
|
<port> is the TCP port which RedBoot is listening on, usually
|
9000. It is also listed in the target document.
|
9000. It is also listed in the target document.
|
|
|
Connect to the target by issuing the following command in
|
Connect to the target by issuing the following command in
|
GDB console mode:
|
GDB console mode:
|
|
|
|
|
(gdb) target remote <hostname>:<port>
|
(gdb) target remote <hostname>:<port>
|
|
|
|
|
In Insight, connect by opening the File->Target
|
In Insight, connect by opening the File->Target
|
Settings window and enter:
|
Settings window and enter:
|
|
|
|
|
Target: Remote/TCP
|
Target: Remote/TCP
|
Hostname: <hostname>
|
Hostname: <hostname>
|
Port: <port>
|
Port: <port>
|
|
|
|
|
Set other options according to
|
Set other options according to
|
preference, close the window and select Run->Connect to
|
preference, close the window and select Run->Connect to
|
target.
|
target.
|
|
|
|
|
|
|
|
|
|
|
|
|
<!-- <index></index> -->Using A Simulator Target
|
<!-- <index></index> -->Using A Simulator Target
|
|
|
GDB connects to all simulator targets using the same basic
|
GDB connects to all simulator targets using the same basic
|
command, although each simulator may require additional options.
|
command, although each simulator may require additional options.
|
These are listed in the document describing the target, and should
|
These are listed in the document describing the target, and should
|
be used when connecting.
|
be used when connecting.
|
|
|
Connect to the target by issuing the following command in
|
Connect to the target by issuing the following command in
|
GDB console mode:
|
GDB console mode:
|
|
|
|
|
(gdb) target sim [target specific options]
|
(gdb) target sim [target specific options]
|
|
|
|
|
In Insight, connect by opening the File->Target
|
In Insight, connect by opening the File->Target
|
Settings window and enter:
|
Settings window and enter:
|
|
|
|
|
Target: Simulator
|
Target: Simulator
|
Options: [target specific options]
|
Options: [target specific options]
|
|
|
|
|
Set other options according to preference, close the window and
|
Set other options according to preference, close the window and
|
select Run->Connect to target.
|
select Run->Connect to target.
|
|
|
|
|
|
|
|
|
|
|
|
|
Using A Synthetic Target
|
Using A Synthetic Target
|
|
|
Synthetic targets are special in that the built tests and
|
Synthetic targets are special in that the built tests and
|
applications actually run as native applications on the host. This
|
applications actually run as native applications on the host. This
|
means that there is no target to connect to. The test or application
|
means that there is no target to connect to. The test or application
|
can be run directly from the GDB console using:
|
can be run directly from the GDB console using:
|
|
|
|
|
(gdb) run
|
(gdb) run
|
|
|
|
|
or from Insight by pressing the Run icon.
|
or from Insight by pressing the Run icon.
|
There is therefore no need to connect to the target or download the
|
There is therefore no need to connect to the target or download the
|
application, so you should ignore GDB “target” and
|
application, so you should ignore GDB “target” and
|
“load” commands in any instructions found in other places
|
“load” commands in any instructions found in other places
|
in the documentation.
|
in the documentation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
