From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Uncompress error with LZO
Date: Thu, 18 Oct 2012 10:21:32 -0700 [thread overview]
Message-ID: <20121018172132.GU27770@bill-the-cat> (raw)
In-Reply-To: <507FF4F4.1080805@arcor.de>
On Thu, Oct 18, 2012 at 02:24:20PM +0200, Matthias Wei?er wrote:
> Hi
>
> I get some misterious errors from time to time when decompressing an
> LZO compressed image. The output is as follows
>
> zmx25> bootm 0x82000000
> ## Booting kernel from Legacy Image at 82000000 ...
> Image Name: zmx25-gfx ifs
> Image Type: ARM QNX Kernel Image (lzo compressed)
> Data Size: 8181868 Bytes = 7.8 MiB
> Load Address: 80000000
> Entry Point: 80000000
> Verifying Checksum ... OK
> Uncompressing Kernel Image ... LZO: uncompress or overwrite error
> -5 - must RESET board to recover
> resetting ...
>
> RAM is from 0x80000000 to 0x83ffffff. The image was transfered using
> TFTP and has an uncompressed size of about 20MB. If I change
> something in the image so that the compressed data is different it
> works. If an image is "broken" it is always broken so the behavior
> is reproducable. I compress the image under windows using:
So you're saying that changing the source image results in good, or bad,
behavior correct? Can you try taking a bad source image and using lzop
on Linux instead?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20121018/b5824da8/attachment.pgp>
next prev parent reply other threads:[~2012-10-18 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 12:24 [U-Boot] Uncompress error with LZO Matthias Weißer
2012-10-18 17:21 ` Tom Rini [this message]
2012-10-18 17:31 ` Tom Rini
2012-10-19 7:43 ` Matthias Weißer
2012-10-19 15:34 ` Tom Rini
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=20121018172132.GU27770@bill-the-cat \
--to=trini@ti.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