[ECOS] using fconfig

David Lewin david.lewin@europe-technologies.com
Wed Aug 4 15:07:00 GMT 2004


If you meant that the option :

"Merged config data adn FIS directory " should be unchecked,
the Redboot configuration is therefore ok.

----- Original Message ----- 
From: "Gary Thomas" <gary@mlbassoc.com>
To: "David Lewin" <david.lewin@europe-technologies.com>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Wednesday, August 04, 2004 4:47 PM
Subject: Re: [ECOS] using fconfig


> On Wed, 2004-08-04 at 08:47, David Lewin wrote:
> > Looks like strange :
> >
> > is it normal that when doing a fconfig -i, the call of the flash_erase
is
> > executed
> > at the same address that the FIS directory,
> > that is to say, if you take in account that :
> >
> > Name                  FLASH addr    Mem addr           Length
Entry
> > point
> > RedBoot             0x01000000     0x01000000    0x00020000  0x00000000
> > RedBoot config   0x0107EC00   0x0107EC00    0x00001000  0x00000000
> > FIS directory      0x0107F800    0x0107F800     0x00000400  0x00000000
> >
> > Boot script timeout (1000ms resolution): 0
> > Update RedBoot non-volatile configuration - continue (y/n)? y
> >  ... Erase from 0x0107ec00-0x0107fbff: ...
> > My Debug string : flash_erase with block: 107f800 / block_size :400
> > $T0a0f:00000801;0d:f8050
> >
> > does someone knows ?
>
> Look at your configuration - the default is for the 'fconfig' data to
> be stored in the same FLASH [erase] block as the FIS directory.
>
> You really should work out how to get ROMRAM mode working.
>
> > .
> > ----- Original Message ----- 
> > From: "David Lewin" <david.lewin@europe-technologies.com>
> > To: "Gary Thomas" <gary@mlbassoc.com>
> > Cc: <ecos-discuss@sources.redhat.com>
> > Sent: Wednesday, August 04, 2004 2:01 PM
> > Subject: Re: [ECOS] using fconfig
> >
> >
> > > thanks gary,
> > >
> > > I tried it and this compiled Redboot to be in such a way that it
didn't
> > > start at all.
> > >
> > > Therefore, for me, it enforce the idea that the Flash driver seems to
be
> > > executed in
> > > RAM .
> > >
> > > ----- Original Message ----- 
> > > From: "Gary Thomas" <gary@mlbassoc.com>
> > > To: "David Lewin" <david.lewin@europe-technologies.com>
> > > Cc: <ecos-discuss@sources.redhat.com>
> > > Sent: Wednesday, August 04, 2004 12:28 PM
> > > Subject: Re: [ECOS] using fconfig
> > >
> > >
> > > > On Wed, 2004-08-04 at 03:28, David Lewin wrote:
> > > > > The facts :
> > > > > I'm workin in flash with an ARM processor.
> > > > >
> > > > > the fis init is working ok, I can see
> > > > > -Redboot
> > > > > - Redboot config
> > > > > - FIS directory
> > > > >
> > > > > directories that have been created.
> > > > >
> > > > > My question is :
> > > > >
> > > > > what can make a fconfig -i crashing redboot[ROM] when I try
> > > > > to create a new config ?
> > > > > while debugging in RAM (insight & gdb dislike Flash debugging)
> > > > > is ok to create my config.
> > > >
> > > > Check that the FLASH drivers you use are ROM-friendly.  In other
> > > > words, while you are writing to the FLASH, you can't be executing
> > > > from it at the same time.
> > > >
> > > > Note: probably the easiest way around this is to run RedBoot
> > > > in ROMRAM mode instead.
> > > >
> > > > -- 
> > > > Gary Thomas <gary@mlbassoc.com>
> > > > MLB Associates
> > > >
> > > >
> > > > -- 
> > > > Before posting, please read the FAQ:
http://ecos.sourceware.org/fom/ecos
> > > > and search the list archive:
http://ecos.sourceware.org/ml/ecos-discuss
> > >
> > >
> > > -- 
> > > Before posting, please read the FAQ:
http://ecos.sourceware.org/fom/ecos
> > > and search the list archive:
http://ecos.sourceware.org/ml/ecos-discuss
> -- 
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
>
>
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



More information about the Ecos-discuss mailing list