From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
Date: Mon, 21 Apr 2008 15:09:43 +0200
Subject: [U-Boot-Users] intended behavior of bootm
Message-ID: <200804211509.43558.matthias.fuchs@esd-electronics.com>
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

Hi,

I am wondering if bootm behaves correctly on CRC errors in kernel and/or ramdisk images.
This is what I observed:

1) I loaded a Linux kernel into RAM at 0x200000 on a 405 system. I loaded an initial ramdisk images
into RAM at address 0x300000. Now 'bootm 200000 300000' boots my system correctly.

2) Same loading as above. But I made the kernel image CRC check fail (mw 220000 12345678).
I get:
...
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
=>

That's ok.

3) Same loading as above. But I make the ramdisk CRC check fail (mw 320000 12345678).
I get:
## Booting kernel from Legacy Image at 00200000 ...
...
## Loading init Ramdisk from Legacy Image at 00300000 ...
...
   Verifying Checksum ... Bad Data CRC
<system reset>
U-Boot 1.3.2-00450-g77dd47f (Apr 21 2008 - 14:43:23)

Hmm, I expected the same behavior as for a corrupted kernel image.
So what should be the correct behavior? I would like to get back to the prompt
on any CRC error. So is this a bug?

Matthias