Vim3: cannot find amlogic,g12a-pcie node

hello guys,
I try to run android s on vim3, and I got the message as title at uboot time

I follow the instruction of the page
https://source.android.com/setup/build/devices#vim3_and_vim3l_boards
Compiling userspace/ Installing initial images/ Flashing images.
After flashing all image, vim3 boot successfully and I can see the version android s in setting page.
However, it show the fail message when I boot the device up.

I also find there is patch here,
https://patchwork.ozlabs.org/project/uboot/patch/20200921073415.24211-5-narmstrong@baylibre.com/
Why the uboot file, u-boot_kvim3_noab.bin on the installing page, has this problem?

here is the boot log

resetting …
bl31 reboot reason: 0xd
bl31 reboot reason: 0x0
system cmd 1.
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: 331556

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

Board ID = 8
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: 00055809
eMMC boot @ 1
sw8 s
board id: 8
Load FIP HDR DDR from eMMC, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 1
Get wrong ddr fw magic! Error!!
fw parse done
PIEI prepare done
ddr saved addr:00016000
Load ddr parameter from eMMC, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0
00000000
emmc switch 0 ok
fastboot data verify
result: 255
Cfg max: 12, cur: 1. Board id: 255. Force loop cfg
LPDDR4 probe

LPDDR4_PHY_V_0_1_22-Built : 16:01:44, May 25 2020. g12b gb6bfa83 - gongwei.chen@droid11-sz
ddr clk to 1608MHz
00000000
emmc switch 1 ok

dmc_version 0001
Check phy result
INFO : End of CA training
INFO : End of initialization
INFO : Training has run successfully!
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : End of read dq deskew training
INFO : End of MPR read delay center optimization
INFO : End of Write leveling coarse delay
INFO : End of read delay center optimization
INFO : Training has run successfully!
Check phy result
INFO : End of initialization
INFO : End of MPR read delay center optimization
INFO : End of write delay center optimization
INFO : End of read delay center optimization
INFO : End of max read latency training
INFO : Training has run successfully!
1D training succeed
Check phy result
INFO : End of initialization
INFO : End of 2D read delay Voltage center optimization
INFO : End of 2D read delay Voltage center optimization
INFO : End of 2D write delay Voltage center optimization
INFO : End of 2D write delay Voltage center optimization
INFO : Training has run successfully!

soc_vref_reg_value 0x 00000026 00000028 00000026 00000027 00000027 00000025 00000026 00000027 00000026 00000025 00000026 00000026 00000027 00000026 00000024 00000027 00000026 00000025 00000025 00000025
dram_vref_reg_value 0x 00000013
2D training succeed
auto size-- 65535DDR cs0 size: 2048MB
DDR cs1 size: 2048MB
DMC_DDR_CTRL: 00e00024DDR size: 3928MB
cs0 DataBus test pass
cs1 DataBus test pass
cs0 AddrBus test pass
cs1 AddrBus test pass

non-sec scramble use zero key
ddr scramble enabled

100bdlr_step_size ps== 437
result report
boot times 0Enable ddr reg access
00000000
emmc switch 3 ok
Authentication key not yet programmed
get rpmb counter error 0x00000007
00000000
emmc switch 1 ok
Load FIP HDR from eMMC, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 1
Load BL3X from eMMC, src: 0x00078200, des: 0x01768000, size: 0x000ab200, part: 1
0.0;M3 CHK:0;cm4_sp_mode 0
[Image: g12b_v1.1.3394-7d43064d5 2020-05-07 15:37:11 gongwei.chen@droid11-sz]
OPS=0x10
ring efuse init
chipver efuse init
29 0b 10 00 01 0f 0f 00 00 06 33 32 4e 31 53 50
[1.032230 Inits done]
secure task start!
high task start!
low task start!
run into bl31
NOTICE: BL31: v1.3(release):d9e1bbe85
NOTICE: BL31: Built : 19:07:43, Sep 7 2020
NOTICE: BL31: G12A normal boot!
NOTICE: BL31: BL33 decompress pass
ERROR: Error initializing runtime service opteed_fast

U-Boot 2021.01-00035-gde44e287b6 (Feb 02 2021 - 18:02:13 +0100) khadas-vim3

Model: Khadas VIM3
SoC: Amlogic Meson G12B (A311D) Revision 29:b (10:2)
DRAM: 3.8 GiB
MMC: sd@ffe03000: 0, sd@ffe05000: 1, mmc@ffe07000: 2
Loading Environment from MMC… *** Warning - bad CRC, using default environment

In: serial@3000
Out: serial@3000
Err: serial@3000
Net: eth0: ethernet@ff3f0000
Verify GPT: success!
switch to partitions #0, OK
mmc2(part 0) is current device

MMC read: dev # 2, block # 1024, count 4096 … 4096 blocks read: OK
There is no valid bmp file at the given address
Hit any key to stop autoboot: 0
Verify GPT: success!
dev: pinctrl@14
dev: pinctrl@40
gpio: pin 88 (gpio 88) value is 1
Loading Android boot partition…
switch to partitions #0, OK
mmc2(part 0) is current device
Running without AVB…

MMC read: dev # 2, block # 23552, count 65536 … 65536 blocks read: OK
Preparing FDT…
Reading DTB for vim3…
Reading DTBO for vim3…

MMC read: dev # 2, block # 6144, count 16384 … 16384 blocks read: OK
Applying DTBOs…
0x493 (1171)
Running Android…

Booting Android Image at 0x01080000 …

Kernel load addr 0x11080000 size 19762 KiB
Kernel command line: no_console_suspend console=ttyAML0,115200 earlycon printk.devkmsg=on androidboot.boot_devices=soc/ffe07000.mmc init=/init firmware_class.path=/vendor/firmware androidboot.hardware=yg
RAM disk load addr 0x11000000 size 1241 KiB

Flattened Device Tree blob at 01000000

Booting using the fdt blob at 0x1000000
Uncompressing Kernel Image
Loading Ramdisk to 7fec9000, end 7ffff312 … OK
Loading Device Tree to 000000007fe46000, end 000000007fec8fff … OK
Cannot setup simplefb: node not found
vim3: cannot find amlogic,g12a-pcie node

Starting kernel …

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]

Could any know this?thank you.

VIM3 can use USB3 (default) or PCIe (if the dts is changed to enable it, disabling USB3). So u-boot must check for the pcie node. It’s not an error and it could be better worded, but it’s simply reporting that the dts did not enable pcie.

3 Likes