From: "Matthias Weißer" <weisserm@arcor.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Uncompress error with LZO
Date: Thu, 18 Oct 2012 14:24:20 +0200 [thread overview]
Message-ID: <507FF4F4.1080805@arcor.de> (raw)
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:
> lzop.exe -f -9 zmx25-gfx-codesys.ifs
> lzop.exe -V
Lempel-Ziv-Oberhumer Packer
Copyright (C) 1996 - 2010
lzop v1.03 Markus Franz Xaver Johannes Oberhumer Nov
1st 2010
lzop version: v1.03, Nov 1st 2010
lzop build date: Nov 1 2010 12:45:58
The image is then created with
> mkimage.exe -A ARM -O QNX -T kernel -C lzo -n "zmx25-gfx-codesys
ifs" -a 0x80000000 -e 0x80000000 -d zmx25-gfx-codesys.ifs.lzo
zmx25-gfx-codesys.lzo.img
Is someone out there who have observed similar behavior? Am I doing
something wrong?
Regards
Matthias
next reply other threads:[~2012-10-18 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 12:24 Matthias Weißer [this message]
2012-10-18 17:21 ` [U-Boot] Uncompress error with LZO Tom Rini
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=507FF4F4.1080805@arcor.de \
--to=weisserm@arcor.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.