1 <!-- Copyright (C) 2003 Red Hat, Inc. -->
2 <!-- This material may be distributed only subject to the terms -->
3 <!-- and conditions set forth in the Open Publication License, v1.0 -->
4 <!-- or later (the latest version is presently available at -->
5 <!-- http://www.opencontent.org/openpub/). -->
6 <!-- Distribution of the work or derivative of the work in any -->
7 <!-- standard (paper) book form is prohibited unless prior -->
8 <!-- permission is obtained from the copyright holder. -->
12 >Configuring and Building eCos from Source</TITLE
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="eCos User Guide"
20 HREF="ecos-user-guide.html"><LINK
22 TITLE="Programming With eCos"
23 HREF="user-guide-programming.html"><LINK
25 TITLE="Programming With eCos"
26 HREF="programming-with-ecos.html"><LINK
28 TITLE="Configuration Tool on Windows and Linux Quick Start"
29 HREF="using-configtool-windows-linux.html"></HEAD
40 SUMMARY="Header navigation table"
57 HREF="programming-with-ecos.html"
71 HREF="using-configtool-windows-linux.html"
84 NAME="CONFIGURING-AND-BUILDING-ECOS-FROM-SOURCE">Chapter 11. Configuring and Building <SPAN
97 HREF="configuring-and-building-ecos-from-source.html#ECOS-STARTUP-CONFIGS"
101 > Start-up Configurations</A
105 HREF="using-configtool-windows-linux.html"
106 >Configuration Tool on Windows and Linux Quick Start</A
110 HREF="using-ecosconfig-on-linux.html"
111 >Ecosconfig on Windows and Linux Quick Start</A
116 >This chapter documents the configuration of <SPAN
120 the same for any of the supported targets: you may select a
121 hardware target (if you have a board available), any one of the
122 simulators, or a synthetic target (if your host platform has synthetic
129 NAME="ECOS-STARTUP-CONFIGS"><SPAN
132 > Start-up Configurations</H1
134 >There are various ways to download an executable image to a
135 target board, and these involve different ways of preparing the
136 executable image. In the <SPAN
139 > Hardware Abstraction Layer (HAL package)
140 there are configuration options to support the different download
142 HREF="configuring-and-building-ecos-from-source.html#USER-GUIDE-DOWNLOAD-METHODS"
145 ways in which an <SPAN
148 > image can be prepared for different types of
149 download. This is not an exhaustive list, some targets define
150 additional start-up types of their own. Where a ROM Monitor is
151 mentioned, this will usually be RedBoot, although on some older, or
152 low resource, targets you may need to use CygMon or the GDB stubs ROM,
153 see the target documentation for details.</P
157 NAME="USER-GUIDE-DOWNLOAD-METHODS"><P
159 >Table 11-1. Configuration for various download methods</B
173 >HAL configuration</TH
181 >Burn hardware ROM</TD
185 > ROM or ROMRAM start-up</TD
191 >Download to ROM emulator</TD
195 > ROM or ROMRAM start-up</TD
201 >Download to board with ROM Monitor</TD
205 > RAM start-up</TD
211 >Download to simulator without ROM Monitor</TD
215 > ROM start-up</TD
221 >Download to simulator with ROM Monitor</TD
225 > RAM start-up</TD
231 >Download to simulator ignoring devices</TD
235 > SIM configuration</TD
241 >Run synthetic target</TD
245 > RAM start-up</TD
269 >You cannot run an application configured for RAM start-up
270 on the simulator directly: it will fail during start-up. You can
271 only download it to the simulator if
272 you are already running RedBoot in the simulator,
273 as described in the toolchain documentation
274 or you load through the
282 GDB debugging component. This is not the same as the simulated
283 stub, since it does not require a target program to be running to
284 get GDB to talk to it. It can be done before letting the simulator
286 or you use the ELF loader component to get a program into memory.</P
301 >' HAL package for simulation should
302 rarely be needed for real development; binaries built with such
303 a kernel will not run on target boards at all,
305 TX39 simulators can run binaries built for stdeval1 and jmr3904
307 The main use for a ``simulation'' configuration
308 is if you are trying to work around problems with the device drivers
309 or with the simulator. Also note that when using a TX39 system configured
310 for simulator start-up you should then invoke the simulator with
313 >--board=jmr3904pal</TT
329 >If your chosen architecture does not have simulator support,
330 then the combinations above that refer to the simulator do not apply.
331 Similarly, if your chosen platform does not have RedBoot
332 ROM support, the combinations listed above that use
333 RedBoot do not apply.</P
337 >The debugging environment for most developers will be either
338 a hardware board or the simulator, in which case they will be able
339 to select a single HAL configuration.</P
347 SUMMARY="Footer navigation table"
358 HREF="programming-with-ecos.html"
367 HREF="ecos-user-guide.html"
376 HREF="using-configtool-windows-linux.html"
386 >Programming With <SPAN
395 HREF="user-guide-programming.html"
403 >Configuration Tool on Windows and Linux Quick Start</TD