Flashing Android PIE on vim3 failed with UBoot stuck: Host Ubuntu 20.04

Which system do you use? Android, Ubuntu, OOWOW or others?

Android

Which version of system do you use? Please provide the version of the system here:

KHADAS pre-built image from https://dl.khadas.com/firmware/vim3/android/vim3_pie_v211220.7z

Please describe your issue below:

Flashing/updating of Android PIE images e.g. is stuck during U-Boot Running. Instructions followed from: Install OS into eMMC on Ubuntu [Khadas Docs]. Host machine is Ubuntu 20.04 on x86_64 platform.

Post a console log of your issue below:

Same results with using either burn-tool or aml-burn-tool, later is invoked with -D option for verbose logging


$ aml-burn-tool -b VIM3 -i update.img -D
Burning image 'update.img' for 'VIM3/VIM3L' to eMMC...
host_os      = Linux cmucl1010638 5.15.0-119-generic #129~20.04.1-Ubuntu SMP Wed Aug 7 13:07:13 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
host_machine = Linux cmucl1010638 5.15.0-119-generic #129~20.04.1-Ubuntu SMP Wed Aug 7 13:07:13 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
SYSTEM       = linux-x86
EXE          = 

Command -> /mnt/ssd-p2/fx-wkspace/khadas_vim3/VIM3_Pie_V211220/utils/aml-flash-tool/tools/linux-x86/update 2>/dev/null identify 7 
- Results ---------------------------------------------------
 AmlUsbIdentifyHost
This firmware version is 3-2-0-0-0-1-0 
-------------------------------------------------------------


Command -> /mnt/ssd-p2/fx-wkspace/khadas_vim3/VIM3_Pie_V211220/utils/aml-flash-tool/tools/linux-x86/update 2>/dev/null identify 7 
- Results ---------------------------------------------------
 AmlUsbIdentifyHost
This firmware version is 3-2-0-0-0-1-0 
-------------------------------------------------------------


Command -> /mnt/ssd-p2/fx-wkspace/khadas_vim3/VIM3_Pie_V211220/utils/aml-flash-tool/tools/linux-x86/update 2>/dev/null bulkcmd "     echo 12345" 
- Results ---------------------------------------------------
 AmlUsbBulkCmd[     echo 12345]
[AmlUsbRom]Err:return len=0 < strLenBusy 11
[AmlUsbRom]Inf:bulkInReply 
ERR: AmlUsbBulkCmd failed! 
-------------------------------------------------------------


Command -> /mnt/ssd-p2/fx-wkspace/khadas_vim3/VIM3_Pie_V211220/utils/aml-flash-tool/tools/linux-x86/update 2>/dev/null identify 7 
- Results ---------------------------------------------------
 AmlUsbIdentifyHost
This firmware version is 3-2-0-0-0-1-0 
-------------------------------------------------------------


Command -> /mnt/ssd-p2/fx-wkspace/khadas_vim3/VIM3_Pie_V211220/utils/aml-flash-tool/tools/linux-x86/update 2>/dev/null rreg 4 0xff800228 
- Results ---------------------------------------------------
 [update]Total tansfer size 0x4

FF800228: e0f83180  
-------------------------------------------------------------

0xff800228      = 0xe0f83180
Secure boot bit = 0
Unpacking image 
[Msg]Image package version 0x2
[Msg]Unpack item [USB         ,              DDR] to (/tmp/aml-flash-tool-2bOz/DDR.USB) size:1583984 bytes
[Msg]Backup item [USB         ,            UBOOT] backItemId[0][USB, DDR]
[Msg]Unpack item [PARTITION   ,         _aml_dtb] to (/tmp/aml-flash-tool-2bOz/_aml_dtb.PARTITION) size:93274 bytes
[Msg]Unpack item [UBOOT       ,     aml_sdc_burn] to (/tmp/aml-flash-tool-2bOz/aml_sdc_burn.UBOOT) size:1584496 bytes
[Msg]Unpack item [ini         ,     aml_sdc_burn] to (/tmp/aml-flash-tool-2bOz/aml_sdc_burn.ini) size:589 bytes
[Msg]Unpack item [PARTITION   ,             boot] to (/tmp/aml-flash-tool-2bOz/boot.PARTITION) size:9584640 bytes
[Msg]Backup item [PARTITION   ,       bootloader] backItemId[0][USB, DDR]
[Msg]Unpack item [PARTITION   ,             dtbo] to (/tmp/aml-flash-tool-2bOz/dtbo.PARTITION) size:438 bytes
[Msg]Unpack item [PARTITION   ,             logo] to (/tmp/aml-flash-tool-2bOz/logo.PARTITION) size:929424 bytes
[Msg]Backup item [dtb         ,           meson1] backItemId[2][PARTITION, _aml_dtb]
[Msg]Unpack item [PARTITION   ,              odm] to (/tmp/aml-flash-tool-2bOz/odm.PARTITION) size:544844 bytes
[Msg]Unpack item [conf        ,         platform] to (/tmp/aml-flash-tool-2bOz/platform.conf) size:155 bytes
[Msg]Unpack item [PARTITION   ,          product] to (/tmp/aml-flash-tool-2bOz/product.PARTITION) size:14610508 bytes
[Msg]Unpack item [PARTITION   ,         recovery] to (/tmp/aml-flash-tool-2bOz/recovery.PARTITION) size:16277504 bytes
[Msg]Unpack item [PARTITION   ,           system] to (/tmp/aml-flash-tool-2bOz/system.PARTITION) size:1384825076 bytes
[Msg]Unpack item [PARTITION   ,           vbmeta] to (/tmp/aml-flash-tool-2bOz/vbmeta.PARTITION) size:4096 bytes
[Msg]Unpack item [PARTITION   ,           vendor] to (/tmp/aml-flash-tool-2bOz/vendor.PARTITION) size:249520300 bytes
[Msg]Write config file "/tmp/aml-flash-tool-2bOz/image.cfg" OK!
Image unpack OK!
[OK]

Parsing image configuration files
---------------------------------
platform_conf_name  = platform.conf
ddr_filename        = DDR.USB
uboot_filename      = DDR.USB
uboot_comp_filename = 
dtb_meson_filename  = 
dtb_meson1_filename = _aml_dtb.PARTITION
dtb_meson1_enc_filename = 
ddr_enc_filename    = 
uboot_enc_filename  = 
keys_filename       = 
platform            = 0x0811
bin_params          = 
ddr_load            = 0xfffa0000
ddr_run             = 0xfffa0000
uboot_down          = 
uboot_decomp        = 
uboot_enc_down      = 
uboot_enc_run       = 
uboot_load          = 
uboot_run           = 
bl2_params          = 
nb_partitions       = 11

Partition list
--------------
0 _aml_dtb.PARTITION _aml_dtb normal
1 boot.PARTITION boot normal
2 DDR.USB bootloader normal
3 dtbo.PARTITION dtbo normal
4 logo.PARTITION logo normal
5 odm.PARTITION odm sparse
6 product.PARTITION product sparse
7 recovery.PARTITION recovery normal
8 system.PARTITION system sparse
9 vbmeta.PARTITION vbmeta normal
10 vendor.PARTITION vendor sparse

Bootloader/DTB files
--------------------
bootloader_file = /tmp/aml-flash-tool-2bOz/DDR.USB
dtb_file        = /tmp/aml-flash-tool-2bOz/_aml_dtb.PARTITION

Initializing ddr 
Command -> /mnt/ssd-p2/fx-wkspace/khadas_vim3/VIM3_Pie_V211220/utils/aml-flash-tool/tools/linux-x86/update 2>/dev/null write /tmp/aml-flash-tool-2bOz/DDR.USB 0xfffa0000 0x10000 
- Results ---------------------------------------------------
 ..
Transfer Complete! total size is 65536 Bytes 
-------------------------------------------------------------


Command -> /mnt/ssd-p2/fx-wkspace/khadas_vim3/VIM3_Pie_V211220/utils/aml-flash-tool/tools/linux-x86/update 2>/dev/null run 0xfffa0000 
- Results ---------------------------------------------------
 [update]Run at Addr fffa0000
AmlUsbRunBinCode:ram_addr=fffa0000 
-------------------------------------------------------------

........[OK]
Running u-boot 
Command -> /mnt/ssd-p2/fx-wkspace/khadas_vim3/VIM3_Pie_V211220/utils/aml-flash-tool/tools/linux-x86/update 2>/dev/null bl2_boot /tmp/aml-flash-tool-2bOz/DDR.USB 
- Results ---------------------------------------------------
 [LUSB][AMLC]dataSize=16384, offset=65536, seq 0
[LUSB]requestType=0
[LUSB]ERR(L1016):Fail in down data, want 16384, but -110
[LUSB]ERR(L1187):fail in download, sequence 0 
-------------------------------------------------------------

[KO]

$ burn-tool -v aml -b VIM3 -i update.img
Try to burn Amlogic image...
Burning image 'update.img' for 'VIM3/VIM3L' to eMMC...
Unpacking image [OK]
Initializing ddr ........[OK]
Running u-boot [KO]

Serial connection via USB-TTL device shows U-boot is stuck running.

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: 211185733

BL2 Built : 19:23:21, Sep 18 2020. g12b g9fde858 - 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: 0c96ba88
board id: 10
Cfg max: 12, cur: 1. Board id: 255. Force loop cfg

USB connection between host and VIM3 board is via KHADAS USB-C to USB-A cable with USB-A connected directly to a USB port on the host machine. Amlogic USB device is correctly detected on the host.

lsusb | grep Amlogic
Bus 003 Device 047: ID 1b8e:c003 Amlogic, Inc. GX-CHIP

UDEV rules were set up by INSTALL script and list the correct USB device.

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="1b8e", ATTR{idProduct}=="c003", MODE:="0666"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="1b8e", ATTR{idProduct}=="c004", MODE:="0666"

Hello, please try following the command below

burn-tool -v aml -b VIM3 -i /path/to/image

Please see the listing I posted, it also contains the attempt using burn-tool, posted again below.

$ burn-tool -v aml -b VIM3 -i update.img
Try to burn Amlogic image...
Burning image 'update.img' for 'VIM3/VIM3L' to eMMC...
Unpacking image [OK]
Initializing ddr ........[OK]
Running u-boot [KO]