From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tolunay Orkun <betatester@orkun.us>
Date: Fri, 28 Apr 2006 10:53:01 -0500
Subject: [U-Boot-Users] Accessing mkimage checksum
In-Reply-To: <20060428034515.7523.qmail@web15904.mail.cnb.yahoo.com>
References: <20060428034515.7523.qmail@web15904.mail.cnb.yahoo.com>
Message-ID: <44523A5D.1040201@orkun.us>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Sam Song wrote:
> NZG <ngustavson@emacinc.com> wrote:
>> Sounds good, it just isn't obvious to me since
>> mkimage -l was verifying the 
>> checksum, since it doesn't display an checksum
>> information.
>> Now that you've said it, I see it in the README.
> 
> I also haven't seen mkimage -l displaying checksum
> info. Is mkimage I used out of date?
> 
> # tools/mkimage -l /tftpboot/uImage
> Image Name:   Linux-2.4.23
> Created:      Tue Dec 20 16:58:58 2005
> Image Type:   PowerPC Linux Kernel Image (gzip
> compressed)
> Data Size:    1442558 Bytes = 1408.75 kB = 1.38 MB
> Load Address: 0x00000000
> Entry Point:  0x00000000
> #
> 
> Thanks in advance,
> 
> Sam
> 

It does not print crc. Inspecting code quickly, it only displays crc
**Warning** if there is mismatch but proceeds after that as if nothing
has happened. So, it was not suitable for the task anyhow.

I think -v option can be added to verify the integrity of archive and
return 0 [OK] or an shell error code so it could be used in a shell
script properly.

Best regards,
Tolunay