[U-Boot-Users] iminfo - Bad Header Checksum

Mon May 30 12:54:13 CEST 2005

In message <429AEC4E.8040202 at commergy.com> you wrote:
>
> The situation, though now in a legal addresses range, is no more 
> pleasant. See below for details:
...
> Metrowerks=> tftpboot 200000 test.img
> Enet starting in Full Duplex
> Enet starting in 1000BT
> TFTP from server 10.82.190.3; our IP address is 10.82.190.238
> Filename 'test.img'.
> Load address: 0x200000
> Loading: *packetHandler changed.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This message is suspicious. It is not part of the standard U-Boot code.

> ## Checking Image at 00200000 ...
>    Bad Header Checksum
> Metrowerks=> md 200000
> 00200000: 27051956 32cf8de9 429679c4 000a1b8b    '..V2...B.y.....
...
> Metrowerks=> crc32 200000 40
> CRC32 for 00200000 ... 0020003f ==> 32cf8de9

This makes little sense to  me.  I  seriously  doubt  that  different
implementations  of the CRC32 code would be used in the imi and bootm
commands.

Can you please send me a copy of your test.img file? (Send it  to  me
only, not to the list.)

> --------------070409080405020000000002
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit
> 
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> <html>

And please don't post HTML here!

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Thought for the day: What if there were no hypothetical situations?