When I call the zImage directly I see then of course with the DEBUG: => go 0x8000 ## Starting application at 0x00008000 ...
Error: unrecognized/unsupported machine ID (r1 = 0x02fddea8).
Available machine support:
ID (hex) NAME 000000f5 Intel IXDP425 Development Platform
Please check your kernel config and/or bootloader.
But wrapping the arch/arm/boot/Image with mkimage it just resets the board then:
=> bootm 0x800000 ## Booting kernel from Legacy Image at 00800000 ... Image Name: linux-2.6 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1783464 Bytes = 1.7 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK resetting ...
although bdinfo shows the same machine ID:
=> bdinfo arch_number = 0x000000F5
thanks horst
2008/11/23 Jean-Christophe PLAGNIOL-VILLARD plagnioj@jcrosoft.com
On 21:15 Sun 23 Nov , Horst Rennfler wrote:
Good evening... I have an IXP425 based platform which currently has redboot installed and want to replace it with u-boot of course :-)
I can start latest u-boot from git inside redboot, display flash information, doing memory test, tftp images onto it without problems...
What bugs me is the fact that I am not able to boot any arm-linux zImage inside u-boot but redboot can...
normally with u-boot we use a uImage not a zImage directly
Trying to boot from within u-boot it just hangs after the call to "decompress_kernel" from arch/arm/compressed/head.S"...
active the low-level kernel debug
and check that in u-boot you pass the good machine ID to the kernel
Best Regards, J.