Re: [ECOS] using fconfig

["David Lewin" <david dot lewin at europe-technologies dot com>]

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