Search the Community

Hi, I have spent several days compiling and decompiling dtb and dts files. Trying to find the better one, comparing dts files in text editors.... Finally I have found something better but yet, not the best. (I have even checked libreelec dtb files) I have also tried to check in Android TV Box by installing terminal or hardware info apps trying to find information about bluetooth. But no luck. I have seen P212 in my android tv box. At this moment, my conclusion is: 1. despite my android tv box "says" P212, i found better this dtb file meson-gxl-s905x-khadas-vim.dtb than this one: meson-gxl-s905x-p212.dtb. 2. Both have errors, but after comparing lots of dts files if I make TWO changes in meson-gxl-s905x-khadas-vim.dts file, I get managed to get working all of this: usb1, usb2, hdmi, lan, wifi, LED, poweroff, poweron with IR, audio. And DON'T work: bluetooth and poweroff with IR dts line 353 change to "disabled" (solve LED problem, so I can see led on and off) dts line 1597 change to "host" (solve that with meson-gxl-s905x-khadas-vim.dtb only one usb port works. Now the two usb ports work) I have "left" two problems with my modified meson-gxl-s905x-khadas-vim.dtb. 1. I haven't got bluetooth working (THIS IS IMPORTANT if I want to use it for home assistant for example) 2. I haven't got the chance to power off the tv box with IR remote control (THIS DOESNT MATTER) Questions, please: 1. Despite my android tv box shows me "P212" in some "play store hardware info apps".... is there any problem not to use meson-gxl-s905x-p212.dtb and use meson-gxl-s905x-khadas-vim.dtb ? 2. Is it dangerous to alter two lines in a dts file? could I damaged hardware? 3. I have also tried to connecto TWO external old usb bluetooth adapters to solve the biggest problem of my modified dtb file. Both have the "same problem". I can see my tv box with armbian firmware from my mobile phone, but my armbian tv box can NOT detect anything. I click on "search" but .... nothing. 4. I have tried also to modified a bit the dts file with these two options to get the INTERNAL bluetooth working: compatible = "brcm,bcm43438-bt"; or compatible = "realtek,rtl8723bs-bt"; (line 329, and with realtek option also add in line 324 this: enable-gpios = <0x15 0x60 0x00>;) do you know how could I find the bluetooth chipset in a rooted android tv box? I can not find any solution with compatible = "brcm,bcm43438-bt" I get this: root@aml-s9xx-box:~# dmesg | grep Bluetooth [ 9.041277] Bluetooth: Core ver 2.22 [ 9.064960] Bluetooth: HCI device and connection manager initialized [ 9.064985] Bluetooth: HCI socket layer initialized [ 9.064992] Bluetooth: L2CAP socket layer initialized [ 9.073711] Bluetooth: SCO socket layer initialized [ 9.161291] Bluetooth: HCI UART driver ver 2.3 [ 9.165629] Bluetooth: HCI UART protocol H4 registered [ 9.170024] Bluetooth: HCI UART protocol BCSP registered [ 9.174866] Bluetooth: HCI UART protocol LL registered [ 9.179849] Bluetooth: HCI UART protocol ATH3K registered [ 9.185282] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 9.191661] Bluetooth: HCI UART protocol Intel registered [ 9.197142] Bluetooth: HCI UART protocol Broadcom registered [ 9.201468] Bluetooth: HCI UART protocol QCA registered [ 9.209641] Bluetooth: HCI UART protocol AG6XX registered [ 9.251766] Bluetooth: HCI UART protocol Marvell registered [ 9.459255] Bluetooth: hci0: BCM: failed to write update baudrate (-56) [ 9.464465] Bluetooth: hci0: Failed to set baudrate [ 9.650023] Bluetooth: hci0: BCM: Read verbose config info failed (-56) [ 22.006738] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 22.006787] Bluetooth: BNEP filters: protocol multicast [ 22.011685] Bluetooth: BNEP socket layer initialized root@aml-s9xx-box:~# rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 unblocked unblocked 1 wlan phy0 unblocked unblocked It seems that the problem is "failed to write update baudrate". 3. with compatible = "realtek,rtl8723bs-bt"; I get this: root@aml-s9xx-box:~# dmesg | grep Bluetooth [ 8.236291] Bluetooth: Core ver 2.22 [ 8.251409] Bluetooth: HCI device and connection manager initialized [ 8.251434] Bluetooth: HCI socket layer initialized [ 8.251441] Bluetooth: L2CAP socket layer initialized [ 8.251483] Bluetooth: SCO socket layer initialized [ 8.312137] Bluetooth: HCI UART driver ver 2.3 [ 8.312193] Bluetooth: HCI UART protocol H4 registered [ 8.316137] Bluetooth: HCI UART protocol BCSP registered [ 8.321480] Bluetooth: HCI UART protocol LL registered [ 8.333958] Bluetooth: HCI UART protocol ATH3K registered [ 8.334060] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 8.334569] Bluetooth: HCI UART protocol Intel registered [ 8.351967] Bluetooth: HCI UART protocol Broadcom registered [ 8.364945] Bluetooth: HCI UART protocol QCA registered [ 8.370309] Bluetooth: HCI UART protocol AG6XX registered [ 8.387307] Bluetooth: HCI UART protocol Marvell registered [ 21.398088] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 21.398110] Bluetooth: BNEP filters: protocol multicast [ 21.398127] Bluetooth: BNEP socket layer initialized root@aml-s9xx-box:~# rfkill ID TYPE DEVICE SOFT HARD 0 wlan phy0 unblocked unblocked No errors, but.... no info in rfkill output Does anybody know how to go further here? Any dts/dtb expert? I can not get the internal bluetooth module working despite it is being "detected". I can not also get the two external usb adapters working because then can not find anything.... NOTE: I will upload my final DTS and DTB files but I want not to upload a not-finished file.

TV Box Status Information Template Version 1.0 ======================================= TV Box Name: Leelbox S1 (PCB marking: "A95X_DDR4" "V1_1 2160906") CPU: AMLogic S905X RAM: 1 GB DDR4 (reported: 860 MiB) - 2 x SpecTek (Micron) "PPE05-075" "F1646" Armbian build file name: Armbian_community 24.5.0-trunk.226 DTB file used: meson-gxl-s905x-p212.dtb Kernel Version: Linux 6.6.22-current-meson64 Distribution Installed: Bookworm Working Ethernet (Yes/No): Yes Max Ethernet Speed that works (100/1000): to be verified Does wifi work (Yes/No): Yes (RTL8189ETV) Does bluetooth work (Yes/No): No Does HDMI audio work (Yes/No): Not tested Comments: - also sold as ABOX-A1 according to online sources; - installation to MMC worked without issue using the dedicated script.

@Khadas Oh, you’re still alive… I’m kidding. Look, I have two boxes similar to yours, but like @uppi , when I use Armbian, my RAM shows as 800M. I tried to install Armbian to eMMC, and I bricked my box. I used the firmware you mentioned, and everything was okay. But when I tried again to install Armbian to eMMC and restore the firmware, it didn’t accept it again, only the first time. Now, I have the second box that I am experimenting on. But the confusing thing is that when I use Armbian_24.8.0_amlogic_s905l2_noble_6.6.33_server_2024.06.15.img.gz or any slightly older version, I need to use X7 5G or ipbs9505 dtb. However, if I install an older system like Armbian_5.91_Aml-s905_Debian_buster_default5.1.0.img.xz, I can use any dtb included in it, such as meson-gxl-s905x-p212 or meson-gxl-s905w-tx3-mini, and it works normally as it supports s905w and s905x. It seems to me that older versions of Armbian don't have issues with the dtb. Currently, I am trying to modify the dts to create a specific file for these boxes because my box's WiFi doesn’t work. It uses Realtek RTL8189ES. I tried to install the drivers from https://github.com/jwrdegoede/rtl8189ES_linux.git but I couldn't find any header list in any version of Armbian that works correctly. Is there a solution to the WiFi issue?

I have recently found this great project and have converted my old unused and dusty s9xx TV Boxes to ARMBIAN for use as remote NAS and other applications. I have X96 Max Plus 2 T, Beelink GT1, and 2x Beelink MiniMXIII II (total of 4 boxes). For the Beelink MiniMXIII II I used the meson-gxl-s905x-p212.dtb out of the box and it works great (100Mbit Ethernet and WIFI) For the X96 Max Plus I had to go to https://github.com/ophub/amlogic-s9xxx-armbian/releases and extract and use the meson-sm1-x96-max-plus.dtb file (Gbit Ethernet works but WIFI doesn't) For the Beelink GT1 I again extract and used (from https://github.com/ophub/amlogic-s9xxx-armbian/releases) the meson-sm1-beelink-gt1.dtb and it works great (Gbit Ethernet and WIFI) The problem is that every time I upgrade the armbian base firmware files when there is a new release (apt upgrade) it overwrites the /boot/dtb/amlogic folder and deletes the old files including the above X96 and GT1 dtb files which breaks my boxes. How can this be avoided? Can these dtb files be included in the official release? Does anyone have a working dtb files for the X96 Max Plus (Ethernet RTL8211F and WIFI AM7256)?