Build FIT image for IMX8MNano

[vinothkumars]

Dear NXP,

I am looking for guide/release notes or user guide to build fit-image.

fitimage - Kernel+DTB+Initramfs

Is there any configuration to be done to build FIT-Image for IMX8Mnano platform ?

Is there any bitbake command to build FIT-Image for IMX8Mnano platform ?

[vinothkumars]

Hi I able to create the FIT image,

             fitImage-linux.bin--5.4-r0-evk-20210130123338.bin

Will you please tell me how to flash this image on target ?

[Zhiming_Liu]

Hi

UUU does not have direct command to flash FIT image.You can try to refer UUU.pdf and write the FIT image into address.

BR

Zhiming

[vinothkumars]

Thank you @Zhiming_Liu for the reply.

I able to boot but, stopped 

=> bootm fitImage

## 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: 11772301 Bytes = 11.2 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x43000000
Entry Point: 0x40480000
Hash algo: sha256
Hash value: c3b6d10c36ec5769ecb2e7725350f4df98025536cdfc8c2165e77571401064a3
Verifying Hash Integrity ... sha256+ OK
## 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: 0x40fba394
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 0x40fba394
Uncompressing Kernel Image
Using Device Tree in place at 0000000040fba394, end 0000000040fc6ee0
failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
failed to get any video link display timings
probe video device failed, ret -22

Starting kernel ...

unable to select a mode
device_remove: Device 'mmc@30b60000.blk' failed to remove, but children are gone
"Synchronous Abort" handler, esr 0x02000000
elr: ffffffffc375c000 lr : 00000000402026e8 (reloc)
elr: 0000000040480000 lr : 00000000bcf266e8
x0 : 0000000040fba394 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 0000000000000000
x4 : 0000000040480000 x5 : 0000000000000001
x6 : 0000000000000008 x7 : 0000000000000000
x8 : 00000000baf1a8c8 x9 : 0000000000000002
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 0000000000000000
x14: 00000000baf1b688 x15: 00000000bcf25b14
x16: 00000000bcfa0c34 x17: 00000000baf53c10
x18: 00000000baf23dc8 x19: 00000000bcfde6d0
x20: 0000000000000000 x21: 0000000000000400
x22: 0000000000000001 x23: 00000000baf2e098
x24: 00000000baf2e098 x25: 00000000bcfc9220
x26: 0000000040480000 x27: 00000000bcf26710
x28: 00000000404800ec x29: 00000000baf1ab90

Code: b1a9b1a9 b1a9b1a9 b1a9b1a9 b1a9b1a9 (edfe0dd0)
Resetting CPU ...

resetting ...

[vinothkumars · Accepted solution]

This is resolved by increasing loadaddress as per image size,

Original solution here,

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