topic Re: Uncompressing Kernel Image ... in PowerQUICC Processors

Uncompressing Kernel Image ...

Freshman — Fri, 29 Mar 2013 10:35:25 GMT

hello

I have compiled the uboot and linux kernel with LTIB ，than transplate the uboot and kernel (uImage) to the board（MPC8313ERDB）. The uboot goes well ，print as follows：

U-Boot 1.3.0 (Mar 26 2013 - 18:11:12) MPC83XX

Reset Status:

CPU: e300c3, MPC8313E, Rev: 21 at 333.333 MHz, CSB: 166 MHz

Board: Freescale MPC8313ERDB

I2C: ready

DRAM: 128 MB

FLASH: 8 MB

NAND:

In: serial

Out: serial

Err: serial

Net: TSEC0, TSEC1 [PRIME]

than after transplant the uImage , reset and boot the board

=>bootm fe100000 fe300000 fe700000

print as follows:

## Booting image at fe100000 ...

Image Name: Linux-2.6.23

Created: 2013-03-29 3:22:25 UTC

Image Type: PowerPC Linux Kernel Image (gzip compressed)

Data Size: 1619970 Bytes = 1.5 MB

Load Address: 00000000

Entry Point: 00000000

Verifying Checksum ... OK

Uncompressing Kernel Image ...

It stops ! There must be something wrong , but why ？help me !

ps：Old uInage is OK for the boot !

Asky

Re: Uncompressing Kernel Image ...

Freshman — Sun, 07 Apr 2013 01:38:43 GMT

The reason is that the uImage is too big .

Re: Uncompressing Kernel Image ...

ivanmercier — Wed, 17 Jul 2013 16:22:06 GMT

I've got the same problem...

so ,you 've just clean out your kernel config?

I got this message at the end of compiling the kernel

INFO: Uncompressed kernel (size 0x9f2000) overlaps the address of the wrapper(0x400000)
INFO: Fixing the link_address of wrapper to (0xa00000)

How can I increase the possible size?

thanks

Re: Uncompressing Kernel Image ...

Freshman — Mon, 12 Aug 2013 09:26:27 GMT

I just decrease the unused modles in the kernel ,you can try to delete some in the makefile.

and I'm sorry for that I don't know how to increase the maxsize allowed .

good luck with you.

Re: Uncompressing Kernel Image ...

scottwood — Mon, 12 Aug 2013 19:04:08 GMT

Those messages are not relevant unless you're using the bootwrapper (e.g. cuImage), which you're not. Even then, the message just indicates that the addresses have been updated to compensate.

I think you may be seeing an old U-Boot bug involving speculative accesses to a mapping that should be marked guarded but isn't. U-Boot 1.3.0 is very old. Please use a current upstream version.