From: Kyle Harris <kharris@nexus-tech.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] booting linux kernel problem...
Date: Wed, 19 Feb 2003 18:22:01 -0500 [thread overview]
Message-ID: <E18lden-0001Cx-00@granger.mail.mindspring.net> (raw)
In-Reply-To: <830C870A-4448-11D7-B791-00039390D626@pepper.com>
On Wednesday 19 February 2003 03:27 pm, Michael Frey wrote:
> The complete log...
>
>
> U-Boot 0.2.0 (Feb 19 2003 - 15:03:30)
>
> U-Boot code: AA000000 -> AA0543E0 BSS: -> AA055994
> DRAM Configuration:
> Bank #0: a0000000 64 MB
> Bank #1: a4000000 0 kB
> Bank #2: a8000000 64 MB
> Bank #3: ac000000 0 kB
> Flash: 32 MB
> *** Warning - bad CRC, using default environment
>
> pepper-> imi
>
> ## Checking Image at 00300000 ...
> Image Name: Pepper Linux
> Image Type: ARM Linux Kernel Image (gzip compressed)
> Data Size: 635311 Bytes = 620.4 kB
> Load Address: a0008000
> Entry Point: a0008000
> Verifying Checksum ... OK
> pepper-> bootm
> ## Booting image at 00300000 ...
> Image Name: Pepper Linux
> Image Type: ARM Linux Kernel Image (gzip compressed)
> Data Size: 635311 Bytes = 620.4 kB
> Load Address: a0008000
> Entry Point: a0008000
> Verifying Checksum ... OK
> Uncompressing Kernel Image ... Error: inflate() returned -2
> GUNZIP ERROR - must RESET board to recover
> reseting ...
How was you compresses image built? This is how I do it.
arm-linux-objcopy -S -O binary vmlinux linux
gzip -vf9 linux
mkimage -n $ts -A arm -O linux -T kernel -C gzip -a a0008000 -e a0008000 -d
linux.gz linuxgz.image
Kyle.
next prev parent reply other threads:[~2003-02-19 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 17:04 [U-Boot-Users] booting linux kernel problem Michael Frey
2003-02-19 20:14 ` Wolfgang Denk
2003-02-19 20:16 ` Kyle Harris
2003-02-19 20:27 ` Michael Frey
2003-02-19 22:52 ` Geir Thomassen
2003-02-19 23:22 ` Kyle Harris [this message]
2003-02-21 20:31 ` Robert Schwebel
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=E18lden-0001Cx-00@granger.mail.mindspring.net \
--to=kharris@nexus-tech.net \
--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