Devmfc

Hi,
 
You are posting on the Armbian forum.
The images you refer to are not Armbian images.
The people of Armbian don't like their forum be polluted with non-Armbian support request. I think that is quite understandable, don't you?
 
That being said, this answer is also true for Armbian tvbox, so maybe the answer is allowed: 
 
All those tvboxes are different, even if they look the same or even have the same 'model name' from the outside.
Especially the wifi modules are a lottery. So you have to be lucky to get a standard supported wifi module. And otherwise you'll have to learn a lot, google a lot to get wifi working. That's the 'fun' of tinkering with those cheap boxes. If you want a working wifi and don't want to learn all that... you are better of buying a well supported SBC instead.
 
Some pointers that might be helpful:
decompile the dtb and look if the aml_wifi gpio's for power are the same gpios as in the DTB you use for mainline linux (sdio-pwrseq node)  sometimes it can help to lower the max-frequency property for the sdio node run ( vendev=( $( cat /sys/bus/mmc/devices/mmc2:*/{vendor,device} ) ) && echo "wifi SDIO ID: ${vendev[0]}:${vendev[1]}" )  to get the driver vendor ID and device ID. If that doesn't work, previous two points are probably not ok. (Or wifi is not on SDIO bus, but is not very likely) (alternatively) open the box, look for the wifi markings and search google for the linux driver source and compile that driver Have fun!
 

Hi all,
I don't understand why you want or need to use those chain loaded u-boot blobs? 
 
The vendor u-boot bootloaders can boot mainline Linux perfectly without them. So they are not needed.
All it takes are some simple modifications of some of the Armbian u-boot scripts.
 
Just copy the attached files to the fat partition of the Armbian image after burning the image to a USB disk. 
Edit armbianEnv.txt for the right DTB (so not in extlinux.conf) and you can boot the newer Armbian images without u-boot.ext.
 
I tested it with the Armbian_23.8.1_Aml-s9xx-box_bookworm_current_6.1.50_minimal.img.xz image on the following SOC's:
S905x (GXL) S912 (GXM)  S905x2 (G12A) S922X (G12B) S905X3 (SM1) assumption: you have vendor u-boot (the one that came with the box) running on eMMC. If you don't, you can just restore the stock Android image with Amlogic USB Burning tool.
 
All needed files and a more detailed description is on github
 
aml_autoscript armbianEnv.txt gxl-fixup.scr s905_autoscript

Hi all,
I don't understand why you want or need to use those chain loaded u-boot blobs? 
 
The vendor u-boot bootloaders can boot mainline Linux perfectly without them. So they are not needed.
All it takes are some simple modifications of some of the Armbian u-boot scripts.
 
Just copy the attached files to the fat partition of the Armbian image after burning the image to a USB disk. 
Edit armbianEnv.txt for the right DTB (so not in extlinux.conf) and you can boot the newer Armbian images without u-boot.ext.
 
I tested it with the Armbian_23.8.1_Aml-s9xx-box_bookworm_current_6.1.50_minimal.img.xz image on the following SOC's:
S905x (GXL) S912 (GXM)  S905x2 (G12A) S922X (G12B) S905X3 (SM1) assumption: you have vendor u-boot (the one that came with the box) running on eMMC. If you don't, you can just restore the stock Android image with Amlogic USB Burning tool.
 
All needed files and a more detailed description is on github
 
aml_autoscript armbianEnv.txt gxl-fixup.scr s905_autoscript

Hi all,
I don't understand why you want or need to use those chain loaded u-boot blobs? 
 
The vendor u-boot bootloaders can boot mainline Linux perfectly without them. So they are not needed.
All it takes are some simple modifications of some of the Armbian u-boot scripts.
 
Just copy the attached files to the fat partition of the Armbian image after burning the image to a USB disk. 
Edit armbianEnv.txt for the right DTB (so not in extlinux.conf) and you can boot the newer Armbian images without u-boot.ext.
 
I tested it with the Armbian_23.8.1_Aml-s9xx-box_bookworm_current_6.1.50_minimal.img.xz image on the following SOC's:
S905x (GXL) S912 (GXM)  S905x2 (G12A) S922X (G12B) S905X3 (SM1) assumption: you have vendor u-boot (the one that came with the box) running on eMMC. If you don't, you can just restore the stock Android image with Amlogic USB Burning tool.
 
All needed files and a more detailed description is on github
 
aml_autoscript armbianEnv.txt gxl-fixup.scr s905_autoscript