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
- From: thierry langlais <thierry dot langlais at efixo dot com>
- To: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Cc: Gary Thomas <gary at mlbassoc dot com>, David Vrabel <dvrabel at arcom dot com>
- Date: Fri, 21 Apr 2006 18:31:22 +0200
- Subject: Re: [ECOS] There is a way to change a 'fconfig' redboot value froma linux program
- References: <1145376176.13516.7.camel@DEV01> <1145376552.17193.42.camel@hermes> <4445FDEC.3060601@arcom.com>
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
...
Does someone know a way to use mdt-utils tools like fcp, unlock and
erase on a RedBoot config partition ?
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.
>
> David Vrabel
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss