Marcelo38 Posted April 8 Posted April 8 Hi Nick, I'm learning how to compile Armbian, and I tried building your H618 image. I selected bananapi during the build and it compiled successfully, but unfortunately it doesn't boot on my Transpeed TV Box with Allwinner H618. If you could share some guidance on how to compile it correctly for this device, I’d really appreciate it. I'm still learning, so any advice helps a lot. Thanks for your awesome work! Best regards, 0 Quote
Nick A Posted April 8 Posted April 8 Hi @Marcelo38 Why did you select Bananapi? There should be Transpeed in the list? In the choose board menu, you need to select "show CSC/WIP/EOS/TVB". You'll find it in the list. 0 Quote
Marcelo38 Posted April 8 Posted April 8 Nick, thank you very much for your reply. Sorry, I hadn't paid attention about Transpeed. I'll work on that tonight. Thank you again. 0 Quote
Robert Roig Santamaria Posted April 9 Posted April 9 so... I just got a Transpeed 8k618-t I hear these can be not that clean... What should I do with it? - can a clean android be installed? any summary? it's 20 pages long topic... I browsed but I am not proficient. What can one do with such a device? 0 Quote
firepower Posted April 10 Posted April 10 (edited) Here is an update for Video Acceleration Repository for v4l2request hardware video decoding (rockchip, allwinner) Does no seem to work tested on my Tanix Tx6 and Vontar H618 Edited April 10 by firepower 0 Quote
firepower Posted April 10 Posted April 10 (edited) Noticed some strange wifi setting for my Vontar H618, its asking for Tanix,Tx6s wifi firmware I am using brcmfmac4334-sdio.bin and wifi works. Quote dmesg | grep -i brcm [ 9.628089] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 [ 9.629995] brcmfmac mmc3:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.tanix,tx6s.bin failed with error -2 [ 9.630025] brcmfmac mmc3:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac4334-sdio.tanix,tx6s.bin [ 9.633241] usbcore: registered new interface driver brcmfmac [ 9.809003] brcmfmac mmc3:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.clm_blob failed with error -2 [ 9.809023] brcmfmac mmc3:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac4334-sdio.clm_blob [ 10.010696] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 10.010717] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 10.011060] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e firepower@vontar-h618:~$ dmesg | grep -i bcm [ 9.628089] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 [ 9.789382] hci_uart_bcm serial0-0: setup of GPIO device-wakeup failed: -517 [ 10.011060] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e [ 11.556673] hci_uart_bcm serial0-0: setup of GPIO device-wakeup failed: -517 [ 16.726540] hci_uart_bcm serial0-0: setup of GPIO device-wakeup failed: -517 [ 21.599112] hci_uart_bcm serial0-0: setup of GPIO device-wakeup failed: -517 Edited April 10 by firepower 0 Quote
Nick A Posted April 10 Posted April 10 That odd are you sure you didn't mix up the images? I think Tanix, tx6 image can boot on Vontar. 0 Quote
Nick A Posted April 10 Posted April 10 @Robert Roig Santamaria this is not an android forum. I can only show you how to install linux on your box. If you want to run linux on your box then write the transpeed image onto a SDcard. I use this software to write images. https://etcher.balena.io/ and you can find my custom made images here. https://github.com/NickAlilovic/build/releases/tag/20250306 0 Quote
firepower Posted April 10 Posted April 10 (edited) I deleted the build folder and built votar image a second time to make sure. same result. brcmfmac4334-sdio.tanix,tx6s.bin again was requested. just thought it strange. was trying to solve bluetooth not working and see what different dmesg give. originally compiled tanix tx6 then after compile vontar, though it may because used same build folder. that why did again with clean build. also tanix tx6 is requesting brcmfmac-ap6330-sdio.tanix,tx6s.bin /build/patch/u-boot/u-boot-h616 153-add-tanix_tx6s_axp313_defconfig.patch + model = "Tanix TX6s (axp313)"; + compatible = "tanix,tx6s", "allwinner,sun50i-h616"; 160-add-vontar-h618-defconfig.patch + model = "Vontar H618"; + compatible = "tanix,tx6s", "allwinner,sun50i-h616"; /build/patch/kernel/archive/warpme-6.12 0649-arm64-dts-allwinner-h618-add-vontar-h618-TVbox.patch + model = "Vontar H618"; + compatible = "tanix,tx6s", "allwinner,sun50i-h616"; should this be + compatible = "vontar,h618", "allwinner,sun50i-h616"; Edited April 12 by firepower 0 Quote
firepower Posted April 12 Posted April 12 (edited) I rebuild with above corrections and also changed the bluetooth GPIO pins to be same as android. Now I can see bluetooth before it was missing. Tanix-tx6s Quote + bluetooth { + compatible = "brcm,bcm43438-bt"; + clocks = <&rtc 1>; + clock-names = "lpo"; + vbat-supply = <®_dldo1>; + vddio-supply = <®_dldo1>; + device-wakeup-gpios = <&pio 6 17 1>; /* PG17 */ + host-wakeup-gpios = <&pio 6 16 6>; /* PG16 */ + shutdown-gpios = <&pio 6 19 1>; /* PG19 */ + }; Quote firepower@vontar-h618:~$ dmesg | grep -i brcm [ 9.696754] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 [ 9.697570] usbcore: registered new interface driver brcmfmac [ 9.747060] brcmfmac mmc3:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.clm_blob failed with error -2 [ 9.747092] brcmfmac mmc3:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac4334-sdio.clm_blob [ 9.985184] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 9.985207] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 9.985596] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e [ 10.123358] Bluetooth: hci0: BCM4334B0 'brcm/BCM4334B0.hcd' Patch firepower@vontar-h618:~$ dmesg | grep -i bcm [ 11.972358] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 [ 12.256575] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e [ 12.359681] Bluetooth: hci0: BCM: chip id 68 [ 12.362259] Bluetooth: hci0: BCM: features 0x0f [ 12.385717] Bluetooth: hci0: BCM4334B0 [ 12.385750] Bluetooth: hci0: BCM4334B0 (002.001.013) build 0000 [ 12.402591] Bluetooth: hci0: BCM4334B0 'brcm/BCM4334B0.hcd' Patch [ 16.940011] Bluetooth: hci0: BCM: features 0x0f [ 16.963508] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM [ 16.963534] Bluetooth: hci0: BCM4334B0 (002.001.013) build 1852 firepower@vontar-h618:~$ dmesg | grep -i blue [ 11.894134] Bluetooth: Core ver 2.22 [ 11.894664] NET: Registered PF_BLUETOOTH protocol family [ 11.894678] Bluetooth: HCI device and connection manager initialized [ 11.894705] Bluetooth: HCI socket layer initialized [ 11.894716] Bluetooth: L2CAP socket layer initialized [ 11.894744] Bluetooth: SCO socket layer initialized [ 11.992783] Bluetooth: HCI UART driver ver 2.3 [ 11.992803] Bluetooth: HCI UART protocol H4 registered [ 11.992811] Bluetooth: HCI UART protocol BCSP registered [ 11.992924] Bluetooth: HCI UART protocol LL registered [ 11.992932] Bluetooth: HCI UART protocol ATH3K registered [ 11.992995] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 11.995124] Bluetooth: HCI UART protocol Intel registered [ 11.995540] Bluetooth: HCI UART protocol Broadcom registered [ 11.995612] Bluetooth: HCI UART protocol QCA registered [ 11.995681] Bluetooth: HCI UART protocol Marvell registered [ 12.359681] Bluetooth: hci0: BCM: chip id 68 [ 12.362259] Bluetooth: hci0: BCM: features 0x0f [ 12.385717] Bluetooth: hci0: BCM4334B0 [ 12.385750] Bluetooth: hci0: BCM4334B0 (002.001.013) build 0000 [ 12.402591] Bluetooth: hci0: BCM4334B0 'brcm/BCM4334B0.hcd' Patch [ 16.259605] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.259632] Bluetooth: BNEP filters: protocol multicast [ 16.259653] Bluetooth: BNEP socket layer initialized [ 16.940011] Bluetooth: hci0: BCM: features 0x0f [ 16.963508] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM [ 16.963534] Bluetooth: hci0: BCM4334B0 (002.001.013) build 1852 [ 17.103729] Bluetooth: MGMT ver 1.23 [ 20.318158] Bluetooth: hci0: command 0x0c13 tx timeout [ 20.318154] Bluetooth: hci0: Opcode 0x0c13 failed: -110 [ 22.451494] Bluetooth: hci0: Opcode 0x0c52 failed: -110 [ 22.454827] Bluetooth: hci0: command 0x0c13 tx timeout [ 36.639198] Bluetooth: RFCOMM TTY layer initialized [ 36.639246] Bluetooth: RFCOMM socket layer initialized [ 36.639283] Bluetooth: RFCOMM ver 1.11 [ 38.668165] Bluetooth: hci0: command 0x0c13 tx timeout [ 38.668165] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 40.798169] Bluetooth: hci0: command 0x0c13 tx timeout [ 40.798169] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 42.931506] Bluetooth: hci0: command 0x0c13 tx timeout [ 42.931510] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 45.064902] Bluetooth: hci0: command 0x0c13 tx timeout [ 45.064968] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 47.198214] Bluetooth: hci0: command 0x0c13 tx timeout [ 47.198270] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 49.331554] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 49.331643] Bluetooth: hci0: command 0x0c13 tx timeout [ 51.464871] Bluetooth: hci0: command 0x0c13 tx timeout [ 51.464933] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 53.598235] Bluetooth: hci0: command 0x0c13 tx timeout [ 53.598235] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 55.731536] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 55.731618] Bluetooth: hci0: command 0x0c13 tx timeout [ 57.864877] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 57.864930] Bluetooth: hci0: command 0x0c13 tx timeout [ 59.998168] Bluetooth: hci0: command 0x0c13 tx timeout [ 59.998169] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 62.131478] Bluetooth: hci0: command 0x0c13 tx timeout [ 62.131485] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 64.264802] Bluetooth: hci0: command 0x0c13 tx timeout [ 64.264802] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 66.398134] Bluetooth: hci0: command 0x0c13 tx timeout [ 66.398134] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 68.531471] Bluetooth: hci0: command 0x0c13 tx timeout [ 68.531470] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 70.664836] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 70.664922] Bluetooth: hci0: command 0x0c13 tx timeout [ 72.798178] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 72.798261] Bluetooth: hci0: command 0x0c13 tx timeout [ 74.931483] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 74.931492] Bluetooth: hci0: command 0x0c13 tx timeout [ 202.725147] Bluetooth: hci0: command 0x0c13 tx timeout [ 202.725206] Bluetooth: hci0: Opcode 0x2005 failed: -110 [ 204.858521] Bluetooth: hci0: command 0x0c13 tx timeout [ 204.858518] Bluetooth: hci0: Opcode 0x200b failed: -110 [ 239.632564] Bluetooth: hci0: Opcode 0x2005 failed: -110 [ 239.632566] Bluetooth: hci0: command 0x0c13 tx timeout [ 241.765866] Bluetooth: hci0: command 0x0c13 tx timeout [ 241.765925] Bluetooth: hci0: Opcode 0x200b failed: -110 [ 485.612209] Bluetooth: hci0: command 0x0c13 tx timeout [ 485.612209] Bluetooth: hci0: Opcode 0x2005 failed: -110 [ 487.745592] Bluetooth: hci0: command 0x0c13 tx timeout [ 487.745657] Bluetooth: hci0: Opcode 0x200b failed: -110 [ 1393.356783] Bluetooth: hci0: Opcode 0x0c03 failed: -110 firepower@vontar-h618:~$ Quote firepower@tanix-tx6s-axp313:~$ dmesg | grep -i brcm [ 13.561402] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac-ap6330-sdio for chip BCM4330/4 [ 13.562569] usbcore: registered new interface driver brcmfmac [ 13.723011] brcmfmac mmc3:0001:1: Direct firmware load for brcm/brcmfmac-ap6330-sdio.clm_blob failed with error -2 [ 13.723044] brcmfmac mmc3:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac-ap6330-sdio.clm_blob [ 14.037452] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 14.037489] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 14.038131] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Jan 23 2013 17:46:35 version 5.90.195.114 FWID 01-cafa6b3e [ 14.083162] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 184 [ 14.083202] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 188 [ 14.083209] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 192 [ 14.083217] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 196 [ 14.083224] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 200 [ 14.083231] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 204 [ 14.083238] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 208 [ 14.083245] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 212 [ 14.083252] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 216 [ 14.123903] Bluetooth: hci0: BCM4330B1 'brcm/BCM4330B1.hcd' Patch [ 26.639000] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred [ 26.639074] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5 firepower@tanix-tx6s-axp313:~$ dmesg | grep -i bcm [ 13.561402] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac-ap6330-sdio for chip BCM4330/4 [ 14.038131] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Jan 23 2013 17:46:35 version 5.90.195.114 FWID 01-cafa6b3e [ 14.057779] Bluetooth: hci0: BCM: chip id 62 [ 14.062558] Bluetooth: hci0: BCM: features 0x0f [ 14.088349] Bluetooth: hci0: BCM4330B1 [ 14.088411] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000 [ 14.123903] Bluetooth: hci0: BCM4330B1 'brcm/BCM4330B1.hcd' Patch [ 17.977607] Bluetooth: hci0: BCM: features 0x0f [ 18.001225] Bluetooth: hci0: BCM4330B1 [ 18.001259] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000 firepower@tanix-tx6s-axp313:~$ dmesg | grep -i blue [ 13.459074] Bluetooth: Core ver 2.22 [ 13.459297] NET: Registered PF_BLUETOOTH protocol family [ 13.459325] Bluetooth: HCI device and connection manager initialized [ 13.459359] Bluetooth: HCI socket layer initialized [ 13.459374] Bluetooth: L2CAP socket layer initialized [ 13.459411] Bluetooth: SCO socket layer initialized [ 13.700931] Bluetooth: HCI UART driver ver 2.3 [ 13.700971] Bluetooth: HCI UART protocol H4 registered [ 13.700978] Bluetooth: HCI UART protocol BCSP registered [ 13.701134] Bluetooth: HCI UART protocol LL registered [ 13.701148] Bluetooth: HCI UART protocol ATH3K registered [ 13.701244] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 13.701765] Bluetooth: HCI UART protocol Intel registered [ 13.702404] Bluetooth: HCI UART protocol Broadcom registered [ 13.702533] Bluetooth: HCI UART protocol QCA registered [ 13.702616] Bluetooth: HCI UART protocol Marvell registered [ 14.057779] Bluetooth: hci0: BCM: chip id 62 [ 14.062558] Bluetooth: hci0: BCM: features 0x0f [ 14.088349] Bluetooth: hci0: BCM4330B1 [ 14.088411] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000 [ 14.123903] Bluetooth: hci0: BCM4330B1 'brcm/BCM4330B1.hcd' Patch [ 17.977607] Bluetooth: hci0: BCM: features 0x0f [ 18.001225] Bluetooth: hci0: BCM4330B1 [ 18.001259] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000 [ 18.054441] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.054472] Bluetooth: BNEP filters: protocol multicast [ 18.054496] Bluetooth: BNEP socket layer initialized [ 18.152593] Bluetooth: MGMT ver 1.23 [ 36.126584] Bluetooth: RFCOMM TTY layer initialized [ 36.126637] Bluetooth: RFCOMM socket layer initialized [ 36.126665] Bluetooth: RFCOMM ver 1.11 firepower@tanix-tx6s-axp313:~$ Edited April 14 by firepower 0 Quote
firepower Posted April 13 Posted April 13 (edited) Quote firepower@vontar-h618:~$ sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Sun 2025-04-13 13:11:25 +07; 9min ago Docs: man:bluetoothd(8) Main PID: 606 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4598) Memory: 3.3M (peak: 3.6M) CPU: 231ms CGroup: /system.slice/bluetooth.service └─606 /usr/libexec/bluetooth/bluetoothd Apr 13 13:12:21 vontar-h618 bluetoothd[606]: Failed to add UUID: Authentication Failed (0x05) Apr 13 13:12:23 vontar-h618 bluetoothd[606]: Failed to add UUID: Authentication Failed (0x05) Apr 13 13:12:25 vontar-h618 bluetoothd[606]: Failed to add UUID: Authentication Failed (0x05) Apr 13 13:12:27 vontar-h618 bluetoothd[606]: Failed to add UUID: Authentication Failed (0x05) Apr 13 13:12:29 vontar-h618 bluetoothd[606]: Failed to add UUID: Authentication Failed (0x05) Apr 13 13:12:32 vontar-h618 bluetoothd[606]: Failed to add UUID: Authentication Failed (0x05) Apr 13 13:12:34 vontar-h618 bluetoothd[606]: Failed to add UUID: Authentication Failed (0x05) Apr 13 13:13:13 vontar-h618 bluetoothd[606]: Failed to set mode: Authentication Failed (0x05) Apr 13 13:13:15 vontar-h618 bluetoothd[606]: Failed to set mode: Authentication Failed (0x05) Apr 13 13:13:18 vontar-h618 bluetoothd[606]: Failed to set mode: Authentication Failed (0x05) Quote firepower@tanix-tx6s-axp313:~$ sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Sun 2025-04-13 14:49:25 +07; 3min 47s ago Docs: man:bluetoothd(8) Main PID: 605 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4598) Memory: 3.2M (peak: 3.6M) CPU: 354ms CGroup: /system.slice/bluetooth.service └─605 /usr/libexec/bluetooth/bluetoothd Apr 13 14:51:15 tanix-tx6s-axp313 bluetoothd[605]: Endpoint unregistered: sender=:1.45 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Apr 13 14:51:15 tanix-tx6s-axp313 bluetoothd[605]: Endpoint unregistered: sender=:1.45 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Apr 13 14:51:19 tanix-tx6s-axp313 bluetoothd[605]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/sbc Apr 13 14:51:19 tanix-tx6s-axp313 bluetoothd[605]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/sbc Apr 13 14:51:19 tanix-tx6s-axp313 bluetoothd[605]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Apr 13 14:51:19 tanix-tx6s-axp313 bluetoothd[605]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Apr 13 14:51:19 tanix-tx6s-axp313 bluetoothd[605]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Apr 13 14:51:19 tanix-tx6s-axp313 bluetoothd[605]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Apr 13 14:51:19 tanix-tx6s-axp313 bluetoothd[605]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Apr 13 14:51:19 tanix-tx6s-axp313 bluetoothd[605]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/sbc_xq_552 firepower@tanix-tx6s-axp313:~$ Bluetooth app opens and scans but does not find any devices. Edited April 14 by firepower 0 Quote
firepower Posted April 15 Posted April 15 (edited) after many day of building and test I have found My TV Box Tanix Tx6 which I use build/patch/kernel/archive/warpme-6.12/0646-arm64-dts-allwinner-h616-add-Tanix-TX6s-axp313-TVbox.patch My TV Box Vontar H618 which I use build/patch/kernel/archive/warpme-6.12/0649-arm64-dts-allwinner-h618-add-vontar-h618-TVbox.patch the Android DTS use different GPIO for bluetooth hex gpio 10 11 13 or dec gpio 16 17 19 (same as transpeed) Quote bt { compatible = "allwinner,sunxi-bt"; clocks = <0x1b>; bt_power; bt_io_regulator; bt_rst_n = <0x53 0x06 0x13 0x01 0xffffffff 0xffffffff 0x00>; status = "okay"; linux,phandle = <0x179>; phandle = <0x179>; }; btlpm { compatible = "allwinner,sunxi-btlpm"; uart_index = <0x01>; bt_wake = <0x53 0x06 0x11 0x01 0xffffffff 0xffffffff 0x01>; bt_hostwake = <0x53 0x06 0x10 0x06 0xffffffff 0xffffffff 0x00>; status = "okay"; linux,phandle = <0x17a>; phandle = <0x17a>; }; but warmme patch uses gpio 6 5 4 Quote &uart1 { pinctrl-names = "default"; pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>; uart-has-rtscts; status = "okay"; bluetooth { compatible = "brcm,bcm43438-bt"; clocks = <&rtc 1>; clock-names = "lpo"; vbat-supply = <®_dldo1>; vddio-supply = <®_dldo1>; device-wakeup-gpios = <&r_pio 0 6 GPIO_ACTIVE_HIGH>; /* PL6 */ host-wakeup-gpios = <&r_pio 0 5 GPIO_ACTIVE_HIGH>; /* PL5 */ shutdown-gpios = <&r_pio 0 4 GPIO_ACTIVE_HIGH>; /* PL4 */ }; }; for my Tanix Tx6s and Vontar H618 I need to edit to Quote &uart1 { pinctrl-names = "default"; pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>; uart-has-rtscts; status = "okay"; bluetooth { compatible = "brcm,bcm43438-bt"; clocks = <&rtc 1>; clock-names = "lpo"; vbat-supply = <®_dldo1>; vddio-supply = <®_dldo1>; device-wakeup-gpios = <&r_pio 6 17 GPIO_ACTIVE_HIGH>; /* PG17 */ host-wakeup-gpios = <&r_pio 6 16 GPIO_ACTIVE_HIGH>; /* PG16 */ shutdown-gpios = <&r_pio 6 19 GPIO_ACTIVE_HIGH>; /* PG19 */ }; }; Note: &r_pio is gpio connected to CPU not sure if it makes a difference to use &pio Edited April 16 by firepower 0 Quote
firepower Posted April 15 Posted April 15 (edited) Tanix Tx6 use Wifi & Bluetooth uses SP6330-X. with 26MHz xtal. for Wifi the brcmfmac-ap6330-sdio firmware works for 26Mhz xtal for bluetooth the BCM4330B1.hcd is used but it is for 37.4MHz xtal I have tried linking to .hcd files that contain 26MHz , but still bluetooth does not work. Good News I have found BCM4330B1.hcd with 26Mhz Xtal Bluetooth is detecting and connecting devices. Quote dmesg|grep -i bcm [ 11.435283] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac-ap6330-sdio for chip BCM4330/4 [ 11.709166] Bluetooth: hci0: BCM: chip id 62 [ 11.717154] Bluetooth: hci0: BCM: features 0x0f [ 11.740846] Bluetooth: hci0: BCM4330B1 [ 11.740880] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000 [ 11.756021] Bluetooth: hci0: BCM4330B1 'brcm/BCM4330B1.hcd' Patch [ 11.965075] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Jan 23 2013 17:46:35 version 5.90.195.114 FWID 01-cafa6b3e [ 17.532682] Bluetooth: hci0: BCM: features 0x0f [ 17.556357] Bluetooth: hci0: Foxconn-T77H36000 BCM4330B2 0876 26MHz BT4.0 Class 1 [ 17.556392] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0991 BCM4330B1.hcd Edited April 16 by firepower 0 Quote
firepower Posted April 16 Posted April 16 (edited) here is the complete brcm wifi BT firmware I found it may have firware useful for other wifi BT devices. brcm.zip Edited April 16 by firepower 0 Quote
firepower Posted April 17 Posted April 17 @Nick A here are the files for Vontar.h618 bluetooth BCM4334B0.hcd.Murata BCM4334B0.hcd.Samsung 0 Quote
Rodrigo Campos Posted April 21 Posted April 21 Thanks @firepower, I have an Transpeed M98 with the same SP6330-X wifi-bluetooth chip and had the same problem as you had described. Now I just replace my original BCM4330B1.hcd by yours and now the Bluetooth worked like a charm. Now The only problem I still need to found a fix is my Ram memory that I just could use the half of 4GB that the box have. 1 Quote
dale Posted April 28 Posted April 28 @firepowercan you let me know what is difference between Murata and Samsung ones? I don't know what is mine and I tried both but nothing is working for me. 0 Quote
Alex2jf Posted April 28 Posted April 28 @firepower I tried to replace the original BCM4334B0.hcd file with these two and bluetooth did not work with either file on my Vontar H618 0 Quote
Nick A Posted April 30 Posted April 30 @Rodrigo Campos have you tried my latest images? There’s a new patch for dram detection. 0 Quote
Alfi ciio Posted Saturday at 03:33 PM Posted Saturday at 03:33 PM (edited) I have a Vontar 4GB/64GB. Using Nick's latest image, I can install to emmc, but fail to install Home Assistant supervised. Using these steps: https://github.com/home-assistant/supervised-installer, I can install docker, but get error when installing homeassistant-supervised.deb, it said can not start docker service. Any help pls? Thanks Edited Saturday at 03:34 PM by Alfi ciio 0 Quote
kvvvp Posted yesterday at 06:46 AM Posted yesterday at 06:46 AM Alfi ciio, I have a Transpeed 8K 4/64Gb and I also use Nick A builds. Docker is installed and running on the 6.9.12 kernel, and it is installed on the 6.12.11 kernel, but it issues an error when running. Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xeu docker.service" for details. 0 Quote
Nick A Posted 16 hours ago Posted 16 hours ago Need more debug info. Try running “sudo dockerd --debug” 0 Quote
firepower Posted 13 hours ago Posted 13 hours ago @dale murata is armbian firmware, samsung is from vontar android firmware, if you open .hcd with text editor you see text of murata or samsung, I just use that as reference for each file. 1 Quote
firepower Posted 13 hours ago Posted 13 hours ago (edited) I am including the Tanix tx6s and Vontar h618 complete android firmware for wifi/bluetooth. I previously tried using some of the files with no success but found the complete firmware save to a usb drive. I think android is using different file names to what is usually expected to work. hopefully its useful to get Bluetooth working in armbian. Tanix Tx6s Wifi/BT: SP6330-X0 Clock: 26.0 MHz Tanix tx6s android firmware also includes fdt (dtb) file Vontar H618 Wifi/BT: HK6334Q Clock: 37.4 MHz Vontar H618 android firmware I no longer have working android to boot into. If someone can copy the android fdt (dtb) file from their vontar h618 box and upload it. i would be very grateful. here is how you can do it , i did this for tanix tx6s get android fdt (dtb) think this is the android path to the file /sys/firmware/fdt Edited 1 hour ago by firepower 0 Quote
svyatoslav Posted 7 hours ago Posted 7 hours ago (edited) Hello. I have a z8pro TV box, installed an image from x98 but WiFi sv6256 doesn't work, no sound. Specifications: System: Android TV 12.0 Processor: Alwinner H618 Graphics processor: Mali-G31 RAM: 4GB Built-in storage: 32GB Connectors: HDMI 2.1, USB 2.0, USB 2.0, LAN 100Mbit, S/PDIF, AV, MicroSD Auto frame rate: Yes Network interfaces: Wi-Fi 2.4/5GHz, Bluetooth, LAN 100Mbit Maybe someone has already assembled an arbian assembly for this board? Please share. Edited 6 hours ago by svyatoslav 0 Quote
firepower Posted 2 hours ago Posted 2 hours ago (edited) Broadcom brcmsmac(PCIe) and brcmfmac(SDIO/USB) drivers https://wireless.docs.kernel.org/en/latest/en/users/drivers/brcm80211.html Broadcom brcmfmac driver Support for both 32 and 64 bit Linux kernels Firmware installation Current For SDIO driver you need to copy the nvram for your system and place it in /lib/firmware/brcm. The nvram file name depends on the chip you have. The kernel log will tell you the exact file name. For the USB driver no nvram file is strictly needed: in fact, the driver only loads the firmware blob and does not look for an nvram text file. However, the nvram parameters are still required and they are already part of the firmware blob. This is a TRX file which contains the nvram parameters as a sequence of zero-terminated plain text strings, appended at the end of the last section. For an example of how to modify/add nvram parameters for USB devices, see this post: https://elimo.io/2-4ghz-coexistence-reverse-engineering-broadcom-chips-to-enable-packet-traffic-arbitration/ The firmware files are located in the linux-firmware repository and can be copied as is to /lib/firmware/brcm. SDIO chip on older kernels (before 3.13) In kernel priors to v3.13 the SDIO driver used generic firmware names. Below are the instruction Use the nvram file installed in your system and copy it to /lib/firmware/brcm/brcmfmac-sdio.txt The firmware can be found in the linux-firmware repository. For 4329: cp brcm/brcmfmac4329.bin /lib/firmware/brcm/brcmfmac-sdio.bin For 4330: cp brcm/brcmfmac4330.bin /lib/firmware/brcm/brcmfmac-sdio.bin Alternatively, when not available the Android version can be used as well: git clone https://android.googlesource.com/platform/hardware/broadcom/wlan firmware files: bcmdhd/firmware/bcm4329/fw_bcm4329.bin bcmdhd/firmware/bcm4330/fw_bcm4330_b2.bin NVRAM from EFI Some new devices are storing the nvram which is needed in addition to the firmware by the driver in an EFI variable and the Windows driver can access it (this file should be optional in the case of PCIe devices). Currently brcmfmac does not support this automatically. First mount the efi vars into sysfs: mount -t efivarfs none /sys/firmware/efi/efivars The content of the nvram is in this file: /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 Copy this file where brcmfmac expects the nvram, for example: cat /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 > /lib/firmware/brcm/brcmfmac43241b4-sdio.txt Edited 1 hour ago by firepower 0 Quote
kvvvp Posted 1 hour ago Posted 1 hour ago Цитата 14 часов назад, Nick A сказал: Need more debug info. Try running “sudo dockerd --debug” Скрытый текст INFO[2025-05-06T08:29:58.675493232+04:00] Starting up DEBU[2025-05-06T08:29:58.678103637+04:00] Listener created for HTTP on unix (/var/run/docker.sock) INFO[2025-05-06T08:29:58.678771843+04:00] OTEL tracing is not configured, using no-op tracer provider INFO[2025-05-06T08:29:58.679190133+04:00] detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf DEBU[2025-05-06T08:29:58.720519998+04:00] Golang's threads limit set to 27540 DEBU[2025-05-06T08:29:58.721581327+04:00] metrics API listening on /var/run/docker/metrics.sock INFO[2025-05-06T08:29:58.721604577+04:00] Creating a containerd client address=/run/containerd/containerd.sock timeout=1m0s DEBU[2025-05-06T08:29:58.743172651+04:00] Using default logging driver json-file DEBU[2025-05-06T08:29:58.743614858+04:00] processing event stream module=libcontainerd namespace=plugins.moby DEBU[2025-05-06T08:29:58.743969856+04:00] No quota support for local volumes in /var/lib/docker/volumes: Filesystem does not support, or has not enabled quotas DEBU[2025-05-06T08:29:59.042884413+04:00] [graphdriver] priority list: [overlay2 fuse-overlayfs btrfs zfs vfs] DEBU[2025-05-06T08:30:02.241026957+04:00] successfully detected metacopy status storage-driver=overlay2 usingMetacopy=false DEBU[2025-05-06T08:30:02.564520057+04:00] backingFs=extfs, projectQuotaSupported=false, usingMetacopy=false, indexOff="index=off,", userxattr="" storage-driver=overlay2 INFO[2025-05-06T08:30:02.564659015+04:00] [graphdriver] using prior storage driver: overlay2 DEBU[2025-05-06T08:30:02.564731223+04:00] Initialized graph driver overlay2 DEBU[2025-05-06T08:30:02.565377345+04:00] Max Concurrent Downloads: 3 DEBU[2025-05-06T08:30:02.565427095+04:00] Max Concurrent Uploads: 5 DEBU[2025-05-06T08:30:02.565461387+04:00] Max Download Attempts: 5 INFO[2025-05-06T08:30:02.565619969+04:00] Loading containers: start. DEBU[2025-05-06T08:30:02.565859010+04:00] Option DefaultDriver: bridge DEBU[2025-05-06T08:30:02.565905468+04:00] Option DefaultNetwork: bridge DEBU[2025-05-06T08:30:02.565942551+04:00] Network Control Plane MTU: 1500 DEBU[2025-05-06T08:30:02.566647507+04:00] processing event stream module=libcontainerd namespace=moby DEBU[2025-05-06T08:30:02.566750631+04:00] Modules already loaded modules="[nf_conntrack nf_conntrack_netlink]" DEBU[2025-05-06T08:30:02.575843592+04:00] /usr/sbin/iptables, [--wait -t filter -C FORWARD -j DOCKER-ISOLATION] DEBU[2025-05-06T08:30:02.582633604+04:00] /usr/sbin/iptables, [--wait -t nat -D PREROUTING -m addrtype --dst-type LOCAL -j DOCKER] DEBU[2025-05-06T08:30:02.589300700+04:00] /usr/sbin/iptables, [--wait -t nat -D OUTPUT -m addrtype --dst-type LOCAL ! --dst 127.0.0.0/8 -j DOCKER] DEBU[2025-05-06T08:30:02.595466965+04:00] /usr/sbin/iptables, [--wait -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER] DEBU[2025-05-06T08:30:02.601738230+04:00] /usr/sbin/iptables, [--wait -t nat -D PREROUTING] DEBU[2025-05-06T08:30:02.607021999+04:00] /usr/sbin/iptables, [--wait -t nat -D OUTPUT] DEBU[2025-05-06T08:30:02.615129464+04:00] /usr/sbin/iptables, [--wait -t nat -F DOCKER] DEBU[2025-05-06T08:30:02.620643356+04:00] /usr/sbin/iptables, [--wait -t nat -X DOCKER] DEBU[2025-05-06T08:30:02.626853663+04:00] /usr/sbin/iptables, [--wait -t filter -F DOCKER] DEBU[2025-05-06T08:30:02.633524926+04:00] /usr/sbin/iptables, [--wait -t filter -X DOCKER] DEBU[2025-05-06T08:30:02.639211151+04:00] /usr/sbin/iptables, [--wait -t filter -F DOCKER-FORWARD] DEBU[2025-05-06T08:30:02.645141167+04:00] /usr/sbin/iptables, [--wait -t filter -X DOCKER-FORWARD] DEBU[2025-05-06T08:30:02.651299724+04:00] /usr/sbin/iptables, [--wait -t filter -F DOCKER-BRIDGE] DEBU[2025-05-06T08:30:02.662217427+04:00] /usr/sbin/iptables, [--wait -t filter -X DOCKER-BRIDGE] DEBU[2025-05-06T08:30:02.671793177+04:00] /usr/sbin/iptables, [--wait -t filter -F DOCKER-CT] DEBU[2025-05-06T08:30:02.677570943+04:00] /usr/sbin/iptables, [--wait -t filter -X DOCKER-CT] DEBU[2025-05-06T08:30:02.684963120+04:00] /usr/sbin/iptables, [--wait -t filter -F DOCKER-ISOLATION-STAGE-1] DEBU[2025-05-06T08:30:02.692968627+04:00] /usr/sbin/iptables, [--wait -t filter -X DOCKER-ISOLATION-STAGE-1] DEBU[2025-05-06T08:30:02.701694214+04:00] /usr/sbin/iptables, [--wait -t filter -F DOCKER-ISOLATION-STAGE-2] DEBU[2025-05-06T08:30:02.710939091+04:00] /usr/sbin/iptables, [--wait -t filter -X DOCKER-ISOLATION-STAGE-2] DEBU[2025-05-06T08:30:02.717652353+04:00] /usr/sbin/iptables, [--wait -t filter -F DOCKER-ISOLATION] DEBU[2025-05-06T08:30:02.722722498+04:00] /usr/sbin/iptables, [--wait -t filter -X DOCKER-ISOLATION] DEBU[2025-05-06T08:30:02.728741930+04:00] /usr/sbin/iptables, [--wait -t nat -n -L DOCKER] DEBU[2025-05-06T08:30:02.734592572+04:00] /usr/sbin/iptables, [--wait -t nat -N DOCKER] DEBU[2025-05-06T08:30:02.758826925+04:00] daemon configured with a 15 seconds minimum shutdown timeout DEBU[2025-05-06T08:30:02.758953841+04:00] start clean shutdown of all containers with a 15 seconds timeout... INFO[2025-05-06T08:30:02.762814408+04:00] stopping event stream following graceful shutdown error="<nil>" module=libcontainerd namespace=moby DEBU[2025-05-06T08:30:02.763127073+04:00] Cleaning up old mountid : start. DEBU[2025-05-06T08:30:02.764481276+04:00] Cleaning up old mountid : done. failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to register "bridge" driver: failed to create NAT chain DOCKER: iptables failed: iptables --wait -t nat -N DOCKER: iptables v1.8.9 (nf_tables): TABLE_ADD failed (Operation not supported): table nat (exit status 4) 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.