This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: is this correct mailing list for redboot relatedquestions
On Wed, 2005-02-02 at 06:04 -0500, Alfred Wong wrote:
> Hi,
>
> First of all thanks for your reply ..
> I understand that its a volunteer thing, but as we were getting no
> answer for long, so thought will check in case we are on the right
> channel and / or questions were too obvious to be answered ..
>
> anyways, some questions on what u said ..
> basically we have been using u-boot for some time and our partitions /
> layout is something like this ..
>
> u-boot
> u-boot config
> kernel
> root fs
> app's
> config area (application / product related config like passwords, etc )
>
> We are short of space and I can see in my redboot that its taking
> nearly 0x1000 and 0x20000 for config and fis directory respectively ..
Those are typically combined into one FLASH erase block.
>
> Please correct me if I am wrong in my thoughts below :
>
> We have only one configuration file .. as in only one image of kernel ,etc ..
> so we dont need to have config area .. RIGHT ??
This is where RedBoot stores it's important data. You can do without,
but you'll have no way to dynamically configure RedBoot's behaviour.
For example, you need this if you want to use a boot time script (like
to automatically boot Linux :-)
>
> and similarly as files are being stored in separate partitions per se
> .. we dont need fis image area .. am I correct ?
>
> If images are to be upgraded from redboot we can use the known
> partition address'es to save new images ..
You _can_, but there is so little to be gained by not using the FIS
completely. The directory, and 'fconfig' data, only take a single
erase block.
>
>
> Cheers,
> Alfred
>
> On Wed, 02 Feb 2005 02:59:40 -0700, Gary Thomas <gary@mlbassoc.com> wrote:
> > On Wed, 2005-02-02 at 04:43 -0500, Alfred Wong wrote:
> > > Hi,
> > >
> > > I have just started to explore the redboot for ixdp425 ,, and am
> > > having some question ..
> > > Nobody has been answering my or my colleague Sumit Chauhan's questions
> > > on the list ..
> > > Is this the correct list for questions we are facing .. ?
> > >
> > > May be our questions are very elementary and basic, but atleast
> > > someone could answer them and help us also learn.
> >
> > It is indeed the proper list for such questions and I was about to
> > post an answer to your previous query. Note: this is a volunteer
> > project - you should not expect an answer immediately.
> >
> > As for how RedBoot uses the FLASH, there is a very complete section
> > on this in the manual:
> > http://sources.redhat.com/ecos/docs-latest/redboot/redboot-guide.html
> >
> > RedBoot provides tools/commands to manipulate the FLASH. These are
> > the 'FIS' (FLASH Image System) and 'FCONFIG' (FLASH Configuration).
> > With these commands, images (files) can be stored in FLASH, loaded
> > into memory from FLASH, etc, as well as some persistent data kept
> > in FLASH. The layout of the FLASH device is automatically detected
> > by RedBoot. By default, you will get an image for RedBoot itself
> > (typically at the bottom of the FLASH device, but this depends on
> > the target), a directory of images (kept in the FLASH as a separate
> > image) and FCONFIG data. e.g.
> >
> > RedBoot> fis list
> > Name FLASH addr Mem addr Length Entry point
> > RedBoot 0x60000000 0x60000000 0x00040000 0x00000000
> > RedBoot config 0x60F80000 0x60F80000 0x00001000 0x00000000
> > FIS directory 0x60FC0000 0x60FC0000 0x00040000 0x00000000
> >
> > --
> > ------------------------------------------------------------
> > Gary Thomas | Consulting for the
> > MLB Associates | Embedded world
> > ------------------------------------------------------------
> >
> >
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss