3 <!-- =============================================================== -->
5 <!-- installation.sgml -->
7 <!-- eCos User Guide -->
9 <!-- =============================================================== -->
10 <!-- ####COPYRIGHTBEGIN#### -->
12 <!-- =============================================================== -->
13 <!-- Copyright (C) 1997, 1998, 1999, 2000, 2001, 2002 Red Hat, Inc. -->
14 <!-- Copyright (C) 2003 Nick Garnett -->
15 <!-- This material may be distributed only subject to the terms -->
16 <!-- and conditions set forth in the Open Publication License, v1.0 -->
17 <!-- or later (the latest version is presently available at -->
18 <!-- http://www.opencontent.org/openpub/) -->
19 <!-- Distribution of the work or derivative of the work in any -->
20 <!-- standard (paper) book form is prohibited unless prior -->
21 <!-- permission obtained from the copyright holder -->
22 <!-- =============================================================== -->
24 <!-- ####COPYRIGHTEND#### -->
25 <!-- =============================================================== -->
26 <!-- #####DESCRIPTIONBEGIN#### -->
28 <!-- ####DESCRIPTIONEND#### -->
29 <!-- =============================================================== -->
33 <part ID="user-guide-installation">
34 <TITLE>Installing <productname>eCos</productname></TITLE>
36 <!-- {{{ System Requirements -->
38 <chapter id="user-guide-installation-requirements">
39 <title>System Requirements</title>
44 <PARA><!-- <conditionaltext> -->Standard Intel architecture PC running
45 Linux (tested on recent Red Hat, SuSE and Debian distributions),
46 Microsoft Windows NT (no earlier than 4.0 + SP6a), Windows 2000 and
47 Windows XP. Linux distributions from other vendors may also work, but
48 are currently untested. </PARA>
52 <PARA>Enough <!-- <index></index> --> disk space for the installed
53 distribution. The <productname>eCos</productname> installation process
54 will detail the various components of <productname>eCos</productname>
55 and the compiler toolkit that can be installed, and their disk space
60 <PARA>64MB of RAM and a 350MHz or faster Pentium processor.</PARA><!-- <conditionaltext> -->
65 <PARA>If you are downloading the <productname>eCos</productname>
66 release distribution from <ULINK
67 URL="http://ecos.sourceware.org">ecos.sourceware.org</ULINK>,
68 you will also need space to store that image and to compile the
69 toolchain and <productname>eCos</productname> from source.</PARA>
75 <!-- {{{ Installation on Linux -->
77 <chapter id="user-guide-installation-linux">
78 <title>Installation on Linux</title>
81 Full instructions for the <ULINK
82 URL="http://ecos.sourceware.org/getstart.html">downloading and
83 installation of eCos</ULINK> on Linux hosts are provided on the eCos
90 <!-- {{{ Installation on Windows -->
92 <chapter id="user-guide-installation-windows">
93 <title>Installation on Windows</title>
96 Full instructions for the <ULINK
97 URL="http://ecos.sourceware.org/getstart.html">downloading and
98 installation of eCos</ULINK> on Windows hosts are provided on the
105 <!-- {{{ Target Setup -->
107 <chapter id="user-guide-installation-target">
108 <title>Target Setup</title>
110 <PARA>While <productname>eCos</productname> supports a variety of
111 targets, communication with all the targets happens in one of four
112 ways. These are described in general below. Any details or variations
113 from these descriptions will be found in the
114 <productname>eCos</productname> documentation for a specific target,
115 in the appendix.</PARA>
117 <SECT1 id="connecting-target-serial">
118 <TITLE><!-- <index></index> -->Connecting Via Serial Line</TITLE>
120 <PARA>Most targets will have RedBoot or GDB Stubs installed.
121 These normally waits for GDB to connect at 38400 baud, using 8 data
122 bit, no parity bit and 1 stop-bit and no hardware flow control. Check
123 the documentation for your target to ensure it uses this speed. If not,
124 adjust the following instructions accordingly.</PARA>
126 <PARA>The following instructions depend on your having selected
127 the appropriate serial port on the host. That is, the serial port
128 which connects to the target's (primary) serial port. On
129 Linux this could be <FILENAME>/dev/ttyS0</FILENAME>,
130 while the same port on Windows would be named COM1.
131 Substitute the proper serial port name in the below.</PARA>
133 <PARA>Connect to the target by issuing the following commands in
134 GDB console mode:</PARA>
137 (gdb) set remotebaud 38400 <!-- <conditionaltext> -->
138 (gdb) target remote /dev/ttyS0
141 <PARA>In Insight, connect by opening the <EMPHASIS>File->Target
142 Settings</EMPHASIS> window and enter:</PARA>
145 Target: Remote/Serial
150 <PARA>Set other options according to preference, close the window
152 <EMPHASIS>Run->Connect to target</EMPHASIS>.
157 <!-- ==================================================== -->
159 <SECT1 id="connecting-target-ethernet">
160 <TITLE><!-- <index></index> -->Connecting Via Ethernet</TITLE>
162 <PARA>Some targets allow GDB to connect via Ethernet - if so, it will
163 be mentioned in the document describing the target. Substitute the
164 target's assigned IP address or hostname for <hostname> in the
165 following. Depending on how RedBoot has been configured, it will
166 either have this address allocated statically, or will acquire it via
167 BOOTP. In both cases RedBoot will report the IP address it is
168 listening on in its startup message printed on the serial port. The
169 <port> is the TCP port which RedBoot is listening on, usually
170 9000. It is also listed in the target document.</PARA>
172 <PARA>Connect to the target by issuing the following command in
173 GDB console mode:</PARA>
176 (gdb) target remote <hostname>:<port>
179 <PARA>In Insight, connect by opening the <EMPHASIS>File->Target
180 Settings</EMPHASIS> window and enter:</PARA>
184 Hostname: <hostname>
188 <PARA><!-- <conditionaltext> -->Set other options according to
189 preference, close the window and select <EMPHASIS>Run->Connect to
190 target</EMPHASIS>.</PARA>
194 <!-- ==================================================== -->
196 <SECT1 id="connecting-target-sim">
197 <TITLE><!-- <index></index> -->Using A Simulator Target</TITLE>
199 <PARA>GDB connects to all simulator targets using the same basic
200 command, although each simulator may require additional options.
201 These are listed in the document describing the target, and should
202 be used when connecting.</PARA>
204 <PARA>Connect to the target by issuing the following command in
205 GDB console mode:</PARA>
208 (gdb) target sim [target specific options]
211 <PARA>In Insight, connect by opening the <EMPHASIS>File->Target
212 Settings</EMPHASIS> window and enter:</PARA>
216 Options: [target specific options]
219 <PARA>Set other options according to preference, close the window and
220 select <EMPHASIS>Run->Connect to target</EMPHASIS>.</PARA>
224 <!-- ==================================================== -->
226 <SECT1 id="connecting-target-synth">
227 <TITLE>Using A Synthetic Target</TITLE>
229 <PARA>Synthetic targets are special in that the built tests and
230 applications actually run as native applications on the host. This
231 means that there is no target to connect to. The test or application
232 can be run directly from the GDB console using:</PARA>
238 <PARA>or from Insight by pressing the <EMPHASIS>Run</EMPHASIS> icon.
239 There is therefore no need to connect to the target or download the
240 application, so you should ignore GDB “target” and
241 “load” commands in any instructions found in other places
242 in the documentation.</PARA>