[U-Boot-Users] Problem uncompressing kernel image

[U-Boot-Users] Problem uncompressing kernel image

["Häpe, Sebastian, HRD/AB"]

Hi everybody!

I now have U-Boot running fine on my self designed, PPC603e-based board.
In the next step I want to try to start a Linux kernel image.
For the generation of it, I use the ELinOS embedded Linux distribution.
This creates me the kernel image (v2.4) + the initial ram disk. For
debugging I use the
BDI-2000 JTAG debugger.

First, I start U-Boot from flash memory, located at 0xff800000. 
After it runs, I load the kernel multi-image to RAM, which is located from
0x00000000 to 0x007fefff, at address 0x00600000.
Using the 'imi 0x00600000'-command, i get the output:

=> imi 0x00600000

## Checking Image at 00600000 ...
   Image Name:    Multi-File Image
   Created:       2005-02-24 14:27:59 UTC
   Image Type:    PowerPC Linux Multi-File Image (gzip compressed)
   Data Size:     1237870 Bytes = 1.2MB
   Load Address:  00010000
   Entry Point:   00010000
   Contents:
   Image 0:   333090 Bytes = 325.3 kB
   Image 1:   904766 Bytes = 883.6 kB
   Verifying Checksum ... OK

=>
   
Then I try to start the image:

=> bootm 0x00600000

## Booting image at 00600000
   [ same as command before ]
   
   Umcompressing Multi-File Image ... inflateInit2() returned -4
   GUNZIP ERROR - must RESET board to recover


What could be the problem?
I calculated the sizes and i am _nearly_ sure, that nothing is overwritten.

Hopefully,
Sebastian H?pe

[U-Boot-Users] Problem uncompressing kernel image

[Wolfgang Denk]

In message <2D9AB865A49FD511914700105A0EF67901C6F271@morse.smart.lfk.eads.net> you wrote:
> 
> I now have U-Boot running fine on my self designed, PPC603e-based
> board.

Congrats.

> First, I start U-Boot from flash memory, located at 0xff800000. 
> After it runs, I load the kernel multi-image to RAM, which is located
> from
> 0x00000000 to 0x007fefff, at address 0x00600000.

Do you really have less than 8 MB of RAM? You will have  hard  times
of getting Linux to run...

> Using the 'imi 0x00600000'-command, i get the output:
> 
> => imi 0x00600000

0x00600000 = 6 MB... Try a higher load  address  (assuming  you  have
enough RAM).

> What could be the problem?
> I calculated the sizes and i am _nearly_ sure, that nothing is
> overwritten.

I'm not. Get more RAM.

Best regards,

Wolfgang Denk

-- 
See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
You got to learn three things. What's  real,  what's  not  real,  and
what's the difference."           - Terry Pratchett, _Witches Abroad_

[U-Boot-Users] Problem uncompressing kernel image

[Cory Tusar]

Wolfgang Denk wrote:
>>First, I start U-Boot from flash memory, located at 0xff800000. 
>>After it runs, I load the kernel multi-image to RAM, which is located
>>from
>>0x00000000 to 0x007fefff, at address 0x00600000.
> 
> 
> Do you really have less than 8 MB of RAM? You will have  hard  times
> of getting Linux to run...

Bollocks.

A 2.4 kernel + RAM disk will run nicely in 4 MB of RAM, you can cut that 
to 2 MB if you go the XIP route.  It's no "harder" than setting it up on 
a board with >= 8 MB, other than the fact that you need to be judicious 
about what's included in your kernel and image.

>>Using the 'imi 0x00600000'-command, i get the output:
>>
>>=> imi 0x00600000
> 
> 
> 0x00600000 = 6 MB... Try a higher load  address  (assuming  you  have
> enough RAM).

Not much higher he can go.  Assuming the exact same image, a base of 
0x006D0000 would put the end of the image at 0x007FE36E, just barely 
within limits.

>>What could be the problem?
>>I calculated the sizes and i am _nearly_ sure, that nothing is
>>overwritten.
> 
> 
> I'm not. Get more RAM.

How large is your uncompressed RAM disk image?  Trying to uncompress a 
16 MB image into 8 MB of RAM is a BadThing(tm)...

-Cory


-- 
Cory T. Tusar
Embedded Systems Engineer
Videon Central, Inc.
2171 Sandy Drive
State College, PA 16801
(814) 235-1111 x316
(814) 235-1118 fax

"Debugging is twice as hard as writing the code in the first place.
   Therefore, if you write the code as cleverly as possible, you are,
     by definition, not smart enough to debug it."  --Brian W. Kernighan