Kernel Image - Uncompression error

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

Kernel Image - Uncompression error

Jump to solution
2,656 Views
sunder
Contributor I

Hi,

The following highlighted error message appeared, while loading bin, rootfs and dtb.

It shows Error: inflate() returned -5, during uncompressing Kernel image. 


what is the solution ? 


Best Regards,

Sunder



transferred = 3121682 (2fa212 hex)

=> tftp c00000 p1020wlan.dtb

Speed: 100, full duplex

Using eTSEC1 device

TFTP from server 192.168.1.5; our IP address is 192.168.1.1

Filename 'p1020wlan.dtb'.

Load address: 0xc00000

Loading: #

done

Bytes transferred = 12288 (3000 hex)

=> bootm 2000000 3000000 c00000

WARNING: adjusting available memory to 30000000

## Booting kernel from Legacy Image at 02000000 ...

   Image Name:   Linux-3.12.19-rt30-QorIQ-SDK-V1.

   Created:      2015-02-11   6:34:28 UTC

   Image Type:   PowerPC Linux Kernel Image (gzip compressed)

   Data Size:    4212480 Bytes =  4 MB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

## Loading init Ramdisk from Legacy Image at 03000000 ...

   Image Name:   fsl-image-minimal-p1020rdb-20150

   Created:      2015-02-16  15:10:27 UTC

   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)

   Data Size:    3121618 Bytes =  3 MB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 00c00000

   Booting using the fdt blob at 0xc00000

   Uncompressing Kernel Image ... Error: inflate() returned -5

GUNZIP: uncompress, out-of-mem or overwrite error - must RESET board to recover

U-Boot 2009.11 (Jun 21 2011 - 16:07:27)

CPU0:  P1020E, Version: 1.1, (0x80ec0011)

Core:  E500, Version: 5.1, (0x80212051)

Clock Configuration:

       CPU0:800  MHz, CPU1:800  MHz,

       CCB:400  MHz,

       DDR:333.333 MHz (666.667 MT/s data rate) (Asynchronous), LBC:25   MHz

L1:    D-cache 32 kB enabled

       I-cache 32 kB enabled

Board: P1020SKU

CPLD:  V5.0

PCBA:  V4.0

I2C:   ready

DRAM:  Configuring DDR for 666.667 MT/s data rate

DDR:    1 GB

FLASH: 64 MB

L2:    256 KB enabled

MMC:  FSL_ESDHC: 0

EEPROM: Invalid ID (ff ff ff ff)

    eTSEC2 is in sgmii mode.

    PCIE2 connected to ULI as Root Complex (base addr ffe09000)

               Scanning PCI bus 01

        01  00  168c  0030  0280  ff

    PCIE2 on bus 00 - 01

    PCIE1 connected to Slot 2 as Root Complex (base addr ffe0a000)

               Scanning PCI bus 03

        03  00  168c  0030  0280  ff

    PCIE1 on bus 02 - 03

In:    serial

Out:   serial

Err:   serial

Net:   eTSEC1, eTSEC3

Hit any key to stop autoboot:  0

Labels (1)
0 Kudos
1 Solution
1,939 Views
Pavel
NXP Employee
NXP Employee

Replace u-boot on your board. Use u-boot from this SDK.

View solution in original post

0 Kudos
3 Replies
1,939 Views
sunder
Contributor I

Let me try and update.  Thanks for information.

0 Kudos
1,939 Views
sunder
Contributor I

My target is P1020WLAN Board.  The U-boot has been compiled as default. There is no change required U-boot. 

The existing current version of u-boot from SDKV1.4 has been uploaded.

The document  QorIQ-SDK-1.6-IC-RevB is gives the following steps as example

=> setenv ipaddr <ipaddr>

=> setenv serverip <serverip>

=> setenv netmask <netmask>

=> setenv ethaddr <mac-addr>

=> save

=> tftp 1000000 u-boot_9131RDB_NAND_100.bin

=> nand erase 0 100000

=> nand write 1000000 0 $filesize

After flashing the required bootloader:

1. Power off the board.

2. Ensure correct switch settings for NAND boot (SW4 – xxxx1001).

3. Power on the board

JTAG is not available, what is the step to place the u-boot in the alternative bank.  Even if something goes wrong, I can use existing one.  

0 Kudos
1,940 Views
Pavel
NXP Employee
NXP Employee

Replace u-boot on your board. Use u-boot from this SDK.

0 Kudos