[ECOS] [Fwd: How to enable redboots CRC checking]

[Jonathan Larmour <jifl@eCosCentric.com>]

[-- Attachment #1: Type: text/plain, Size: 179 bytes --]

This was misaddressed...
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

[-- Attachment #2: How to enable redboots CRC checking --]
[-- Type: message/rfc822, Size: 3385 bytes --]

From: Winkler Andreas <andreas.aw.winkler@siemens.com>
To: "'ecos-discuss-owner@ecos.sourceware.org'" <ecos-discuss-owner@ecos.sourceware.org>
Subject: How to enable redboots CRC checking
Date: Wed, 5 May 2004 09:28:40 +0200
Message-ID: <BCB494E8B7BF2D40B56D1164C67BC2A801B16872@kher443a.ww004.siemens.net>

Hi,

some weeks ago I asked about the CRC checking of redboot. From Thomas Gary i
got the following answer:

"When images are written to the FIS, a CRC will be calculated and saved with
the image. When you read the image into RAM ("fis load"), the CRC is
verified and if it fails, then the entry point address is suppressed. This
is normally used to prevent the "go" command from executing."

Now I made a test. for the CRC checking.
With Redboot I wrote a Linux kernel to flash (fis create). I could load that
kernel to RAM and start it.
With Linux I wrote something into that flash image.
Then I booted Redboot. Again I loaded the kernel image to RAM and could
start it without any fault message.
Of course the kernel was not runnable and crashed.

I had expected a fault message when trying to run the corrumpted kernel
image.
What could be the reason that it doesn't work?

Regards
Andreas


[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss