[U-Boot-Users] fsload questions

Charles Krinke ckrinke at istor.com
Thu Dec 21 23:57:44 CET 2006

-----Original Message-----
From: Stefan Roese [mailto:sr at denx.de] 
Sent: Thursday, December 21, 2006 11:18 AM
To: u-boot-users at lists.sourceforge.net
Cc: Charles Krinke; Randy Brown; Kevin Smith
Subject: Re: [U-Boot-Users] fsload questions

On Thursday 21 December 2006 19:47, Charles Krinke wrote:
> I8000E> bootm 100000
> ## Booting image at 00100000 ...
>    Image Name:   Linux-
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    936926 Bytes = 915 kB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... Error: inflate() returned -3
> GUNZIP ERROR - must RESET board to recover

Use a bigger address (e.g. 0x400000) since the uncompressing can
overwrite the 
original image.

Best regards,

Thank you Stefan, that cleared up one mystery. Given an offset of
0x1000000 instead of 0x100000, uImage can be loaded by fsload and will
now bootm to a bash prompt.

This leaves the time question. It seems that the fsload starts out

Scanning JFFS2 FS

But it takes almost 2 minutes to scan the flash before the fsload
completes and loads the uImage. So, this adds an additional 2 minutes to
the boot of the embedded system, which is clearly a problem.

The flash was formatted in Linux using the flash_eraseall utility. I am
hoping that you, or someone else, can tell me that there is some
configuration constant missing or that the flash may be formatted in a
way that is not quite consistent with U-Boot's needs.


More information about the U-Boot mailing list