[U-Boot-Users] bad header checksum

Kevin Bailey kevin.bailey at ind.alcatel.com
Thu Nov 4 20:19:35 CET 2004


BTW, I got kermit downloading working and it does the same thing,
so I changed the subject to avoid confusing other readers.

On Thursday 04 November 2004 08:39 am, you wrote:
> In message <200411040809.16589.kevin.bailey at ind.alcatel.com> you wrote:
> > Metrowerks=> bootp 4000000
>
> 0x4000000 is 64 MB - how much RAM is on your board?

256MB

> > Metrowerks=> iminfo
> > ## Checking Image at 04000000 ...
> >    Bad Header Checksum
>
> Try:
>
>  md 04000000
>
> and post the rsults...

Here's the one at 0x01000000. It's the same everywhere I try it.

01000000: 27051956 3f6f2360 418155cd 0004c42d    '..V?o#`A.U....-
01000010: 00000000 00000000 27cee1e0 05070201    ........'.......
01000020: 4c696e75 782d322e 342e3235 00000000    Linux-2.4.25....
01000030: 00000000 00000000 00000000 00000000    ................
01000040: 1f8b0808 cc558141 0203766d 6c696e75    .....U.A..vmlinu
01000050: 7800e45b 0d705455 963eaf7f 42b7c1d0    x..[.pTU.>..B...

> This looks OK to me. Try a hexdump of the first 64 bytes of the image
> on your build host, and then of the loaded file in U-Boot. Compare.

They're identical.

> Maybe you have a memory corruption problem.

It runs the built-in Linux image ok. Perhaps the vendor changed
the loader or the crc algorithm ? I don't know why, I just can't
think of anything else.

Thanks,
krb




More information about the U-Boot mailing list