fitImage boot failed for imx8mn

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

fitImage boot failed for imx8mn

Jump to solution
2,727 Views
vinothkumars
Senior Contributor IV

Dear NXP,

 

I got following error while boot custom fitImage for IMX8MN-EVK board,

Error: inflate() returned -3

 

## Loading kernel from FIT Image at 40480000 ...
Using 'conf@imx8mn.dtb' configuration
Trying 'kernel@1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x404800ec
Data Size: 129349480 Bytes = 123.4 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x47800000
Entry Point: 0x40480000
Hash algo: sha256
Hash value: 2efcf840e02e2759d71164a5ee29dbcd1207a660572cd2f34c0d70998fc2f397
Verifying Hash Integrity ... sha256+ OK
VINOTH +++++++++++++++++++++++++++== FIT2 bootm_find_os ++++++++++++++++++
## Loading ramdisk from FIT Image at 40480000 ...
Using 'conf@imx8mn.dtb' configuration
Trying 'ramdisk@1' ramdisk subimage
Description: core-image-base
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x47fe5584
Data Size: 117961425 Bytes = 112.5 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha256
Hash value: 9faa0b32287198af6c94d94b8d1892c2f741ce955023529e86c46fbf297a3278
Verifying Hash Integrity ... sha256+ OK
VINOTH +++++++++++++++++++++++++++==FIT4 bootm_find_images find ramdisk: 0 ++++++++++++++++++
## Loading fdt from FIT Image at 40480000 ...
Using 'conf@imx8mn.dtb' configuration
Trying 'fdt@imx8mn.dtb' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x47fdb96c
Data Size: 39757 Bytes = 38.8 KiB
Architecture: AArch64
Hash algo: sha256
Hash value: 3c0cb713acf4bf2130e1def2b18e93f7a0067cd14c0632cecc51b35edda42fd5
Verifying Hash Integrity ... sha256+ OK
Booting using the fdt blob at 0x47fdb96c
VINOTH +++++++++++++++++++++++++++==FIT4 bootm_find_images find flattened device tree ret: 0 ++++++++++++++++++
VINOTH +++++++++++++++++++++++++++==FIT4 bootm_find_images ++++++++++++++++++
VINOTH +++++++++++++++++++++++++++==FIT4 bootm_find_images find all of the loadables ret: 0 ++++++++++++++++++
Uncompressing Kernel Image
Error: inflate() returned -3
VINOTH ++++++++++++++++++++++ bootm_load_os : image_decomp ret: -1
VINOTH +++++++++++++++++++ handle_decomp_error +++++++++++++
gzip compressed: uncompress error -1
Must RESET board to recover
resetting ...

 

 

 

local.conf,

# Add FIT image dependency
KERNEL_CLASSES += "kernel-fitimage"
KERNEL_IMAGETYPES += "fitImage"

# Specify FIT image variables
UBOOT_ENTRYPOINT = "0x47800000"
UBOOT_LOADADDRESS = "0x47800000"

INITRAMFS_IMAGE = "core-image-base"
INITRAMFS_IMAGE_BUNDLE = "1"
IMAGE_FSTYPES = "cpio.gz"

 

Please check the local.conf file for fitImage

 

 

 

 

Regards,
Vinothkumar Sekar
Tags (2)
0 Kudos
1 Solution
2,647 Views
vinothkumars
Senior Contributor IV

This is due to load address issue.

 

original solutions here,

https://community.nxp.com/t5/i-MX-Processors/fitImage-loadaddress-and-entrypoint-for-imx8mn-evk/m-p/...

Regards,
Vinothkumar Sekar

View solution in original post

0 Kudos
5 Replies
2,706 Views
vinothkumars
Senior Contributor IV

Thank you @igorpadykov  for the reply,

Actually I am looking for kernel-fit (Kernel, DTB, Initramfs) Image like this,

 

local.conf,

# Add FIT image dependency
KERNEL_CLASSES += "kernel-fitimage"
KERNEL_IMAGETYPES += "fitImage"

# Specify FIT image variables
UBOOT_ENTRYPOINT = "0x47800000"
UBOOT_LOADADDRESS = "0x47800000"

INITRAMFS_IMAGE = "core-image-base"
INITRAMFS_IMAGE_BUNDLE = "1"
IMAGE_FSTYPES = "cpio.gz"

 

Please check the local.conf file for kernel-fitImage

 

 

Regards,
Vinothkumar Sekar
0 Kudos
2,700 Views
igorpadykov
NXP Employee
NXP Employee
0 Kudos
2,691 Views
vinothkumars
Senior Contributor IV

Thank you @igorpadykov for the reply,

Will you please tell what return -3 

-5 = is image is too large

but, what is -3 returns,

 

Error: inflate() returned -3

 

Regards,
Vinothkumar Sekar
0 Kudos
2,648 Views
vinothkumars
Senior Contributor IV

This is due to load address issue.

 

original solutions here,

https://community.nxp.com/t5/i-MX-Processors/fitImage-loadaddress-and-entrypoint-for-imx8mn-evk/m-p/...

Regards,
Vinothkumar Sekar
0 Kudos