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 >RedBoot Startup Mode</TITLE
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="eCos Reference Manual"
20 HREF="ecos-ref.html"><LINK
22 TITLE="Getting Started with RedBoot"
23 HREF="getting-started-with-redboot.html"><LINK
25 TITLE="RedBoot Editing Commands"
26 HREF="redboot-editing-commands.html"><LINK
28 TITLE="RedBoot Resource Usage"
29 HREF="resource-usage.html"></HEAD
40 SUMMARY="Header navigation table"
49 >eCos Reference Manual</TH
57 HREF="redboot-editing-commands.html"
65 >Chapter 1. Getting Started with RedBoot</TD
71 HREF="resource-usage.html"
85 NAME="STARTUP-MODE">RedBoot Startup Mode</H1
90 >RedBoot can normally be configured to run in a number of startup
91 modes (or just "modes" for short), determining its location of
92 residence and execution:
102 >In this mode, RedBoot both resides and executes from
103 ROM memory (flash or EPROM). This mode is used when there are limited
104 RAM resources. The flash commands cannot update the region of flash
105 where the RedBoot image resides. In order to update the RedBoot image
106 in flash, it is necessary to run a RAM mode instance of
113 >In this mode, RedBoot resides in ROM memory (flash or
114 EPROM), but is copied to RAM memory before it starts executing. The
115 RAM footprint is larger than for ROM mode, but there are two
116 advantages to make up for this: it normally runs faster (relevant
117 only on slower boards) and it is able to update the flash region
118 where the image resides.</P
124 >In this mode, RedBoot both resides and executes from
125 RAM memory. This is used for updating a primary ROM
126 mode image in situ and sometimes as part of the RedBoot installation
127 on the board when there's already an existing (non-RedBoot) boot
128 monitor available.</P
130 > You can only use ROM and ROMRAM mode images for booting a
131 board - a RAM mode image cannot run unless loaded by another ROM
132 monitor. There is no need for this startup mode if a RedBoot ROMRAM
133 mode image is the primary boot monitor. When this startup mode is
134 programmed into flash (as a convenience as it's fast to load from
135 flash) it will generally be named as "RedBoot[RAM]" in the FIS
142 The chosen mode has influence on flash and RAM resource usage (see
144 HREF="resource-usage.html"
145 >the Section called <I
146 >RedBoot Resource Usage</I
148 >) and the procedure of an in situ update
149 of RedBoot in flash (see <A
150 HREF="updating-redboot.html"
154 >The startup mode is controlled by the option CYG_HAL_STARTUP
155 which resides in the platform HAL. Some platforms provide only some of
156 the RAM, ROM, and ROMRAM modes, others provide additional
159 >To see mode of a currently executing RedBoot, issue the
163 > command, which prints the RedBoot banner,
164 including the startup mode (here ROM):
180 RedBoot(tm) bootstrap and debug environment <SPAN
187 Non-certified release, version UNKNOWN - built 13:31:57, May 17 2002</PRE
198 SUMMARY="Footer navigation table"
209 HREF="redboot-editing-commands.html"
227 HREF="resource-usage.html"
237 >RedBoot Editing Commands</TD
243 HREF="getting-started-with-redboot.html"
251 >RedBoot Resource Usage</TD