Approved: Fortect
Hi everyone,
I started using U-Boot about 3 days ago, so I apologize in advance if I’ve
missed something obvious in the documentation.
I’m using a Metrowerks MPC8540 test board preloaded with
U-Boot 1.0.1 (eval-20040206-0-pre4). I suspect this may be part of the problem i.e. H. It’s just that I flashed an older version of U-Boot for the firmware. I
currently don’t have the ability to flash the card to its current state,
so I’ve always been reluctant to update U-Boot.
I have downloaded ELDK 3.1.1 and a built-in kernel using make uImage. I then downloaded a specific TFTP uImage via the card. Running Iminfo results in
“Bad Header Checksum”. I used mkimage -l to check if
is a valid title and if it’s complete.
Besides, since I was able to download and run the “Hello World” sample program, I know that my TFTP generator is not a problem either.
I would appreciate any hints as to where the . mr. goes wrong.
A message from Dale by Dunlea
I’m using a Metrowerks MPC8540 test board, which unfortunately
pre-installed U-Boot 1.0.1 (eval-20040206-0-pre4). Guess who it could be?
Part of moher problems.e. that I wrote an old version of Flash for U-Boot. At the moment I have no way to return the block
to its current state, so I’m hesitant to update U-Boot
for the time being.
I did some more digging and found this:
When I loaded the CRC block onto my screen and ran the crc32
command, it generated the same CRC that was already running, which means
it’s correct. I ended up copying the linux image, which is not being used by
Flash, into RAM and running iminfo. The photo has disappeared. I then reset the
CRC lock on this image and ran the crc32 command. The generated CRC
was the result of something other than what actually existed.
How are the U-boot environment variables set up?
Environment variables can be configured in a file requested by the card, for example package / uboot-ar71xx / files / include / configs / nbg460n.h for Zyxel NBG 460N / 550N / 550NH. The storage location is completely predefined in the flash partition: that is, it is copied to RAM during U-Boot deployment. The U-Boot environment is protected by a CRC32 checksum.
It seems to me that Metrowerks has introduced a modified version of
U-Boot that uses a different checksum function when checking the
header. If so, they are probably subject to the terms of the GPL,
should they if they want to release their changes? However, I wasn’t quite ready to find it
to make an impact.
Has anyone else used this chart? Further research, including archives, led
to this topic:
This seems to be exactly the problem I had this morning. Unfortunately
this thread seems to have ended for a solution.
Thanks again to everyone who can shed some light on the situation.
Approved: Fortect
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
Message to Dale Dunlea
I believe Metrowerks has installed a modified copy of
U-Boot that uses a different checksum function to check
the header. If so, then probably under the terms of the GPL,
Instead of speculating, provide relatively
more detailed information, much like the EXACT commands you used on your card,
to load the image and let them check its consistency. Most people
for example, have they tried dragging the image header part onto “md”? And maybe also try a hex dump of the photo on your host system?
—
Software development: embedded and real-time systems, embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 E- mail :wd from denx.de
It is better to marry than to burn yourself.
– Bible “I. K Rynthians ” ca. 7, volt. 9
Dear Dale,
Sorry if I wasn’t clear before. I uploaded my photo via TFTP In (as mentioned in my first post), then via Kermit and Srecord.
The results were the same in each case.
Please don’t describe exactly what you did, instead be sure to post
the EXACT commands you used.
During the verification of the downloaded visions, as mentioned, I checked
the checksum of the checksums and additional elements of the magic number of the downloaded fingerprint using MD,
Order on both the main course and the target board. Considering parameters
there is a certain inconsistency in the situation where the CRC fails the CRC
test by the crc32 instruction generated when installing U-Boot