[U-Boot-Users] booting linux kernel problem...

[U-Boot-Users] booting linux kernel problem...

[Michael Frey]

I now have u-boot running on my custom PXA250 hardware!!!

I am now trying to boot my linux kernel and I am getting the following 
error after trying to boot using the boom command.

Error: inflate() returned -2

Anyone have any ideas why this might be.  I went through the steps of 
creating a gzipped linux image and creating a uboot image using mkimage 
than building an srecord image.

the imi command gives me the correct info and the checksum is correct.

Michael

[U-Boot-Users] booting linux kernel problem...

[Wolfgang Denk]

In message <430C2158-442C-11D7-B791-00039390D626@pepper.com> you wrote:
> I now have u-boot running on my custom PXA250 hardware!!!

Congratulations!

> Error: inflate() returned -2

What are your load / entry point addrresses, and where is  the  image
located in memory when you "bootm" it?

> Anyone have any ideas why this might be.  I went through the steps of 

Probably  the  uncompressed  code  is   overwriting   the   not   yet
uncompressed tail of the image.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
See us @ Embedded World, Nuremberg, Feb 18-20, Hall 12.0 Booth 12-442

[U-Boot-Users] booting linux kernel problem...

[Kyle Harris]

On Wednesday 19 February 2003 12:04 pm, Michael Frey wrote:

> I now have u-boot running on my custom PXA250 hardware!!!
>
> I am now trying to boot my linux kernel and I am getting the following
> error after trying to boot using the boom command.
>
> Error: inflate() returned -2
>

Can you provide the complete boot log?

Thanks, Kyle.

[U-Boot-Users] booting linux kernel problem...

[Michael Frey]

The complete log...


U-Boot 0.2.0 (Feb 19 2003 - 15:03:30)

U-Boot code: AA000000 -> AA0543E0  BSS: -> AA055994
DRAM Configuration:
Bank #0: a0000000 64 MB
Bank #1: a4000000  0 kB
Bank #2: a8000000 64 MB
Bank #3: ac000000  0 kB
Flash: 32 MB
*** Warning - bad CRC, using default environment

pepper-> imi

## Checking Image at 00300000 ...
    Image Name:   Pepper Linux
    Image Type:   ARM Linux Kernel Image (gzip compressed)
    Data Size:    635311 Bytes = 620.4 kB
    Load Address: a0008000
    Entry Point:  a0008000
    Verifying Checksum ... OK
pepper-> bootm
## Booting image at 00300000 ...
    Image Name:   Pepper Linux
    Image Type:   ARM Linux Kernel Image (gzip compressed)
    Data Size:    635311 Bytes = 620.4 kB
    Load Address: a0008000
    Entry Point:  a0008000
    Verifying Checksum ... OK
    Uncompressing Kernel Image ... Error: inflate() returned -2
GUNZIP ERROR - must RESET board to recover
reseting ...


On Wednesday, February 19, 2003, at 03:16  PM, Kyle Harris wrote:

>
> On Wednesday 19 February 2003 12:04 pm, Michael Frey wrote:
>
>> I now have u-boot running on my custom PXA250 hardware!!!
>>
>> I am now trying to boot my linux kernel and I am getting the following
>> error after trying to boot using the boom command.
>>
>> Error: inflate() returned -2
>>
>
> Can you provide the complete boot log?
>
> Thanks, Kyle.

[U-Boot-Users] booting linux kernel problem...

[Geir Thomassen]

Michael Frey wrote:
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... Error: inflate() returned -2

-2 = Z_STREAM_ERROR, meaning the data is corrupt (truncated ?).

Quick workaround:

Compress the kernel instead (make zImage). You don't gain anything
by compressing your image twice.

I saw a similar problem and traced it back to troubles with malloc()
because armboot_real_end wasn't initialized correctly. See my mail:
"Memory layout on PXA" a couple of days ago.

If you are going to use initrd (eg. bootm 0x30000 0x40000) you need
to modify the initrd loading code also (at least I had to...),
since the code doesn't load the initrd to RAM. It passes a
pointer to the image in flash to the kernel instead.

Geir

[U-Boot-Users] booting linux kernel problem...

[Kyle Harris]

On Wednesday 19 February 2003 03:27 pm, Michael Frey wrote:

> The complete log...
>
>
> U-Boot 0.2.0 (Feb 19 2003 - 15:03:30)
>
> U-Boot code: AA000000 -> AA0543E0  BSS: -> AA055994
> DRAM Configuration:
> Bank #0: a0000000 64 MB
> Bank #1: a4000000  0 kB
> Bank #2: a8000000 64 MB
> Bank #3: ac000000  0 kB
> Flash: 32 MB
> *** Warning - bad CRC, using default environment
>
> pepper-> imi
>
> ## Checking Image at 00300000 ...
>     Image Name:   Pepper Linux
>     Image Type:   ARM Linux Kernel Image (gzip compressed)
>     Data Size:    635311 Bytes = 620.4 kB
>     Load Address: a0008000
>     Entry Point:  a0008000
>     Verifying Checksum ... OK
> pepper-> bootm
> ## Booting image at 00300000 ...
>     Image Name:   Pepper Linux
>     Image Type:   ARM Linux Kernel Image (gzip compressed)
>     Data Size:    635311 Bytes = 620.4 kB
>     Load Address: a0008000
>     Entry Point:  a0008000
>     Verifying Checksum ... OK
>     Uncompressing Kernel Image ... Error: inflate() returned -2
> GUNZIP ERROR - must RESET board to recover
> reseting ...

How was you compresses image built? This is how I do it.

arm-linux-objcopy -S -O binary vmlinux linux
gzip -vf9 linux
mkimage -n $ts -A arm -O linux -T kernel -C gzip -a a0008000 -e a0008000 -d 
linux.gz linuxgz.image

Kyle.

[U-Boot-Users] booting linux kernel problem...

[Robert Schwebel]

On Wed, Feb 19, 2003 at 12:04:52PM -0500, Michael Frey wrote:
> Anyone have any ideas why this might be.  I went through the steps of 
> creating a gzipped linux image and creating a uboot image using mkimage 
> than building an srecord image.

Try my PXA patch (on our web site) for the Linux kernel - it lets you
'make uImage UBOOT=/where/u-boot/lives' to make an uImage. 

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Braunschweiger Str. 79,  31134 Hildesheim, Germany
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
    Phone: +49-5121-28619-0 |  Fax: +49-5121-28619-4