Thank you for help, could you please help me one more time. I can't understand, how to start such image from u-boot?
Now I have FIT image over ubi volume rootfsa, boot sequence:
setenv bootargs "earlycon=uart8250,mmio,0x21c0500 ubi.mtd=ubi rootfstype=squashfs,ubifs root=/dev/ram0 rw console=ttyLP0,115200 cma=32M@0x0-0x60000000 vmalloc=544M"
ubi read 0x82000000 rootfsa
bootm 0x82000000
Image2 contains only squashfs rootfs
FIT image structure
## Checking Image at 82000000 ...
FIT image found
FIT description: U-Boot fitImage for 5.4.168 kernel
Image 0 (kernel-0)
Description: Linux Kernel
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x820000d4
Data Size: 5128365 Bytes = 4.9 MiB
Architecture: ARM
OS: Linux
Load Address: 0x81000000
Entry Point: 0x81000000
Hash algo: sha1
Hash value: cf8aa43d5a899d5f5006b3d760945931929603e3
Image 1 (fdt-0)
Description: Flattened Device Tree blob Glomex_LS1021A
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x824e4288
Data Size: 21720 Bytes = 21.2 KiB
Architecture: ARM
Load Address: 0x8f000000
Hash algo: sha1
Hash value: e7ac479784acd82715629ebe34c0fd33a17fc1fd
Image 2 (ramdisk-0)
Description: ramdisk
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x824e9820
Data Size: 29373970 Bytes = 28 MiB
Architecture: ARM
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha1
Hash value: 639c5f87c0ea2f85c2ec22b4660aec18168e025a
Configuration 0 (conf-1)
Description: Boot Linux kernel with FDT blob + ramdisk
Kernel: kernel-0
Init Ramdisk: ramdisk-0
FDT: fdt-0
Hash algo: sha1
Hash value: unavailable
## Checking hash(es) for FIT Image at 82000000 ...
Hash(es) for Image 0 (kernel-0): sha1+
Hash(es) for Image 1 (fdt-0): sha1+
Hash(es) for Image 2 (ramdisk-0): sha1+