This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: redboot fis trouble
- From: Jonathan Larmour <jlarmour at redhat dot com>
- To: "Amin A. Khaef" <akhaef at ea dot oac dot uci dot edu>
- Cc: ecos-discuss at sources dot redhat dot com, akhaef at uci dot edu
- Date: Tue, 18 Dec 2001 04:09:07 +0000
- Subject: Re: [ECOS] redboot fis trouble
- References: <Pine.GSO.4.30.0112171548210.5223-100000@taurus.oac.uci.edu>
"Amin A. Khaef" wrote:
> RedBoot> fis create -f 0x50140000 -l 0x1E40000 -n "JFFS2"
> ... Unlock from 0x51fc0000-0x52000000: .
> ... Erase from 0x51fc0000-0x52000000: .
> ... Program from 0x01fbf000-0x01fff000 at 0x51fc0000: .
> ... Lock from 0x51fc0000-0x52000000: .
> RedBoot> fis list
> Name FLASH addr Mem addr Length Entry point
> RedBoot 0x50000000 0x50000000 0x00040000 0x00000000
> RedBoot[backup] 0x50040000 0x50040000 0x00040000 0x00000000
> RedBoot config 0x51F80000 0x51F80000 0x00001000 0x00000000
> FIS directory 0x51FC0000 0x51FC0000 0x00040000 0x00000000
> Linux kernel 0x50080000 0x00100000 0x000C0000 0x00000000
> JFFS2 0x50140000 0x50140000 0x01E40000 0x00000000
> RedBoot> fis free
> 0x503C0000 .. 0x51F80000
This is a little gotcha of fis free. fis free works simply by peeking into
the first 4 words of each flash block and seeing if its erased. This means
if the image *happens* to start with 0xffffffff it would show up as free.
But more relevantly it means it ignores the FIS and just looks at the
flash. This is documented in the RedBoot manual.
However it should really be fixed. You can submit a bug report at
http://sources.redhat.com/ecos/problemreport.html and/or submit a fix
yourself that will perhaps list both ideas of free flash - that which
appears free according to the FIS, and that which appears free according to
contents.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine