public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dale Dunlea <daledunlea@commergy.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] iminfo - Bad Header Checksum
Date: Sun, 29 May 2005 02:47:39 +0100	[thread overview]
Message-ID: <42991F3B.5000104@commergy.com> (raw)

Hi All,

I started using U-Boot about 3 days ago, so apologies in advance if I 
have missed something obvious in the documentation.

I'm using a Metrowerks MPC8540 test board, which came pre-installed with 
U-Boot 1.0.1(eval-20040206-0-pre4). I suspect that this may be part of 
the problem i.e. that I have an old version of U-Boot burned to flash. I 
do not currently have the means to re-flash the board back to its 
current state, and so I am reluctant to try and upgrade U-Boot just yet.

I downloaded ELDK 3.1.1 and built the kernel, using make uImage. I then 
downloaded the uImage via TFTP to the board. Running iminfo results in 
"Bad Header Checksum". I ran mkimage -l to verify that there was a valid 
header in place, and there does seem to be.

Also, I know that there is no problem with my TFTP setup as I have been 
able to download and execute the "Hello World" example program.

I would appreciate any pointers on where I am going wrong.

Thanks in advance,
Dale Dunlea

             reply	other threads:[~2005-05-29  1:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-29  1:47 Dale Dunlea [this message]
2005-05-29 21:25 ` [U-Boot-Users] iminfo - Bad Header Checksum Dale Dunlea
2005-05-29 21:32   ` Wolfgang Denk
2005-05-29 23:25     ` [U-Boot-Users] ARC A4 richard at uclinux.net
     [not found] <429A6A6C.10106@commergy.com>
2005-05-30  8:04 ` [U-Boot-Users] iminfo - Bad Header Checksum Wolfgang Denk
2005-05-30 10:20   ` Dale Dunlea
2005-05-30 10:27     ` Wolfgang Denk
2005-05-30 10:34       ` Dale Dunlea
2005-05-30 10:54         ` Wolfgang Denk
2005-05-30 11:32         ` Wolfgang Denk
2005-05-30 11:38           ` Dale Dunlea

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42991F3B.5000104@commergy.com \
    --to=daledunlea@commergy.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox