If folks like bumerc have failed to understand or figure out how Armbian booted in the various CE forum threads I don't stand much chance of a eureka moment (as I know far less then them) .. so I'll pass on the opportunity for a fruitless and frustrating investigation. I'd prefer to spend my limited time for Amlogic fiddling on other dev things. Sorry.
It's okay, thank you for your reply.
Hi chewitt
I have a Xiaomi Mibox 3 MDZ-16-AA with S905H chip. I got UART connected to it and set the uboot env like this:
setenv bootcmd "run start_autoscript; run storeboot;"
setenv start_autoscript "if usb start ; then run start_usb_autoscript; fi; if mmcinfo; then run start_mmc_autoscript; fi;"
setenv start_mmc_autoscript "if fatload mmc 0 1020000 s905_autoscript; then autoscr 1020000; fi;"
setenv start_usb_autoscript "if fatload usb 0 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 1 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 2 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 3 1020000 s905_autoscript; then autoscr 1020000; fi;"
setenv upgrade_step "0"
saveenvThen i used the LibreELEC-AMLGX.arm-10.0.0-box.img.gz image, set dtb as meson-gxbb-p200.dtb, the kernel seems loaded but it didn't boot
Here is the UART log:LE10-Fail
Before i tried with LE, i've found out ARMBIAN do actually boot (with meson-gxbb-p200.dtb or meson-gxbb_p200_1G_wetek_hub.dtb files). And i tried with CE, more info here Xiaomi Mi Box 3 MDZ-16-AA booting stuck at kernel startup
I know you did a great job on Wetek Play, which is S905H too. So i think maybe you can help me with this. 
Or maybe i should try replacing the stock uboot?
