[U-Boot] Debugging why my kernel won't start

Albert ARIBAUD
2010-08-17T15:38:18Z

Le 17/08/2010 13:42, Rogan Dawes a ?crit :
> On 2010/08/17 1:19 PM, Rogan Dawes wrote:
>> I'll try with a higher value, and see what happens.
>>
>
> So, I tried with TEXT_BASE=f10000, and I got a bit further:
>
> DNS323B1> bootm FF820000
> ## Booting kernel from Legacy Image at ff820000 ...
> Image Name: Linux-2.6.12.6-arm1
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 1490204 Bytes = 1.4 MiB
> Load Address: 00008000
> Entry Point: 00008000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
> OK
> Using machid 0x526 from environment
>
> Starting kernel ...
>
> Uncompressing
> Linux...................................................................................................
> done, booting the kernel.
>
> So, that does appear to have been (at least part of) the problem.

Ok, so u-boot is now out of the way of the linux image load area.

> Now to figure out why I'm not getting any further than this. (And why
> the vendor ramdisk is giving me CRC errors).

What is the actual command you use for booting your kernel? IIUC (and if
I trust the few experiments I did on edminiv2 with ramdisks) you need to
pass the ramdisk address to the bootm command, e.g. bootm ff820000
ff8xxxxx (where xxxxx is your ramdisk's location in flash (I'm assuming
your ramdisk image is in flash as your kernel image is). You did an
'iminfo' on both images to verify their integrity, didn't you?

Amicalement,
--
Albert.