[U-Boot] Problem booting Linux

[U-Boot] Problem booting Linux

[Remco Poelstra]

Hi all,

I'm trying to get Linux booting on an ARM7 (NXP LPC2468). I copy the 
uImage to 0xa1500000 and the romfs.bin to 0xa1800000. I set bootargs to: 
root=/dev/ram initrd=0xa1800000,4000k console=/dev/ttyS0,115200N8
When I do 'bootm a1500000', it finds the image and tries to uncompress 
it, but it goes silent after printing    "Uncompressing Kernel Image ..."
When I try to create the uImage with
'mkimage -A arm -O linux -T kernel -a 0 -e 0 -n "Linux Kernel Image" -d 
linux.bin uImage', I get the following output (mind the absent -C flag):
-----------
Image Name:   Linux Kernel Image
Created:      Thu Mar 12 15:37:01 2009
Image Type:   ARM Linux Kernel Image (gzip compressed)
Data Size:    1986268 Bytes = 1939.71 kB = 1.89 MB
Load Address: 0x00000000
Entry Point:  0x00000000
---------
bootm also still thinks that the image is compressed and bootm prints: 
Uncompressing Kernel Image ... Error: Bad gzipped data
GUNZIP: uncompress or overwrite error - must RESET board to recover

How can I make sure that the Linux image can boot?

Kind regards,

Remco Poelstra

[U-Boot] Problem booting Linux

[Remco Poelstra]

Remco Poelstra schreef:
> Hi all,
> 
> I'm trying to get Linux booting on an ARM7 (NXP LPC2468). I copy the 
> uImage to 0xa1500000 and the romfs.bin to 0xa1800000. I set bootargs to: 
> root=/dev/ram initrd=0xa1800000,4000k console=/dev/ttyS0,115200N8
> When I do 'bootm a1500000', it finds the image and tries to uncompress 
> it, but it goes silent after printing    "Uncompressing Kernel Image ..."
> When I try to create the uImage with
> 'mkimage -A arm -O linux -T kernel -a 0 -e 0 -n "Linux Kernel Image" -d 
> linux.bin uImage', I get the following output (mind the absent -C flag):
> -----------
> Image Name:   Linux Kernel Image
> Created:      Thu Mar 12 15:37:01 2009
> Image Type:   ARM Linux Kernel Image (gzip compressed)
> Data Size:    1986268 Bytes = 1939.71 kB = 1.89 MB
> Load Address: 0x00000000
> Entry Point:  0x00000000
> ---------
> bootm also still thinks that the image is compressed and bootm prints: 
> Uncompressing Kernel Image ... Error: Bad gzipped data
> GUNZIP: uncompress or overwrite error - must RESET board to recover
> 
> How can I make sure that the Linux image can boot?

I just noticed that when I set the load and entry address to 0xa0000000 
(the start address of my external RAM), then bootm prints "starting 
kernel" and then U-boot resets itself twice....
I think I have no idea what's going on here. Is this a problem in my 
U-boot or is it already in the kernel?

Kind regards,

Remco Poelstra

[U-Boot] Problem booting Linux

[Wolfgang Denk]

Dear Remco Poelstra,

In message <49B9224C.6090302@duran-audio.com> you wrote:
> 
> linux.bin uImage', I get the following output (mind the absent -C flag):
> -----------
> Image Name:   Linux Kernel Image
> Created:      Thu Mar 12 15:37:01 2009
> Image Type:   ARM Linux Kernel Image (gzip compressed)
> Data Size:    1986268 Bytes = 1939.71 kB = 1.89 MB
> Load Address: 0x00000000
----------------^^^^^^^^^^
> Entry Point:  0x00000000
----------------^^^^^^^^^^

Are you sure these are correct? 0x0000 is usually a ROM address on
ARM; I don't think you can load and run your kernel image there.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The flow chart is a most thoroughly oversold piece of  program  docu-
mentation.              -- Frederick Brooks, "The Mythical Man Month"

[U-Boot] Problem booting Linux

[Wolfgang Denk]

Dear Remco Poelstra,

In message <49B9262F.9080802@duran-audio.com> you wrote:
>
> I just noticed that when I set the load and entry address to 0xa0000000 
> (the start address of my external RAM), then bootm prints "starting 
> kernel" and then U-boot resets itself twice....
> I think I have no idea what's going on here. Is this a problem in my 
> U-boot or is it already in the kernel?

After printing "starting the kernel", U-Boot is gone, and the kernel
(resp. the ARM bootstrap wrapper) is running. This is a kernel
problem, resp. a configuration issue.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
I have a theory that it's impossible to prove anything, but  I  can't
prove it.