Got X96 max+ (2+16G) working with LAN+WIFI but still some confused points

[dinhchinh82]

@ophub I've tried your latest build for S905X2 (2G+16G, Realtek card), and got both ethernet and wifi working from USB after using the dtb file from balbes150 (5.7.8)
Armbian_22.02.0_Aml_s905x3_focal_5.4.175_2022.01.30.0137.img.gz

Here is the detail log:
http://ix.io/3NXY

Here are updates board photos:

But the log related to the network adapter is showed continuously. I'm not sure how to disable this log.

By the way, I just confused that you said Realtek has no driver under Armbian but it seems working now with balbes150's dtb.
#47 (comment)
S905x3 dtb file from balbes150's image:
https://www.dropbox.com/s/d83yqv69tkjvias/meson-sm1-sei610_578.dtb?dl=0

Could you give me any suggestions for this board?

Thank you.

[dinhchinh82]

Unfortunately, after install armbian to eMMC and unplug the USB and reboot again, my S905X3 box is unable to boot:
here is the screen log:

Note:
before running install armbian to eMMC, I already replaced your original S905x3's dtb for X96-Max+ (meson-sm1-x96-max-plus.dtb) by balbes150's dtb meson-sm1-sei610_578.dtb as mentioned above.

[ophub]

flippy has added the rtl8188fu/8822cs/8189fs driver to the kernel, which is enabled by default in 5.10.91/5.4.172/5.15.14 and later kernels.

You can test the wireless network with the latest kernel.

If you use another dtb yourself, modify the dtb in the installation file armbian-install, so that it can be correct when writing emmc.

Choose the correct firmware. What you choose is the dtb of s905x3, if your box is s905x2, use your own series. I think the solid one comes with it and it can be used.

[dinhchinh82]

@ophub thank you for your quick comment.

Choose the correct firmware. What you choose is the dtb of s905x3, if your box is s905x2, use your own series. I think the solid one comes with it and it can be used.

I can make sure my box is X96 max + (2G + 16G) with S905x3 CPU.

flippy has added the rtl8188fu/8822cs/8189fs driver to the kernel, which is enabled by default in 5.10.91/5.4.172/5.15.14 and later kernels.

Yes, I found out the wifi works well with default dtb while running from USB.
By the way, there is very strange that after install to eMMC, the box is unable to boot and got the the error below EVEN with default dtb of X96 max + (index 51).

I also tried to install to eMMC using X96 max + overclock (index 52) but also got the same issue.

In summary, I just confused why the box running on USB but unable to boot after installing to eMMC.

Is there a way to burn exactly default setting of USB to eMMC without any selection of board?

Thank you.

[ophub]

amlogic-s9xxx-armbian/build-armbian/common-files/files/usr/sbin/armbian-install

Line 102 in 3a9aac5

51:X96 Max+:s905x3:meson-sm1-x96-max-plus.dtb:u-boot-x96maxplus.bin:/lib/u-boot/x96maxplus-u-boot.bin.sd.bin:/lib/u-boot/hk1box-bootloader.img:4C@2100Mhz,4GB Mem,1Gb Net

armbian-install
select 51

Mine is s905x3 but it's not the same as yours, are you sure yours is s905x3? If it is a 2G -s905x2, choose 32

amlogic-s9xxx-armbian/build-armbian/common-files/files/usr/sbin/armbian-install

Line 90 in 3a9aac5

32:X96 Max 2GB:s905x2:meson-g12a-x96-max-rmii.dtb:u-boot-x96max.bin:/lib/u-boot/x96max-u-boot.bin.sd.bin:NA:4C@1908Mhz,2GB Mem,100M Net

armbian-install
select 32

[dinhchinh82]

armbian-install
select 51

My box is S905X3 and I already selected 51 without any changes of DTB (don't use DTB from balbes150 anymore) but still got error after booting from eMMC.

I have several this box (S905X3 with 2+16G) and I can make sure there is no S905X2.

[ophub]

Yours is a 100M network？

amlogic-s9xxx-armbian/build-armbian/common-files/files/usr/sbin/armbian-install

Line 102 in 3a9aac5

51:X96 Max+:s905x3:meson-sm1-x96-max-plus.dtb:u-boot-x96maxplus.bin:/lib/u-boot/x96maxplus-u-boot.bin.sd.bin:/lib/u-boot/hk1box-bootloader.img:4C@2100Mhz,4GB Mem,1Gb Net

armbian-install: Change the dtb in line 102 to meson-sm1-x96-max-plus-100m.dtb, and then install and write emmc, which is the dtb file used when usb starts.

[dinhchinh82]

Yours is a 100M network？

I'm not sure, may be 100M network, only 2.4G wifi, no bluetooth.

[dinhchinh82]

Please check my updated photos:

[dinhchinh82]

There are several version of X96 max plus (S905X3), this guy also have same version as mine:
https://forum.freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905x3/firmware-roms-tools-ds/805518-x96-max-plus-2gb-optical-rt-8189ftv-q5x3_141-v3-1

https://androidtvbox.eu/x96-max-plus2-firmware-for-tv-box-with-s905x3-soc-20200901/
I can restore my box with the Android version from link above.

[ophub]

There are instructions on your website. yes. your box is 100M network.

CPU – Amlogic S905X3 quad-core Arm Cortex-A55 processor @ 1.9 GHz
GPU – Arm Mali-G31MP2 GPU
System Memory, Storage & Networking configurations:
2GB DDR3 / 16 GB eMMC flash + microSD card slot + 2.4 GHz WiFi (no Bluetooth), 10/100M Ethernet

amlogic-s9xxx-armbian/build-armbian/common-files/files/usr/sbin/armbian-install

Line 102 in 3a9aac5

51:X96 Max+:s905x3:meson-sm1-x96-max-plus.dtb:u-boot-x96maxplus.bin:/lib/u-boot/x96maxplus-u-boot.bin.sd.bin:/lib/u-boot/hk1box-bootloader.img:4C@2100Mhz,4GB Mem,1Gb Net

armbian-install: Change the dtb in line 102 to meson-sm1-x96-max-plus-100m.dtb, and then install and write emmc, which is the dtb file used when usb starts.

[dinhchinh82]

armbian-install: Change the dtb in line 102 to meson-sm1-x96-max-plus-100m.dtb, and then install and write emmc, which is the dtb file used when usb starts.

I'm trying again.

By the way, I just confused why do you need to add an resistor as your photo?

As before, when I used balbes150's armbian image, sometimes my X96 max plus+ unable to reboot after power outtage.

[ophub]

When the 5.10 kernel just came out, because u-boot was easily disturbed when it was booted, adding a resistor could solve this problem. At present this has been automatically resolved by u-boot reload, but this resistor no longer needs to be added.

[dinhchinh82]

When the 5.10 kernel just came out, because u-boot was easily disturbed when it was booted, adding a resistor could solve this problem. At present this has been automatically resolved by u-boot reload, but this resistor no longer needs to be added.

So if using the kernel 5.10.91/5.4.172/5.15.14 or later, there is no need to add this resistor anymore, right?

[ophub]

No need, it's been many generations since 5.10.y, now it's 5.16.y, this was a moment, about the summer of 2020.

[dinhchinh82]

@ophub I've tried the following steps and the box still could not boot from eMMC after running armbian-install:

Step 1: Burning the S905x3 images to USB
Armbian_22.02.0_Aml_s905x3_bullseye_5.15.16_2022.01.22.1251.img.gz

Step 2: Boot from USB with default dtb, the LAN is not recognized

Step 3: Edit dtb from uEnv.txt
from meson-sm1-x96-max-plus-100m.dtb to meson-sm1-sei610.dtb
then reboot

Step 4: after rebooting, the LAN is recognized

Step 5: Edit /usr/sbin/armbian-install file as below:

Step 6: Run the armbian-install

Step 7: Run "shutdown now" command, unplug power, unplug USB

Step 8: Replug power. There is no any boot/logo or terminal on screen.

So I still confused while the box running well on USB but not work on eMMC.

Please give me your suggestion if any.

Thank you so much.

[dinhchinh82]

51:X96 Max+:s905x3:meson-sm1-x96-max-plus.dtb:u-boot-x96maxplus.bin:/lib/u-boot/x96maxplus-u-boot.bin.sd.bin:/lib/u-boot/hk1box-bootloader.img:4C@2100Mhz,4GB Mem,1Gb Net

armbian-install: Change the dtb in line 102 to meson-sm1-x96-max-plus-100m.dtb, and then install and write emmc, which is the dtb file used when usb starts.

I also tried your suggestion above to use meson-sm1-x96-max-plus-100m.dtb but the box is also still unable to boot (black screen) after unplug USB and reboot:

Note:
There is strange error message here:

Please Input ID: 51
FDTFILE: [ meson-sm1-x96-max-plus-100m.dtb ]
UBOOT_OVERLOAD: [ u-boot-x96maxplus.bin ]
Error: /dev/mmcblk2: unrecognised disk label

[ophub]

You use the firmware of the 5.4 kernel and modify it to use your dtb. do not use other kernels

59:X96 Max+:s905x3:meson-sm1-sei610.dtb:u-boot-x96maxplus.bin:NA:NA:4C@2100Mhz,2g/16g,100m

[dinhchinh82]

@ophub I will try again.
By the way, how to boot from SD card?
When I tried to boot from SD card, I also got the black screen.

[dinhchinh82]

@ophub I already tried to use 5.4 kernel but still got black screen error after install to eMMC:

I also added your suggestion to the script:
59:X96 Max+:s905x3:meson-sm1-sei610.dtb:u-boot-x96maxplus.bin:NA:NA:4C@2100Mhz,2g/16g,100m

The strange error message still happend:

Please Input ID: 59
FDTFILE: [ meson-sm1-sei610.dtb ]
UBOOT_OVERLOAD: [ u-boot-x96maxplus.bin ]
Start backup default bootloader
4+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.24677 s, 17.0 MB/s
Error: /dev/mmcblk2: unrecognised disk label

[ophub]

Can you use the 5.4 kernel to write emmc?

That error can be ignored. It is a prompt to clear the current emmc data and labels. It does not affect the use. I will close this unaffected prompt when I update it later.

[dinhchinh82]

Can I use the 5.4 kernel to write emmc?

I can only use 5.4 kernel when booting from USB but after install to eMMC, the box is still unable to boot.

Here is the list of partitions before running armbian-install:

[dinhchinh82]

After install to eMMC, it is unable to boot from USB again to check whether data from eMMC is consistency or not. It's quite strange again.

As before, when I use images from balbe150, it is able to boot from SD card even after installing to eMMC.

[dinhchinh82]

This is updated screenshot when I tried to add some debug code to your armbian-install to list the latest partitions

[ophub]

After the installation is completed using armbian-install, you must unplug the usb/tf/sd card, reinsert the power supply and boot from emmc

[dinhchinh82]

After the installation is completed using armbian-install, you must unplug the usb/tf/sd card, reinsert the power supply and boot from emmc

Sure, I always unplug the usb/tf/sd card then reinsert the power supply but still no signal.

[ophub]

Is it so magical that even 5.4 cannot be written to emmc? that can only be used in usb

[dinhchinh82]

@ophub I just tried to installed your build (5.10.93) to X96 max+ (4G+32G 1Gps) using index 51 and it works well from eMMC.

Only X96 max + version 2+16 (100Mps) got issue that unable to boot from eMMC. I also very confused why it happens.

Please note that my X96 max+ (2+16, 100Mps) still can boot from eMMC if using Balbes150 image.

[dinhchinh82]

Is it so magical that even 5.4 cannot be written to emmc? that can only be used in usb

I just confused that you said S905x3 is supported in the latest kernel like 5.10.x or 5.16.x but here why you recommend 5.4 ?

[dinhchinh82]

59:X96 Max+:s905x3:meson-sm1-sei610.dtb:u-boot-x96maxplus.bin:NA:NA:4C@2100Mhz,2g/16g,100m

@ophub Can you help me to make the profile that exactly same as the profile for default USB image of X96 max +?

[ophub]

Whether it can be started is determined by two files, one is the correct dtb and the other is the correct u-boot. Because the 5.4 kernel only uses dtb, it is recommended that you test with 5.4 to determine which dtb is suitable for your box.

Which dtb and u-boot.ext file do you use in the Balbes150 firmware, you can copy and test.

[dinhchinh82]

@ophub so your u-boot is .bin file, right?

Is there a way to boot your image from micro SD card?

I used to boot Balbes150's image from micro SD card on X96 max +.

[ophub]

.bin file in the /boot directory

In the available boxes, tf/sd/usb/emmc boot is supported

[dinhchinh82]

In the available boxes, tf/sd/usb/emmc boot is supported

@ophub There is another strange point that I've tried to boot your firmware from TF card but unable to boot, only could boot from USB 3.0 port.
But the firmware from Balbes150 could boot from TF card. Please note that I always restore default Android firmware before testing any Armbian firmware.

[ophub]

It can be used from tf card, my s905x3 x96max+ box is used on tf card.

[dinhchinh82]

@ophub I'd like to give you the summary of the current test for S905X3 X96 max+ (2G+16G + 100Mbp LAN)

1. Armbian_22.02.0_Aml_s905x3_bullseye_5.4.176: default dtb (meson-sm1-x96-max-plus-100m.dtb)

• Boot from TF card: unable to boot
• Boot from USB 3.0 port: can boot and login to Armbian, LAN did not work, WIFI works
• eMMC: unable to boot

2. Armbian_22.02.0_Aml_s905x3_bullseye_5.4.176: custom dtb (meson-sm1-sei610.dtb)

• Boot from TF card: unable to boot
• Boot from USB 3.0 port: can boot and login to Armbian, LAN works, WIFI works
• eMMC: unable to boot

3. Armbian_22.02.0_Aml_s905x_bullseye_5.10.96: default dtb (meson-sm1-x96-max-plus-100m.dtb)

• Boot from TF card: unable to boot
• Boot from USB 3.0 port: can boot and login to Armbian, LAN did not work, WIFI works
• eMMC: unable to boot

4. Armbian_22.02.0_Aml_s905x_bullseye_5.10.96: custom dtb (meson-sm1-sei610.dtb)

• Boot from TF card: unable to boot
• Boot from USB 3.0 port: can boot and login to Armbian, LAN works, WIFI works
• eMMC: unable to boot

5. Armbian_20.10_Arm-64_bullseye_current_5.9.0.img.xz: default dtb (mmeson-sm1-sei610.dtb

• Boot from TF card: can boot and login to Armbian, LAN work (but sometimes not stable), WIFI works
• Boot from USB 3.0 port: unable to boot
• eMMC: can boot and login to Armbian, LAN work (but sometimes not stable), WIFI works

Please give me any other suggestions to test if any. I'd like to install the Armbian to eMMC for long time runing.
There is no problem for me to install any additional tools for debugging according to your requirement. I have some knowledge in Linux, Android, Flashing firmware etc.
Thank you.

[ophub]

dtb: /boot/uEnv.ext meson-sm1-sei610.dtb
uboot: /boot/u-boot-s905x2-s922.bin copy to u-boot.ext

[dinhchinh82]

@ophub

dtb: /boot/uEnv.ext meson-sm1-sei610.dtb uboot: /boot/u-boot-s905x2-s922.bin copy to u-boot.ext

The /boot/u-boot-s905x2-s922.bin is the old one from Balbes150 or new one from Flippy? I'm afraid that if using the old one the issue related to LAN will be occurred again even the box could boot.