IMX8QM-EVK android boot fail in android 12 bsp

althafahammed — Wed, 15 Jan 2025 09:41:19 GMT

I built Android 12.0.0_2.0.0 (L5.15.32_2.0.0 BSP) for the IMX-8qm EVK board with the lunch configuration 82 (mek_8q_car-userdebug). Initially, the build was unsuccessful due to an out-of-space issue, which I resolved by changing the FILE_SYSTEM_TYPE from "ext4" to "erofs." After that, the build was successful. However, some of the .img files, such as init_boot.img and super.img, were missing from the out folder.

We flashed the build using the following steps:

adb reboot bootloader
sudo ./fastboot_imx_flashall.sh -f imx8qm -a -d md -e
sudo fastboot reboot

The flashing process completed successfully, but after the fastboot reboot command, the device started displaying continuous logs indicating "starting kernel." The logs eventually ended with the error message: avb_slot_verify.c:700: ERROR: init_boot_b: Error loading footer.

full log
______________

Normal Boot
Trying to boot from MMC1
Booting from bootloader_a...
UU
boot args 0x2000000 0xfe000000 0x2000 0x0
initializing trusty (Project: imx8qm_a72, Built: 10:15:43 May 30 2022)
Core: 180 devices, 28 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

[*]-Video Link 0 (1280 x 720)
        [0] dpu@56180000, video
        [1] lvds-channel@0, display
        [2] lvds-to-hdmi-bridge@4c, video_bridge
In:    serial
Out:   serial
Err:   serial

BuildInfo:
- SCFW 8172eaea, SECO-FW c9de51c0, IMX-MKIMAGE a8bb8edb, ATF 44c44f0
- U-Boot 2022.04

flash target is MMC:0
Net:   eth0: ethernet@5b040000 [PRIME], eth1: ethernet@5b050000
INFO Initializing Trusty device
INFO selected trusty api version: 3 (requested 3)
INFO Initializing Trusty IPC device
INFO Initializing RPMB storage proxy service
INFO Initializing Trusty Keymaster client
INFO Initializing Trusty Hardware Crypto client
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
Verifying slot _a ...
Writing A/B metadata to disk.
verify OK, boot 'boot_a'
Kernel load addr 0x80280000 size 20122 KiB
kernel   @ 80280000 (41943040)
ramdisk @ fc000000 (10910699)
fdt      @ 82c00400 (137843)
Moving Image from 0x80280000 to 0x80400000, end=82c00000
## Flattened Device Tree blob at 82c00400
   Booting using the fdt blob at 0x82c00400
ERROR: reserving fdt memory region failed (addr=901ff000 size=1000 flags=4)
ERROR: reserving fdt memory region failed (addr=91f00000 size=100000 flags=0)
   Using Device Tree in place at 0000000082c00400, end 0000000082c24e72

Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
Verifying slot _b ...
fsl_read_from_partition_multi: no init_boot_b partition
idx 0, ptn 0 name='gpt' start=0 len=2048
idx 1, ptn 0 name='' start=0 len=0
idx 2, ptn 0 name='all' start=0 len=62160896
idx 3, ptn 0 name='bootloader0' start=0 len=64512
idx 4, ptn 1 name='bootloader_a' start=16384 len=32768
idx 5, ptn 2 name='bootloader_b' start=49152 len=32768
idx 6, ptn 3 name='dtbo_a' start=81920 len=8192
idx 7, ptn 4 name='dtbo_b' start=90112 len=8192
idx 8, ptn 5 name='boot_a' start=98304 len=131072
idx 9, ptn 6 name='boot_b' start=229376 len=131072
idx 10, ptn 7 name='system_a' start=360448 len=3145728
idx 11, ptn 8 name='system_b' start=3506176 len=3145728
idx 12, ptn 9 name='system_ext_a' start=6651904 len=524288
idx 13, ptn 10 name='system_ext_b' start=7176192 len=524288
idx 14, ptn 11 name='misc' start=7700480 len=8192
idx 15, ptn 12 name='metadata' start=7708672 len=32768
idx 16, ptn 13 name='presistdata' start=7741440 len=2048
idx 17, ptn 14 name='vendor_a' start=7745536 len=1310720
idx 18, ptn 15 name='vendor_b' start=9056256 len=1310720
idx 19, ptn 16 name='product_a' start=10366976 len=3670016
idx 20, ptn 17 name='product_b' start=14036992 len=3670016
idx 21, ptn 18 name='userdata' start=17707008 len=9539584
idx 22, ptn 19 name='fbmisc' start=27246592 len=2048
idx 23, ptn 20 name='vbmeta_a' start=27250688 len=2048
idx 24, ptn 21 name='vbmeta_b' start=27254784 len=2048
avb_slot_verify.c:700: ERROR: init_boot_b: Error loading footer.

From the log, it appears that the system first attempts to boot from bootloader_a multiple times. After that, it attempts to boot from bootloader_b, but no further serial logs are displayed, and the device remains in fastboot mode.

Re: IMX8QM-EVK android boot fail in android 12 bsp

Bio_TICFSL — Thu, 16 Jan 2025 13:56:12 GMT

Hello,

It looks like you are not installed the correct partition, erase everything in the sd and try to burn again the image and tested since it goes out of memory.

Regards

Re: IMX8QM-EVK android boot fail in android 12 bsp

althafahammed — Fri, 17 Jan 2025 04:41:30 GMT

Hello,

Can you please elaborate the procedure. Also in the same board we could able to flash android 13 build successfully
I have one query is 12.0.0_2.0.0 (L5.15.32_2.0.0 BSP) version support imx-8qm evk board ??

Re: IMX8QM-EVK android boot fail in android 12 bsp

Bio_TICFSL — Fri, 17 Jan 2025 12:34:01 GMT

Hello,

You can see the android 13 user guide:

https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/imx-processors/217786/1/ANDROID_USERS_GUIDE.pdf

Where it has a table with all partition and how it burn to your board.

Regards

Re: IMX8QM-EVK android boot fail in android 12 bsp

althafahammed — Thu, 23 Jan 2025 12:07:51 GMT

I have made a change in the BoardConfigCommon file change the system file type from ext4 to erofs

After reverting that change build flash properly

topic IMX8QM-EVK android boot fail in android 12 bsp in i.MX Processors

IMX8QM-EVK android boot fail in android 12 bsp

Re: IMX8QM-EVK android boot fail in android 12 bsp

Re: IMX8QM-EVK android boot fail in android 12 bsp

Re: IMX8QM-EVK android boot fail in android 12 bsp

Re: IMX8QM-EVK android boot fail in android 12 bsp