This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: There is a way to change a 'fconfig' redboot value froma linux program
On Fri, 2006-04-21 at 18:31 +0200, thierry langlais wrote:
> It seems to be also the case when FIS and fconfig are not combined!
>
> Here are traces from linux at boot
> ...
> 0x00fe0000-0x00fff000 : "FIS directory"
> mtd: partition "FIS directory" doesn't end on an erase block -- force
> read-only
> 0x00fff000-0x01000000 : "RedBoot config"
> mtd: partition "RedBoot config" doesn't start on an erase block boundary
> -- force read-only
> ...
These still look combined to me. If you rebuild RedBoot to have them
be separate, you'll have to rebuild your FIS directory (fis init)
>
> Does someone know a way to use mdt-utils tools like fcp, unlock and
> erase on a RedBoot config partition ?
You should ask the MTD folks for guidance on this. Send mail to
linux-mtd@lists.infradead.org
>
> Thanks,
>
> Thierry.
>
> Le mercredi 19 avril 2006 à 10:07 +0100, David Vrabel a écrit :
> > Gary Thomas wrote:
> > >
> > > In Linux, you could use MTD to access the 'fconfig' data.
> >
> > Note that by default if you're using a combined FIS/fconfig block then
> > both FIS and fconfig will be read-only from Linux.
--
------------------------------------------------------------
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