From: Andrew Lunn <andrew@lunn.ch>
To: Winkler Andreas <andreas.aw.winkler@siemens.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] [Fwd: How to enable redboots CRC checking]
Date: Wed, 26 May 2004 12:51:00 -0000 [thread overview]
Message-ID: <20040526122821.GN32174@lunn.ch> (raw)
In-Reply-To: <BCB494E8B7BF2D40B56D1164C67BC2A801B168AF@kher443a.ww004.siemens.net>
> Hi,
>
> I just built a new redboot for my IXDP425 evaluation board from Intel
> with an ecos snapshot from 19. May 2004.
> (Is it OK, that i get a lot of warnings, e. g. signed/unsigned mismatch
> while building?)
> The CRC check doesn't work yet.
Are you sure the CRC check does not work? Look at the actual error message
> RedBoot> fi loa kernel
> RedBoot> e
> Using base address 0x01008000 and length 0x000ba7c8
> Uncompressing Linux...........
>
> invalid compressed format (err=2)
I think this is an error from the compression library, not the CRC
checking code. What format did you compress the image with? Do you
have the correct endianness etc...
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2004-05-26 12:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 12:29 Winkler Andreas
2004-05-26 12:51 ` Andrew Lunn [this message]
2004-05-26 12:52 ` Gary Thomas
2004-05-26 13:00 ` Mark Salter
2004-05-26 13:03 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2004-05-26 15:48 Winkler Andreas
2004-05-26 13:20 Winkler Andreas
2004-05-26 13:28 ` Gary Thomas
2004-05-26 13:16 Winkler Andreas
2004-05-26 12:55 Winkler Andreas
2004-05-26 13:16 ` Gary Thomas
2004-05-19 12:15 Winkler Andreas
2004-05-19 10:36 Winkler Andreas
2004-05-19 10:46 ` Gary Thomas
2004-05-05 10:13 Jonathan Larmour
2004-05-05 10:52 ` Gary Thomas
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=20040526122821.GN32174@lunn.ch \
--to=andrew@lunn.ch \
--cc=andreas.aw.winkler@siemens.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).