From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Error uncompressing kernel image
Date: Fri, 20 Feb 2009 11:01:28 -0500 [thread overview]
Message-ID: <499ED3D8.6020809@ge.com> (raw)
In-Reply-To: <d970ff420902200749yb27554fj526701529277723a@mail.gmail.com>
Alemao wrote:
> Hi all,
>
> I have two JFFS2 images, both with the _same_ kernel inside.
>
> But the images differs in size, cause one is for debugging and has
> some additional apps:
>
> debug.im = 13 MB
> release.im = 6.2 MB
>
>
> Im loading kernel and dtb via fsload:
>
> fsload 2000000 uImage
> fsload 4000000 mpc8343.dtb
> bootm 2000000 - 4000000
Your uImage is located pretty high in memory: 0x02000000. A lot of
boards load the image at 0x00400000. I would move this down and see if
it helps.
Your DTB is loaded way away from your image. I would load it 32K below
(lower address) your uImage. It probably is only around 8K, 32K will
give you plenty of room to grow (famous last words ;-). Try 0x003F8000.
Combining the lower addresses should give bigger available chunks of RAM
on startup.
> When I use release.im, no problems. But when I use debug.im:
>
> Verifying Checksum ... OK
> Uncompressing Kernel Image ... Error: inflateInit2() returned -4
> GUNZIP ERROR - must RESET board to recover
> Resetting the board.
>
> In u-boot/include/zlib.h:232:
>
> #define Z_MEM_ERROR (-4)
Out of memory - probably due to fragmentation (see above) because of
where you are loading your image and dtb.
[snip]
>
> Any ideas why this is happening?
>
> Maybe scanning JFFS2 is consuming a lot of memory?
Quite likely.
> My board has 128 MB of DDR SDRAM, I think space is not a problem, so
> is there a place that I can set for exemple max values for
> allocations?
>
> Im using U-boot-1.2.0.
Very old.
> Cheers,
>
> --
> Alemao
Best regards,
gvb
next prev parent reply other threads:[~2009-02-20 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 15:49 [U-Boot] Error uncompressing kernel image Alemao
2009-02-20 16:01 ` Jerry Van Baren [this message]
2009-02-23 7:18 ` Michael Lawnick
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=499ED3D8.6020809@ge.com \
--to=gerald.vanbaren@ge.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 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.