[U-Boot-Users] Booting Linux stops at Starting Kernel, perhaps an endian problem

[Wolfgang Denk]

In message <BAY15-DAV62qyFp4gpr000115c9 at hotmail.com> you wrote:
> 
> The kernel and file system image (u-boot multi image) is loaded into RAM
> with kermit at 0xa3100000. But, when we try to boot linux with the bootm
> command, it stops at "Starting Kernel" (We're working with Linux kernel
> 2.4.19 patched with -rmk7-pxa1 in eLinOS distribution). 
> 
> In order to see if something went wrong, we've compared vmlinux.bin
> before compression and the kernel decompressed in RAM, in position
> Load_address. We've found that the information is the same but one is in
> big endian (in RAM) and the other one in little endian (vmlinux.bin).
> The platform works in little endian, so this is probably the problem.
> How can we solve it?? Is it a gunzip problem?? 

I cannot see how gunzip could perform a byte swapping.

Kermit binary protocol is byte oriented, so it definitely does not do
any byte swapping either.


How did you compare the images?

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
Research is what I'm doing when I don't know what I'm doing.
                                                 -- Wernher von Braun