From: Amit Shah <shahamit@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Uncompressing uImage: inflate() returned -3
Date: Mon, 23 Aug 2004 20:09:55 +0530 [thread overview]
Message-ID: <877aabc4040823073962e725a8@mail.gmail.com> (raw)
Hi,
I now have u-boot working properly on my single PPC750GX on MV64360;
it turned out to be SDRAM init issues, which were sorted out by some
trial and error.
Okay, so now there are issues when it's loading uImage: The uImage
built fails on the CRC. This is due to inconsistencies in the byte
order of vmlinux.gz. When built on i386, it is CRC'ed in little
endian, while when it's being checked on the board, it gets CRC'ed in
big endian... so there will definitely be a mismatch in the two CRCs.
Or I'm overlooking something.
So while generating the vmlinux.gz, I byteswapped it.. before feeding
it to mkimage. So the CRCs are matched, and gunzip on the board tries
to gunzip the image... However, it complains about 'bad gzipped data'.
Hmm, so setting 'verify' to 'n' also doesn't work; gunzip says
'inflate returned -3'.. which is some Z_DATA_ERROR.
I'm obviously doing something wrong here, since this should've worked...
I'm right now using an uncompressed image and working with it, that's
working fine, except the kernel's bombing out after some
initializations...
Amit.
--
Amit Shah
http://amitshah.nav.to/
next reply other threads:[~2004-08-23 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 14:39 Amit Shah [this message]
2004-08-23 17:14 ` [U-Boot-Users] Uncompressing uImage: inflate() returned -3 Wolfgang Denk
2004-08-23 17:40 ` Amit Shah
-- strict thread matches above, loose matches on Subject: below --
2004-08-23 15:07 Michael Bendzick
2004-08-23 16:20 ` Amit Shah
2004-08-23 17:24 ` Wolfgang Denk
2004-08-23 17:48 ` Amit Shah
2004-08-23 18:10 ` Wolfgang Denk
2004-08-23 18:49 ` Amit Shah
2004-08-23 22:33 ` Wolfgang Denk
2004-08-23 19:46 ` Amit Shah
2004-08-23 17:16 ` Wolfgang Denk
2004-08-23 18:54 RUSSELL PETERSON
2004-08-23 19:06 ` Amit Shah
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=877aabc4040823073962e725a8@mail.gmail.com \
--to=shahamit@gmail.com \
--cc=u-boot@lists.denx.de \
/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