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