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

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [rtos/] [ecos-2.0/] [doc/] [html/] [ref/] [hal-linker-scripts.html] - Blame information for rev 232

Go to most recent revision | Details | Compare with Previous | View Log


<!-- Copyright (C) 2003 Red Hat, Inc.                                -->
<!-- This material may be distributed only subject to the terms      -->
<!-- and conditions set forth in the Open Publication License, v1.0  -->
<!-- or later (the latest version is presently available at          -->
<!-- http://www.opencontent.org/openpub/).                           -->
<!-- Distribution of the work or derivative of the work in any       -->
<!-- standard (paper) book form is prohibited unless prior           -->
<!-- permission is obtained from the copyright holder.               -->
<HTML
><HEAD
><TITLE
>Linker Scripts</TITLE
><meta name="MSSmartTagsPreventParsing" content="TRUE">
<META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="eCos Reference Manual"
HREF="ecos-ref.html"><LINK
REL="UP"
TITLE="HAL Interfaces"
HREF="hal-interfaces.html"><LINK
REL="PREVIOUS"
TITLE="Cache Control"
HREF="hal-cache-control.html"><LINK
REL="NEXT"
TITLE="Diagnostic Support"
HREF="hal-diagnostic-support.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>eCos Reference Manual</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="hal-cache-control.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 9. HAL Interfaces</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="hal-diagnostic-support.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
><H1
CLASS="SECTION"
><A
NAME="HAL-LINKER-SCRIPTS">Linker Scripts</H1
><P
>When an eCos application is linked it must be done under the control
of a linker script. This script defines the memory areas, addresses
and sized, into which the code and data are to be put, and allocates
the various sections generated by the compiler to these.</P
><P
>The linker script actually used is in
<TT
CLASS="FILENAME"
>lib/target.ld</TT
> in the install directory. This is
actually manufactured out of two other files: a base linker script and
an <TT
CLASS="LITERAL"
>.ldi</TT
> file that was generated by the memory
layout tool.</P
><P
>The base linker script is usually supplied either by the architecture
HAL or the variant HAL. It consists of a set of linker script
fragments, in the form of C preprocessor macros, that define the major
output sections to be generated by the link operation. The
<TT
CLASS="LITERAL"
>.ldi</TT
> file, which is <TT
CLASS="LITERAL"
>#include'ed</TT
>
by the base linker script, uses these macro definitions to assign the
output sections to the required memory areas and link addresses.</P
><P
>The <TT
CLASS="LITERAL"
>.ldi</TT
> file is supplied by the platform HAL, and
contains knowledge of the memory layout of the target platform. These
files generally conform to a standard naming convention, each file
being of the form:</P
><P
><TT
CLASS="FILENAME"
>pkgconf/mlt_&lt;architecture&gt;_&lt;variant&gt;_&lt;platform&gt;_&lt;startup&gt;.ldi</TT
></P
><P
>where <TT
CLASS="LITERAL"
>&lt;architecture&gt;</TT
>,
<TT
CLASS="LITERAL"
>&lt;variant&gt;</TT
> and
<TT
CLASS="LITERAL"
>&lt;platform&gt;</TT
> are the respective HAL package
names and <TT
CLASS="LITERAL"
>&lt;startup&gt;</TT
> is the startup type which
is usually one of <TT
CLASS="LITERAL"
>ROM</TT
>, <TT
CLASS="LITERAL"
>RAM</TT
> or
<TT
CLASS="LITERAL"
>ROMRAM</TT
>.</P
><P
>In addition to the <TT
CLASS="LITERAL"
>.ldi</TT
> file, there is also a
congruously name <TT
CLASS="LITERAL"
>.h</TT
> file. This may be used by the
application to access information defined in the
<TT
CLASS="LITERAL"
>.ldi</TT
> file. Specifically it contains the memory
layout defined there, together with any additional section names
defined by the user. Examples of the latter are heap areas or PCI bus
memory access windows.</P
><P
>The <TT
CLASS="LITERAL"
>.ldi</TT
> is manufactured by the <SPAN
CLASS="APPLICATION"
>Memory
Layout Tool</SPAN
> (MLT). The <SPAN
CLASS="APPLICATION"
>MLT</SPAN
> saves the memory
configuration into a file named</P
><P
><TT
CLASS="FILENAME"
>include/pkgconf/mlt_&lt;architecture&gt;_&lt;variant&gt;_&lt;platform&gt;_&lt;startup&gt;.mlt</TT
></P
><P
>in the platform HAL. This file is used by the
<SPAN
CLASS="APPLICATION"
>MLT</SPAN
> to manufacture both the
<TT
CLASS="LITERAL"
>.ldi</TT
> and <TT
CLASS="LITERAL"
>.h</TT
> files. Users should
beware that direct edits the either of these files may be overwritten
if the <SPAN
CLASS="APPLICATION"
>MLT</SPAN
> is run and regenerates them from the
<TT
CLASS="LITERAL"
>.mlt</TT
> file.</P
><P
>The names of the <TT
CLASS="LITERAL"
>.ldi</TT
> and <TT
CLASS="LITERAL"
>.h</TT
>
files are defined by macro definitions in
<TT
CLASS="FILENAME"
>pkgconf/system.h</TT
>. These are
<TT
CLASS="LITERAL"
>CYGHWR_MEMORY_LAYOUT_LDI</TT
> and
<TT
CLASS="LITERAL"
>CYGHWR_MEMORY_LAYOUT_H</TT
> respectively. While there
will be little need for the application to refer to the
<TT
CLASS="LITERAL"
>.ldi</TT
> file directly, it may include the
<TT
CLASS="LITERAL"
>.h</TT
> file as follows:</P
><TABLE
BORDER="5"
BGCOLOR="#E0E0F0"
WIDTH="70%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>#include CYGHWR_MEMORY_LAYOUT_H</PRE
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="hal-cache-control.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="ecos-ref.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="hal-diagnostic-support.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Cache Control</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="hal-interfaces.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Diagnostic Support</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

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			`>Linker Scripts</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 Reference Manual"`
20			`HREF="ecos-ref.html"><LINK`
21			`REL="UP"`
22			`TITLE="HAL Interfaces"`
23			`HREF="hal-interfaces.html"><LINK`
24			`REL="PREVIOUS"`
25			`TITLE="Cache Control"`
26			`HREF="hal-cache-control.html"><LINK`
27			`REL="NEXT"`
28			`TITLE="Diagnostic Support"`
29			`HREF="hal-diagnostic-support.html"></HEAD`
30			`><BODY`
31			`CLASS="SECTION"`
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 Reference Manual</TH`
50			`></TR`
51			`><TR`
52			`><TD`
53			`WIDTH="10%"`
54			`ALIGN="left"`
55			`VALIGN="bottom"`
56			`><A`
57			`HREF="hal-cache-control.html"`
58			`ACCESSKEY="P"`
59			`>Prev</A`
60			`></TD`
61			`><TD`
62			`WIDTH="80%"`
63			`ALIGN="center"`
64			`VALIGN="bottom"`
65			`>Chapter 9. HAL Interfaces</TD`
66			`><TD`
67			`WIDTH="10%"`
68			`ALIGN="right"`
69			`VALIGN="bottom"`
70			`><A`
71			`HREF="hal-diagnostic-support.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="SECTION"`
82			`><H1`
83			`CLASS="SECTION"`
84			`><A`
85			`NAME="HAL-LINKER-SCRIPTS">Linker Scripts</H1`
86			`><P`
87			`>When an eCos application is linked it must be done under the control`
88			`of a linker script. This script defines the memory areas, addresses`
89			`and sized, into which the code and data are to be put, and allocates`
90			`the various sections generated by the compiler to these.</P`
91			`><P`
92			`>The linker script actually used is in`
93			`<TT`
94			`CLASS="FILENAME"`
95			`>lib/target.ld</TT`
96			`> in the install directory. This is`
97			`actually manufactured out of two other files: a base linker script and`
98			`an <TT`
99			`CLASS="LITERAL"`
100			`>.ldi</TT`
101			`> file that was generated by the memory`
102			`layout tool.</P`
103			`><P`
104			`>The base linker script is usually supplied either by the architecture`
105			`HAL or the variant HAL. It consists of a set of linker script`
106			`fragments, in the form of C preprocessor macros, that define the major`
107			`output sections to be generated by the link operation. The`
108			`<TT`
109			`CLASS="LITERAL"`
110			`>.ldi</TT`
111			`> file, which is <TT`
112			`CLASS="LITERAL"`
113			`>#include'ed</TT`
114			`>`
115			`by the base linker script, uses these macro definitions to assign the`
116			`output sections to the required memory areas and link addresses.</P`
117			`><P`
118			`>The <TT`
119			`CLASS="LITERAL"`
120			`>.ldi</TT`
121			`> file is supplied by the platform HAL, and`
122			`contains knowledge of the memory layout of the target platform. These`
123			`files generally conform to a standard naming convention, each file`
124			`being of the form:</P`
125			`><P`
126			`><TT`
127			`CLASS="FILENAME"`
128			`>pkgconf/mlt_<architecture>_<variant>_<platform>_<startup>.ldi</TT`
129			`></P`
130			`><P`
131			`>where <TT`
132			`CLASS="LITERAL"`
133			`><architecture></TT`
134			`>,`
135			`<TT`
136			`CLASS="LITERAL"`
137			`><variant></TT`
138			`> and`
139			`<TT`
140			`CLASS="LITERAL"`
141			`><platform></TT`
142			`> are the respective HAL package`
143			`names and <TT`
144			`CLASS="LITERAL"`
145			`><startup></TT`
146			`> is the startup type which`
147			`is usually one of <TT`
148			`CLASS="LITERAL"`
149			`>ROM</TT`
150			`>, <TT`
151			`CLASS="LITERAL"`
152			`>RAM</TT`
153			`> or`
154			`<TT`
155			`CLASS="LITERAL"`
156			`>ROMRAM</TT`
157			`>.</P`
158			`><P`
159			`>In addition to the <TT`
160			`CLASS="LITERAL"`
161			`>.ldi</TT`
162			`> file, there is also a`
163			`congruously name <TT`
164			`CLASS="LITERAL"`
165			`>.h</TT`
166			`> file. This may be used by the`
167			`application to access information defined in the`
168			`<TT`
169			`CLASS="LITERAL"`
170			`>.ldi</TT`
171			`> file. Specifically it contains the memory`
172			`layout defined there, together with any additional section names`
173			`defined by the user. Examples of the latter are heap areas or PCI bus`
174			`memory access windows.</P`
175			`><P`
176			`>The <TT`
177			`CLASS="LITERAL"`
178			`>.ldi</TT`
179			`> is manufactured by the <SPAN`
180			`CLASS="APPLICATION"`
181			`>Memory`
182			`Layout Tool</SPAN`
183			`> (MLT). The <SPAN`
184			`CLASS="APPLICATION"`
185			`>MLT</SPAN`
186			`> saves the memory`
187			`configuration into a file named</P`
188			`><P`
189			`><TT`
190			`CLASS="FILENAME"`
191			`>include/pkgconf/mlt_<architecture>_<variant>_<platform>_<startup>.mlt</TT`
192			`></P`
193			`><P`
194			`>in the platform HAL. This file is used by the`
195			`<SPAN`
196			`CLASS="APPLICATION"`
197			`>MLT</SPAN`
198			`> to manufacture both the`
199			`<TT`
200			`CLASS="LITERAL"`
201			`>.ldi</TT`
202			`> and <TT`
203			`CLASS="LITERAL"`
204			`>.h</TT`
205			`> files. Users should`
206			`beware that direct edits the either of these files may be overwritten`
207			`if the <SPAN`
208			`CLASS="APPLICATION"`
209			`>MLT</SPAN`
210			`> is run and regenerates them from the`
211			`<TT`
212			`CLASS="LITERAL"`
213			`>.mlt</TT`
214			`> file.</P`
215			`><P`
216			`>The names of the <TT`
217			`CLASS="LITERAL"`
218			`>.ldi</TT`
219			`> and <TT`
220			`CLASS="LITERAL"`
221			`>.h</TT`
222			`>`
223			`files are defined by macro definitions in`
224			`<TT`
225			`CLASS="FILENAME"`
226			`>pkgconf/system.h</TT`
227			`>. These are`
228			`<TT`
229			`CLASS="LITERAL"`
230			`>CYGHWR_MEMORY_LAYOUT_LDI</TT`
231			`> and`
232			`<TT`
233			`CLASS="LITERAL"`
234			`>CYGHWR_MEMORY_LAYOUT_H</TT`
235			`> respectively. While there`
236			`will be little need for the application to refer to the`
237			`<TT`
238			`CLASS="LITERAL"`
239			`>.ldi</TT`
240			`> file directly, it may include the`
241			`<TT`
242			`CLASS="LITERAL"`
243			`>.h</TT`
244			`> file as follows:</P`
245			`><TABLE`
246			`BORDER="5"`
247			`BGCOLOR="#E0E0F0"`
248			`WIDTH="70%"`
249			`><TR`
250			`><TD`
251			`><PRE`
252			`CLASS="PROGRAMLISTING"`
253			`>#include CYGHWR_MEMORY_LAYOUT_H</PRE`
254			`></TD`
255			`></TR`
256			`></TABLE`
257			`></DIV`
258			`><DIV`
259			`CLASS="NAVFOOTER"`
260			`><HR`
261			`ALIGN="LEFT"`
262			`WIDTH="100%"><TABLE`
263			`SUMMARY="Footer navigation table"`
264			`WIDTH="100%"`
265			`BORDER="0"`
266			`CELLPADDING="0"`
267			`CELLSPACING="0"`
268			`><TR`
269			`><TD`
270			`WIDTH="33%"`
271			`ALIGN="left"`
272			`VALIGN="top"`
273			`><A`
274			`HREF="hal-cache-control.html"`
275			`ACCESSKEY="P"`
276			`>Prev</A`
277			`></TD`
278			`><TD`
279			`WIDTH="34%"`
280			`ALIGN="center"`
281			`VALIGN="top"`
282			`><A`
283			`HREF="ecos-ref.html"`
284			`ACCESSKEY="H"`
285			`>Home</A`
286			`></TD`
287			`><TD`
288			`WIDTH="33%"`
289			`ALIGN="right"`
290			`VALIGN="top"`
291			`><A`
292			`HREF="hal-diagnostic-support.html"`
293			`ACCESSKEY="N"`
294			`>Next</A`
295			`></TD`
296			`></TR`
297			`><TR`
298			`><TD`
299			`WIDTH="33%"`
300			`ALIGN="left"`
301			`VALIGN="top"`
302			`>Cache Control</TD`
303			`><TD`
304			`WIDTH="34%"`
305			`ALIGN="center"`
306			`VALIGN="top"`
307			`><A`
308			`HREF="hal-interfaces.html"`
309			`ACCESSKEY="U"`
310			`>Up</A`
311			`></TD`
312			`><TD`
313			`WIDTH="33%"`
314			`ALIGN="right"`
315			`VALIGN="top"`
316			`>Diagnostic Support</TD`
317			`></TR`
318			`></TABLE`
319			`></DIV`
320			`></BODY`
321			`></HTML`
322			`>`

Browse

Tools

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [rtos/] [ecos-2.0/] [doc/] [html/] [ref/] [hal-linker-scripts.html] - Blame information for rev 232