[VIM3 Pro] AOSP 12 (Yukawa) Boot Loop - Stuck at "Reading DTB for vim3"

Hi, I’m trying to boot AOSP 12 (Yukawa) on my VIM3 Pro (4GB RAM), but I’m stuck in a boot loop.

Environment:

  • Board: Khadas VIM3 Pro (v14)

  • OS: AOSP 12 (Build target: yukawa-userdebug)

  • Kernel: 5.4 (standard yukawa)

  • Power: USB-PD (ThinkPad X1 Carbon Charger) - Power supply is stable.

Steps taken:

  1. Built AOSP 12 following the standard Google/Yukawa instructions.

  2. Flashed boot.img, super.img, and dtb.img via fastboot.

  3. Erased misc and dtbo partitions to ensure a clean boot.

The Problem: The device shows a grey screen and immediately reboots. I captured the serial log using an Arduino-based debugger (115200bps).

Serial Log:

G12B:BL:6e7c85:2a3b91;FEAT:E0F83180:402000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;0.
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0000 - pwm id 0x01
bl2_stage_init 0xc1
bl2_stage_init 0x02

L0:00000000
L1:20000703
L2:00008067
L3:14000000
B2:00402000
B1:e0f83180

TE: 249449

BL2 Built : 16:01:39, May 25 2020. g12b gb6bfa83 - gongwei.chen@droid11-sz

Board ID = 10
Set A53 clk to 24M
Set A73 clk to 24M
Set clk81 to 24M
A53 clk: 1200 MHz
A73 clk: 1200 MHz
CLK81: 166.6M
smccc: 000417a5
eMMC boePIE:

,0.0;MhNNIN o

ets 4 0 021.01-Model: Kh3MMC: sd*** WarnIn:    serial@3000
Verify GPT: success!
dev: pinctrl@14
dev: pinctrl@40
gpio: pin 88 (gsO65536 blocks read: OK
Preparing FDT...
  Reading DTB for vim3...16384 blocks rea
ztr dndu  n[o0ta0u[  : t[   arc0[m t306r35[[ [ [s47 c t5]f o.ftlpLmoll6 gdd[[  [  [  [ir: [JT h 0 1ip1[  9[r noaofs03 e57[a[3S f[ el8e[ 2(.[
COrChIIINaIN 9h10.0;M ndhbgs2t wd [ eE;RRE02GPI02

U-Boot 2021.015Model: K3MMC:  s3*** WarIn:    serial@3000
etsl 0 
Verify GPT: success!
dev: pinctrl@14
dev: pinctrl@40
gpio: pin 88 (gpiso65536 blocks read: OK
Preparing FDT...
16384 blocks rea
(Enter FastBoot)

Question: Does the standard Yukawa dtb.img support the 4GB Pro model out of the box? Or do I need to modify the Device Tree / BoardConfig to account for the memory difference?

Any advice would be appreciated. Thanks!

@Gy_Lh ,
Can you use Android 14 or Android 16?
We collaborated with Baylibre to adapt AOSP for Android 14 and Android 16.