Android 12 EVK_8MM uboot failed to load kernel

[dmitry_abdulov]

I fetched aosp-android-12.0.0_2.0.0 and built for  evk_8mm-userdebug.

There are no source code changes from me.

However, 8M Mini EVK Board failed to bootup.

There is a reboot loop after “Starting kernel ...”

What is it about "Moving Image from 0x40480000 to 0x40600000, end=435f0000" ?

Is anything else I'm missing?

U-Boot SPL 2022.04 (Oct 24 2022 - 14:48:44 -0700)
Can't find PMIC:PCA9450
DDRINFO: start DRAM init
DDRINFO: DRAM rate 3000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
SEC0: RNG instantiated
Normal Boot
Trying to boot from MMC2
NOTICE: BL31: v2.6(release):android-12.0.0_2.0.0-0-gca6eff3c5
NOTICE: BL31: Built : 14:49:02, Oct 24 2022

U-Boot 2022.04 (Oct 24 2022 - 14:48:44 -0700)

CPU: i.MX8MMQ rev1.0 1800 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 35C
Reset cause: POR
Model: NXP i.MX8MM EVK board
DRAM: 2 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x52]
Power supply on USB2
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50]
Core: 167 devices, 28 uclasses, devicetree: separate
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment

[*]-Video Link 0 (1920 x 1080)
[0] lcdif@32e00000, video
[1] mipi_dsi@32e10000, video_bridge
[2] adv7535@3d, panel
In: serial
Out: serial
Err: serial

BuildInfo:
- ATF ca6eff3

flash target is MMC:2
Net: eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
In boota get fastboot lock status error. Set lock status
Magic is incorrect.
Error validating A/B metadata from disk. Resetting and writing new A/B metadata to disk.
Writing A/B metadata to disk.
verify OK, boot 'boot_a'
Kernel load addr 0x40480000 size 48455 KiB
kernel @ 40480000 (50266112)
ramdisk @ 44680000 (14864469)
fdt @ 435f0400 (50398)
Moving Image from 0x40480000 to 0x40600000, end=435f0000
## Flattened Device Tree blob at 435f0400
Booting using the fdt blob at 0x435f0400
Using Device Tree in place at 00000000435f0400, end 00000000435ff8dd

Starting kernel ...

[Zhiming_Liu]

Hi @dmitry_abdulov 

The compile system of Android 11/12 will generate boot.img and boot-imx.img, boot.img includes gki kernel, boot-imx.img doesn't includes gki.

So you can change uuu_imx_android_flash.bat like below.

The version of kernel_imx in Android is same as GKI kernel version, so you will see same version after using boot-imx.img

[dmitry_abdulov]

Hi Qmiller,

Thank you very much!!

[Zhiming_Liu]

Update previous reply.

[dmitry_abdulov]

Hi Qmiller

Yes, I tried demo image and it works just fine.

I found, that I applied one change in the source code.

I disabled “IMX8MM_USES_GKI”.

Apparently, I can run the build when “IMX8MM_USES_GKI” is enabled, but if I disable it I meet the problem I mentioned above.

Is anything else I need to do to run the image without GKI?

[Zhiming_Liu]

Hi @dmitry_abdulov 

Please try to open all CONFIG_XXXX in SharedBoardConfig.mk

[dmitry_abdulov]

Hi Qmiller, 

I opened all of them and it didn't help, I still had the same issue.

Is anything else I can do?

[Zhiming_Liu]

I am compiling this BSP, will reply you when i solve this .

[dmitry_abdulov]

Hi Qmiller,

There are plenty "# CONFIG_XXX" commented out in "SharedBoardConfig.mk".

Do you mean they have to be defined as "y" in kernel config in that case?

[Zhiming_Liu]

Hi @dmitry_abdulov 

Have you tried the demo image on EVK?

Regads

Qmiller