Uncompressing Kernel Image ...

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Uncompressing Kernel Image ...

Jump to solution
3,063 Views
Freshman
Contributor III

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


Tags (1)
0 Kudos
1 Solution
1,770 Views
Freshman
Contributor III

The reason is that the uImage is too big .

View solution in original post

0 Kudos
4 Replies
1,771 Views
Freshman
Contributor III

The reason is that the uImage is too big .

0 Kudos
1,770 Views
ivanmercier
Contributor I

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

0 Kudos
1,770 Views
scottwood
NXP Employee
NXP Employee

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.

0 Kudos
1,770 Views
Freshman
Contributor III

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.

0 Kudos