OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [rtos/] [ecos-2.0/] [doc/] [html/] [user-guide/] [configuring-and-building-ecos-from-source.html] - Blame information for rev 174

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 28 unneback
<!-- 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.               -->
9
<HTML
10
><HEAD
11
><TITLE
12
>Configuring and Building eCos from Source</TITLE
13
><meta name="MSSmartTagsPreventParsing" content="TRUE">
14
<META
15
NAME="GENERATOR"
16
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
17
"><LINK
18
REL="HOME"
19
TITLE="eCos User Guide"
20
HREF="ecos-user-guide.html"><LINK
21
REL="UP"
22
TITLE="Programming With eCos"
23
HREF="user-guide-programming.html"><LINK
24
REL="PREVIOUS"
25
TITLE="Programming With eCos"
26
HREF="programming-with-ecos.html"><LINK
27
REL="NEXT"
28
TITLE="Configuration Tool on Windows and Linux Quick Start"
29
HREF="using-configtool-windows-linux.html"></HEAD
30
><BODY
31
CLASS="CHAPTER"
32
BGCOLOR="#FFFFFF"
33
TEXT="#000000"
34
LINK="#0000FF"
35
VLINK="#840084"
36
ALINK="#0000FF"
37
><DIV
38
CLASS="NAVHEADER"
39
><TABLE
40
SUMMARY="Header navigation table"
41
WIDTH="100%"
42
BORDER="0"
43
CELLPADDING="0"
44
CELLSPACING="0"
45
><TR
46
><TH
47
COLSPAN="3"
48
ALIGN="center"
49
>eCos User Guide</TH
50
></TR
51
><TR
52
><TD
53
WIDTH="10%"
54
ALIGN="left"
55
VALIGN="bottom"
56
><A
57
HREF="programming-with-ecos.html"
58
ACCESSKEY="P"
59
>Prev</A
60
></TD
61
><TD
62
WIDTH="80%"
63
ALIGN="center"
64
VALIGN="bottom"
65
></TD
66
><TD
67
WIDTH="10%"
68
ALIGN="right"
69
VALIGN="bottom"
70
><A
71
HREF="using-configtool-windows-linux.html"
72
ACCESSKEY="N"
73
>Next</A
74
></TD
75
></TR
76
></TABLE
77
><HR
78
ALIGN="LEFT"
79
WIDTH="100%"></DIV
80
><DIV
81
CLASS="CHAPTER"
82
><H1
83
><A
84
NAME="CONFIGURING-AND-BUILDING-ECOS-FROM-SOURCE">Chapter 11. Configuring and Building <SPAN
85
CLASS="PRODUCTNAME"
86
>eCos</SPAN
87
> from Source</H1
88
><DIV
89
CLASS="TOC"
90
><DL
91
><DT
92
><B
93
>Table of Contents</B
94
></DT
95
><DT
96
><A
97
HREF="configuring-and-building-ecos-from-source.html#ECOS-STARTUP-CONFIGS"
98
><SPAN
99
CLASS="PRODUCTNAME"
100
>eCos</SPAN
101
> Start-up Configurations</A
102
></DT
103
><DT
104
><A
105
HREF="using-configtool-windows-linux.html"
106
>Configuration Tool on Windows and Linux Quick Start</A
107
></DT
108
><DT
109
><A
110
HREF="using-ecosconfig-on-linux.html"
111
>Ecosconfig on Windows and Linux Quick Start</A
112
></DT
113
></DL
114
></DIV
115
><P
116
>This chapter documents the configuration of <SPAN
117
CLASS="PRODUCTNAME"
118
>eCos</SPAN
119
>. The process is
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
123
target support).</P
124
><DIV
125
CLASS="SECT1"
126
><H1
127
CLASS="SECT1"
128
><A
129
NAME="ECOS-STARTUP-CONFIGS"><SPAN
130
CLASS="PRODUCTNAME"
131
>eCos</SPAN
132
> Start-up Configurations</H1
133
><P
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
137
CLASS="PRODUCTNAME"
138
>eCos</SPAN
139
> Hardware Abstraction Layer (HAL package)
140
there are configuration options to support the different download
141
methods. <A
142
HREF="configuring-and-building-ecos-from-source.html#USER-GUIDE-DOWNLOAD-METHODS"
143
>Table 11-1</A
144
> summarizes the
145
ways in which an <SPAN
146
CLASS="PRODUCTNAME"
147
>eCos</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
154
><DIV
155
CLASS="TABLE"
156
><A
157
NAME="USER-GUIDE-DOWNLOAD-METHODS"><P
158
><B
159
>Table 11-1. Configuration for various download methods</B
160
></P
161
><TABLE
162
BORDER="1"
163
CLASS="CALSTABLE"
164
><THEAD
165
><TR
166
><TH
167
ALIGN="LEFT"
168
VALIGN="TOP"
169
>Download method</TH
170
><TH
171
ALIGN="LEFT"
172
VALIGN="TOP"
173
>HAL configuration</TH
174
></TR
175
></THEAD
176
><TBODY
177
><TR
178
><TD
179
ALIGN="LEFT"
180
VALIGN="TOP"
181
>Burn hardware ROM</TD
182
><TD
183
ALIGN="LEFT"
184
VALIGN="TOP"
185
>&nbsp;ROM or ROMRAM start-up</TD
186
></TR
187
><TR
188
><TD
189
ALIGN="LEFT"
190
VALIGN="TOP"
191
>Download to ROM emulator</TD
192
><TD
193
ALIGN="LEFT"
194
VALIGN="TOP"
195
>&nbsp;ROM or ROMRAM start-up</TD
196
></TR
197
><TR
198
><TD
199
ALIGN="LEFT"
200
VALIGN="TOP"
201
>Download to board with ROM Monitor</TD
202
><TD
203
ALIGN="LEFT"
204
VALIGN="TOP"
205
>&nbsp;RAM start-up</TD
206
></TR
207
><TR
208
><TD
209
ALIGN="LEFT"
210
VALIGN="TOP"
211
>Download to simulator without ROM Monitor</TD
212
><TD
213
ALIGN="LEFT"
214
VALIGN="TOP"
215
>&nbsp;ROM start-up</TD
216
></TR
217
><TR
218
><TD
219
ALIGN="LEFT"
220
VALIGN="TOP"
221
>Download to simulator with ROM Monitor</TD
222
><TD
223
ALIGN="LEFT"
224
VALIGN="TOP"
225
>&nbsp;RAM start-up</TD
226
></TR
227
><TR
228
><TD
229
ALIGN="LEFT"
230
VALIGN="TOP"
231
>Download to simulator ignoring devices</TD
232
><TD
233
ALIGN="LEFT"
234
VALIGN="TOP"
235
>&nbsp;SIM configuration</TD
236
></TR
237
><TR
238
><TD
239
ALIGN="LEFT"
240
VALIGN="TOP"
241
>Run synthetic target</TD
242
><TD
243
ALIGN="LEFT"
244
VALIGN="TOP"
245
>&nbsp;RAM start-up</TD
246
></TR
247
></TBODY
248
></TABLE
249
></DIV
250
><DIV
251
CLASS="CAUTION"
252
><P
253
></P
254
><TABLE
255
CLASS="CAUTION"
256
BORDER="1"
257
WIDTH="100%"
258
><TR
259
><TD
260
ALIGN="CENTER"
261
><B
262
>Caution</B
263
></TD
264
></TR
265
><TR
266
><TD
267
ALIGN="LEFT"
268
><P
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
275
<SPAN
276
CLASS="emphasis"
277
><I
278
CLASS="EMPHASIS"
279
>SID </I
280
></SPAN
281
>
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
285
run
286
or you use the ELF loader component to get a program into memory.</P
287
></TD
288
></TR
289
></TABLE
290
></DIV
291
><DIV
292
CLASS="NOTE"
293
><BLOCKQUOTE
294
CLASS="NOTE"
295
><P
296
><B
297
>Note: </B
298
>Configuring <SPAN
299
CLASS="PRODUCTNAME"
300
>eCos</SPAN
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,
304
and the MN10300 and
305
TX39 simulators can run binaries built for stdeval1 and jmr3904
306
target boards.
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
311
the <TT
312
CLASS="OPTION"
313
>--board=jmr3904pal</TT
314
>
315
option instead of
316
<TT
317
CLASS="OPTION"
318
>--board=jmr3904</TT
319
></P
320
></BLOCKQUOTE
321
></DIV
322
><DIV
323
CLASS="NOTE"
324
><BLOCKQUOTE
325
CLASS="NOTE"
326
><P
327
><B
328
>Note: </B
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
334
></BLOCKQUOTE
335
></DIV
336
><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
340
></DIV
341
></DIV
342
><DIV
343
CLASS="NAVFOOTER"
344
><HR
345
ALIGN="LEFT"
346
WIDTH="100%"><TABLE
347
SUMMARY="Footer navigation table"
348
WIDTH="100%"
349
BORDER="0"
350
CELLPADDING="0"
351
CELLSPACING="0"
352
><TR
353
><TD
354
WIDTH="33%"
355
ALIGN="left"
356
VALIGN="top"
357
><A
358
HREF="programming-with-ecos.html"
359
ACCESSKEY="P"
360
>Prev</A
361
></TD
362
><TD
363
WIDTH="34%"
364
ALIGN="center"
365
VALIGN="top"
366
><A
367
HREF="ecos-user-guide.html"
368
ACCESSKEY="H"
369
>Home</A
370
></TD
371
><TD
372
WIDTH="33%"
373
ALIGN="right"
374
VALIGN="top"
375
><A
376
HREF="using-configtool-windows-linux.html"
377
ACCESSKEY="N"
378
>Next</A
379
></TD
380
></TR
381
><TR
382
><TD
383
WIDTH="33%"
384
ALIGN="left"
385
VALIGN="top"
386
>Programming With <SPAN
387
CLASS="PRODUCTNAME"
388
>eCos</SPAN
389
></TD
390
><TD
391
WIDTH="34%"
392
ALIGN="center"
393
VALIGN="top"
394
><A
395
HREF="user-guide-programming.html"
396
ACCESSKEY="U"
397
>Up</A
398
></TD
399
><TD
400
WIDTH="33%"
401
ALIGN="right"
402
VALIGN="top"
403
>Configuration Tool on Windows and Linux Quick Start</TD
404
></TR
405
></TABLE
406
></DIV
407
></BODY
408
></HTML
409
>

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.