Jump to content

How to install armbian in h618?

alienxz77b

By alienxz77b
in Allwinner CPU Boxes

 Share

Recommended Posts

Nick A

Nick A

Posted
Posted (edited)

Looking at the patch again... I don't think adding cooling will solve the issue. Also the H616 dtsi already has "#cooling-cells = <2>;".

 

https://lore.kernel.org/linux-arm-kernel/20230821-ths-h616-v2-0-cda60d556798@somainline.org/T/

 

Right now I'm using the 6.10.10 kernel. I'll update to 6.10.14 and make a new kernel config.

 

Your board is using an external crystal for it's clock. Can I see your dmesg log? Maybe you just need bluetooth firmware.

Edited by Nick A
0
Link to comment
Share on other sites
firepower

firepower

Posted
Posted 
firepower@tanix-tx6s-axp313:~$ dmesg | grep -i bluetooth
[   11.946450] Bluetooth: Core ver 2.22
[   11.946611] NET: Registered PF_BLUETOOTH protocol family
[   11.946621] Bluetooth: HCI device and connection manager initialized
[   11.946642] Bluetooth: HCI socket layer initialized
[   11.946650] Bluetooth: L2CAP socket layer initialized
[   11.946681] Bluetooth: SCO socket layer initialized
[   12.099653] Bluetooth: HCI UART driver ver 2.3
[   12.099681] Bluetooth: HCI UART protocol H4 registered
[   12.099686] Bluetooth: HCI UART protocol BCSP registered
[   12.099793] Bluetooth: HCI UART protocol LL registered
[   12.099802] Bluetooth: HCI UART protocol ATH3K registered
[   12.099840] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   12.100025] Bluetooth: HCI UART protocol Intel registered
[   12.100275] Bluetooth: HCI UART protocol Broadcom registered
[   12.100338] Bluetooth: HCI UART protocol QCA registered
[   12.100344] Bluetooth: HCI UART protocol AG6XX registered
[   12.100373] Bluetooth: HCI UART protocol Marvell registered
[   41.324215] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   41.324250] Bluetooth: BNEP filters: protocol multicast
[   41.324272] Bluetooth: BNEP socket layer initialized

 

0
Link to comment
Share on other sites
MMorales

MMorales

Posted
Posted
Quote

root@transpeed-8k618-t:~# dmesg | grep -i bluetooth
[    5.478537] Bluetooth: Core ver 2.22
[    5.478627] NET: Registered PF_BLUETOOTH protocol family
[    5.478632] Bluetooth: HCI device and connection manager initialized
[    5.478650] Bluetooth: HCI socket layer initialized
[    5.478658] Bluetooth: L2CAP socket layer initialized
[    5.478672] Bluetooth: SCO socket layer initialized
[    5.531438] Bluetooth: HCI UART driver ver 2.3
[    5.531464] Bluetooth: HCI UART protocol H4 registered
[    5.531469] Bluetooth: HCI UART protocol BCSP registered
[    5.531553] Bluetooth: HCI UART protocol LL registered
[    5.531558] Bluetooth: HCI UART protocol ATH3K registered
[    5.531591] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    5.531762] Bluetooth: HCI UART protocol Intel registered
[    5.531870] Bluetooth: HCI UART protocol Broadcom registered
[    5.531906] Bluetooth: HCI UART protocol QCA registered
[    5.531911] Bluetooth: HCI UART protocol AG6XX registered
[    5.531941] Bluetooth: HCI UART protocol Marvell registered
[    5.893268] Bluetooth: hci0: BCM: chip id 68
[    5.895711] Bluetooth: hci0: BCM: features 0x0f
[    5.919060] Bluetooth: hci0: BCM4334B0
[    5.919078] Bluetooth: hci0: BCM4334B0 (002.001.013) build 0000
[    5.920257] Bluetooth: hci0: BCM4334B0 'brcm/BCM4334B0.hcd' Patch
[   10.433680] Bluetooth: hci0: BCM: features 0x0f
[   10.457165] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM
[   10.457192] Bluetooth: hci0: BCM4334B0 (002.001.013) build 1852
[   12.003621] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   12.003657] Bluetooth: BNEP filters: protocol multicast
[   12.003677] Bluetooth: BNEP socket layer initialized
[   12.010332] Bluetooth: MGMT ver 1.22
[   14.116580] Bluetooth: hci0: Opcode 0x0c56 failed: -110
[   14.116666] Bluetooth: hci0: command 0x0c56 tx timeout
[   16.132606] Bluetooth: hci0: Opcode 0x0c52 failed: -110
[   16.132693] Bluetooth: hci0: command 0x0c56 tx timeout
[   18.148604] Bluetooth: hci0: command 0x0c56 tx timeout
[   18.152608] Bluetooth: hci0: Opcode 0x0c52 failed: -110
[   20.168709] Bluetooth: hci0: Opcode 0x0c52 failed: -110
[   20.168799] Bluetooth: hci0: command 0x0c56 tx timeout
[   22.180702] Bluetooth: hci0: command 0x0c56 tx timeout
[   22.180757] Bluetooth: hci0: Opcode 0x0c13 failed: -110
[   24.196740] Bluetooth: hci0: command 0x0c56 tx timeout
[   24.196920] Bluetooth: hci0: Opcode 0x0c52 failed: -110
[   26.298259] Bluetooth: hci0: command 0x0c56 tx timeout
[   26.298257] Bluetooth: hci0: Opcode 0x0c13 failed: -110
root@transpeed-8k618-t:~# bluetoothctl
Agent registered
[CHG] Controller 43:34:B0:00:1F:AC Powered: yes
[CHG] Controller 43:34:B0:00:1F:AC Pairable: yes
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# show
Controller 43:34:B0:00:1F:AC (public)
    Name: transpeed-8k618-t
    Alias: transpeed-8k618-t
    Class: 0x00000000
    Powered: yes
    Discoverable: no
    DiscoverableTimeout: 0x000000b4
    Pairable: yes
    UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
    UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
    UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
    Modalias: usb:v1D6Bp0246d0542
    Discovering: no
    Roles: central
    Roles: peripheral
Advertising Features:
    ActiveInstances: 0x00 (0)
    SupportedInstances: 0x05 (5)
    SupportedIncludes: tx-power
    SupportedIncludes: appearance
    SupportedIncludes: local-name

 

0
Link to comment
Share on other sites
Nick A

Nick A

Posted
Posted (edited)

firepower.. I don't even see a HCI interface detected at all. Maybe your dts needs some work. 

 

MMorales your dmesg looks like a firmware issue.. extract the firmware from your original android. 

Edited by Nick A
0
Link to comment
Share on other sites
Nick A

Nick A

Posted
Posted (edited)

I forget exactly where the firmware is... I think it's in /vendor/etc/firmware. Search your android partitions for a file called BCM4334B0.hcd. You can also try your original android wifi firmware too. 

 

You can use the X-plorer app. My box comes with it.  

Edited by Nick A
0
Link to comment
Share on other sites
rafman

rafman

Posted
Posted
23 minutes ago, Nick A said:

MMorales your dmesg looks like a firmware issue.. extract the firmware from your original android. 

 

I have the same output as MMorales on 6.7.12 but ..( probably this is valid and for 6.10.x)

 

 kernel asks for an additional firmware blob file:  (but i can't find it)   --> (probably  is filtered from dmesg of  MMorales)

[    6.169613] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.clm_blob failed with error -2

 

 

I Formated my emmc on my box but i found a firmware however there are many variations of such boxes

Additionally:

Super partition is dynamic partition not an ext4

i Have convert Super.fex with simg2img to raw image  but i can not mount it... 

 

We need A live box.

 

@MMorales

Do you have any working Android firmware for your box ?

 

0
Link to comment
Share on other sites
rafman

rafman

Posted
Posted
Just now, MMorales said:

@rafman its your bluetooth working ? can you share the file ?

 

I will check it ... now i am in progress

 

Download the files Here:  https://easyupload.io/wab7ki

 

 

 

Firmware Contains: ( For transpeed 8k HK6334Q these files are suspected)

 

bcm4334.hcd    

fw_bcm43341b0_ag.bin  

fw_bcm43341b0_ag_apsta.bin

fw_bcm43341b0_ag_p2p.bin

regulatory.db

regulatory.db.p7s

 

 

 

 

 

 

 

0
Link to comment
Share on other sites
Nick A

Nick A

Posted
Posted

You need these three files:

bcm4334.hcd                           (bluetooth)

fw_bcm4334b1_ag.bin           (wifi .bin)

nvram_ap6334.txt                   (wifi .txt)

 

 

0
Link to comment
Share on other sites
MMorales

MMorales

Posted
Posted

i copy the selected files in this way. 

mv /usr/lib/firmware/brcm/BCM4334B0.hcd /usr/lib/firmware/brcm/BCM4334B0_BAK.hcd
cp ./bcm4334.hcd /usr/lib/firmware/brcm/BCM4334B0.hcd

mv /usr/lib/firmware/rkwifi/fw_bcm4334b1_ag.bin /usr/lib/firmware/rkwifi/fw_bcm4334b1_ag_BAK.bin
cp ./fw_bcm4334b1_ag.bin /usr/lib/firmware/rkwifi/fw_bcm4334b1_ag.bin

cp ./nvram_ap6334.txt /usr/lib/firmware/rkwifi/

with these results: 

root@transpeed-8k618-t:~/ble# nano do.sh 
root@transpeed-8k618-t:~/ble# dmesg | grep -i bluetooth
[    5.456993] Bluetooth: Core ver 2.22
[    5.457104] NET: Registered PF_BLUETOOTH protocol family
[    5.457109] Bluetooth: HCI device and connection manager initialized
[    5.457128] Bluetooth: HCI socket layer initialized
[    5.457136] Bluetooth: L2CAP socket layer initialized
[    5.457150] Bluetooth: SCO socket layer initialized
[    5.590405] Bluetooth: HCI UART driver ver 2.3
[    5.590433] Bluetooth: HCI UART protocol H4 registered
[    5.590438] Bluetooth: HCI UART protocol BCSP registered
[    5.590540] Bluetooth: HCI UART protocol LL registered
[    5.590545] Bluetooth: HCI UART protocol ATH3K registered
[    5.590575] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    5.590741] Bluetooth: HCI UART protocol Intel registered
[    5.590870] Bluetooth: HCI UART protocol Broadcom registered
[    5.590904] Bluetooth: HCI UART protocol QCA registered
[    5.590910] Bluetooth: HCI UART protocol AG6XX registered
[    5.590937] Bluetooth: HCI UART protocol Marvell registered
[    5.949227] Bluetooth: hci0: BCM: chip id 68
[    5.951685] Bluetooth: hci0: BCM: features 0x0f
[    5.975070] Bluetooth: hci0: BCM4334B0
[    5.975091] Bluetooth: hci0: BCM4334B0 (002.001.013) build 0000
[    5.976485] Bluetooth: hci0: BCM4334B0 'brcm/BCM4334B0.hcd' Patch
[   11.805787] Bluetooth: hci0: BCM: features 0x0f
[   11.829327] Bluetooth: hci0: BCM4334B0 37.4MHz Class1.5 Samsung Note8-1675
[   11.829358] Bluetooth: hci0: BCM4334B0 (002.001.013) build 1718
[   12.100151] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   12.100185] Bluetooth: BNEP filters: protocol multicast
[   12.100204] Bluetooth: BNEP socket layer initialized
[   12.106914] Bluetooth: MGMT ver 1.22
root@transpeed-8k618-t:~/ble#  bluetoothctl
Agent registered
[CHG] Controller 43:34:B0:00:1F:AC Pairable: yes
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# discoverable on
Failed to set discoverable on: org.bluez.Error.Failed

 

0
Link to comment
Share on other sites
rafman

rafman

Posted
Posted (edited)
2 hours ago, Nick A said:

You need these three files:

bcm4334.hcd                           (bluetooth)

fw_bcm4334b1_ag.bin           (wifi .bin)

nvram_ap6334.txt                   (wifi .txt)

I rename: the files and copy it to /lib/firmware/brcm

 

bcm4334.hcd    -->  BCM4334B0.hcd

fw_bcm4334b1_ag.bin --> brcmfmac4334-sdio.transpeed,8k618-t.bin

nvram_ap6334.txt -->  (as is) to /lib/filrmware/brcm/

 

it seems to work for me now (i can see my mobile phone on discovery)  but i still have tx errors on dmesg.

Edited by rafman
0
Link to comment
Share on other sites
MMorales

MMorales

Posted
Posted 
cp ./bcm4334.hcd /lib/firmware/brcm/BCM4334B0.hcd
cp ./fw_bcm4334b1_ag.bin /lib/firmware/brcm/brcmfmac4334-sdio.transpeed,8k618-t.bin
cp ./nvram_ap6334.txt /lib/firmware/brcm/

 

@rafman I did same as you but not working.
my kernel is 6.9.12-edge-sunxi64 maybe is the diference.

  

Agent registered
[CHG] Controller 43:34:B0:00:1F:AC Pairable: yes
[bluetooth]# discoverable yes
Changing discoverable on succeeded
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# exit
root@transpeed-8k618-t:~/ble# bluetoothctl
Agent registered
[CHG] Controller 43:34:B0:00:1F:AC Pairable: yes
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress

 


 

0
Link to comment
Share on other sites
rafman

rafman

Posted
Posted
4 minutes ago, MMorales said:

@rafman I did same as you but not working.
my kernel is 6.9.12-edge-sunxi64 maybe is the diference.

 

Firmware is not stable Bluetooth adapter is not powered correctly.. sometimes works but not stable and lot of tx errors.

0
Link to comment
Share on other sites
MMorales

MMorales

Posted
Posted 
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
     Active: active (running) since Sat 2024-10-12 00:05:19 CEST; 1s ago
       Docs: man:bluetoothd(8)
   Main PID: 8382 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4539)
     Memory: 824.0K
        CPU: 372ms
     CGroup: /system.slice/bluetooth.service
             └─8382 /usr/libexec/bluetooth/bluetoothd

Oct 12 00:05:19 transpeed-8k618-t bluetoothd[8382]: Starting SDP server
Oct 12 00:05:19 transpeed-8k618-t bluetoothd[8382]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Oct 12 00:05:19 transpeed-8k618-t bluetoothd[8382]: src/plugin.c:plugin_init() Failed to init vcp plugin
Oct 12 00:05:19 transpeed-8k618-t bluetoothd[8382]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Oct 12 00:05:19 transpeed-8k618-t bluetoothd[8382]: src/plugin.c:plugin_init() Failed to init mcp plugin
Oct 12 00:05:19 transpeed-8k618-t bluetoothd[8382]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Oct 12 00:05:19 transpeed-8k618-t bluetoothd[8382]: src/plugin.c:plugin_init() Failed to init bap plugin
Oct 12 00:05:19 transpeed-8k618-t bluetoothd[8382]: Bluetooth management interface 1.22 initialized
Oct 12 00:05:19 transpeed-8k618-t bluetoothd[8382]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Oct 12 00:05:19 transpeed-8k618-t bluetoothd[8382]: sap-server: Operation not permitted (1)

 

i saw this and after seach in google i edited /etc/bluetooth/main.conf and add the line :

Experimental = true
after that: the result of status service is: 

root@transpeed-8k618-t:~# systemctl status bluetooth.service 
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
     Active: active (running) since Sat 2024-10-12 00:21:25 CEST; 1s ago
       Docs: man:bluetoothd(8)
   Main PID: 9590 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4539)
     Memory: 864.0K
        CPU: 284ms
     CGroup: /system.slice/bluetooth.service
             └─9590 /usr/libexec/bluetooth/bluetoothd

Oct 12 00:21:25 transpeed-8k618-t systemd[1]: Starting bluetooth.service - Bluetooth service...
Oct 12 00:21:25 transpeed-8k618-t bluetoothd[9590]: Bluetooth daemon 5.66
Oct 12 00:21:25 transpeed-8k618-t systemd[1]: Started bluetooth.service - Bluetooth service.
Oct 12 00:21:25 transpeed-8k618-t bluetoothd[9590]: Starting SDP server
Oct 12 00:21:25 transpeed-8k618-t bluetoothd[9590]: Bluetooth management interface 1.22 initialized
Oct 12 00:21:25 transpeed-8k618-t bluetoothd[9590]: Battery Provider Manager created
Oct 12 00:21:25 transpeed-8k618-t bluetoothd[9590]: Adv Monitor Manager created with supported features:0x00000000, enabled features:0x00000000, max number of supported moni>

and the ble stil not working: bah 

root@transpeed-8k618-t:~# bluetoothctl
Agent registered
[CHG] Controller 43:34:B0:00:1F:AC Pairable: yes
AdvertisementMonitor path registered
[bluetooth]# power on
[CHG] Controller 43:34:B0:00:1F:AC PowerState: off-enabling
Failed to set power on: org.bluez.Error.Failed
[CHG] Controller 43:34:B0:00:1F:AC PowerState: on
[bluetooth]# show
Controller 43:34:B0:00:1F:AC (public)
	Name: transpeed-8k618-t
	Alias: transpeed-8k618-t
	Class: 0x00000000
	Powered: no
	PowerState: on
	Discoverable: no
	DiscoverableTimeout: 0x000000b4
	Pairable: yes
	UUID: SIM Access                (0000112d-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Volume Control            (00001844-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0542
	Discovering: no
	Roles: central
	Roles: peripheral
Advertising Features:
	ActiveInstances: 0x00 (0)
	SupportedInstances: 0x05 (5)
	SupportedIncludes: tx-power
	SupportedIncludes: appearance
	SupportedIncludes: local-name
	SupportedCapabilities Key: MaxAdvLen
	SupportedCapabilities Value: 0x1f (31)
	SupportedCapabilities Key: MaxScnRspLen
	SupportedCapabilities Value: 0x1f (31)
Advertisement Monitor Features:
	SupportedMonitorTypes: or_patterns
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
[bluetooth]# devices
[bluetooth]# discoverable on
Failed to set discoverable on: org.bluez.Error.Failed

 

0
Link to comment
Share on other sites
rafman

rafman

Posted
Posted (edited)
13 hours ago, Nick A said:

Maybe you'll have better luck with these.

 

I will try for more tomorrow.

 

it seems to do be a mater of firmware however this firmware works but not stable.

With previous firmware a was not able to discover any device. however and with android firmware I have tx errors.

 

IMG_20241012_015942.jpg.120856032532f94881b358038752a8d4.jpg

 

FYI : I attach my dmesg files for both situations with original (before)  and (android) 

original fw files was also from LibreElec collection. but i will check tomorrow if something is different in your link above.

 

 

 

android-fw-dmesg original-fw-dmesg

Edited by rafman
0
Link to comment
Share on other sites
Nick A

Nick A

Posted
Posted (edited)
Quote

original fw files was also from LibreElec collection

 

I think you used the wifi firmware from LibreElec. But the bluetooth firmware "BCM4334B0.hcd" was already existing in the Armbian firmware folder. The Armbian firmware might be different than LibreElec's version. Worth a try.

 

I'm not sure if the sdio.txt file has bluetooth configuration settings in it. We can play with some of these settings.

Edited by Nick A
0
Link to comment
Share on other sites
firepower

firepower

Posted
Posted (edited)

I have ordered the Vontar H618 as it hardware is similar to transpeed most are using. I am new armbian and have much to learn, so using Vontar should be easier then Tanix Tx6.

@rafman what is the monitor software on your desktop?

 

Edited by firepower
0
Link to comment
Share on other sites
rafman

rafman

Posted
Posted (edited)
11 hours ago, Nick A said:

I think you used the wifi firmware from LibreElec. But the bluetooth firmware "BCM4334B0.hcd" was already existing in the Armbian firmware folder. The Armbian firmware might be different than LibreElec's version. Worth a try.

 

I'm not sure if the sdio.txt file has bluetooth configuration settings in it. We can play with some of these settings.

 

Results.

 

1> The original BCM4334B0.hcd from my Armbian image does not work, and i think has same behavior as the LibreElec BCM4334B0.hcd.

 

2> Firmware from LibreElec works only with the wifi but not with Bluetooth.

 

3> The android firmware works but not stable (I am not 100% sure about the Android firmware file) i used to extract it because i did not Flash this

      firmware to my device, however from my internet search i found that  many  variations of transpeed-8k h618 box exists arround.

      NOTE: There is also a newer version of android firmware (H618.apollo-p3.T-H618_100M_12_FD650.2023.09.13.17.20.img) that i will investigate today to see if some firmware is different.

 

4> I think the "sdio.txt" is the nvram file (nvram_ap6334.txt) and i already test it (as is)  by copy to /lib/firmware/brcm and as brcmfmac4334-sdio.transpeed,8k618-t.txt

     but this did not make any changes.

 

 

I am taking this information about interface (android fw):

 

rafman@orion-8k:~$ sudo hciconfig -a
[sudo] password for rafman:
hci0:    Type: Primary  Bus: UART
    BD Address: 43:34:B0:00:1F:AC  ACL MTU: 1021:8  SCO MTU: 64:1
    UP RUNNING
    RX bytes:5156 acl:0 sco:0 events:603 errors:0
    TX bytes:56764 acl:0 sco:0 commands:619 errors:0
    Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH SNIFF
    Link mode: PERIPHERAL ACCEPT
Can't read local name on hci0: Connection timed out (110)

 

 

7 hours ago, firepower said:

what is the monitor software on your desktop?

This is my TV, with Mate Desktop (customized) 

Edited by rafman
0
Link to comment
Share on other sites
MMorales

MMorales

Posted
Posted (edited)

I have this android image wich is the latest H618.apollo-p16.VONTAR_H618_100M_12_FD650.2024.05.20.12.40.img
you can get here https://www.dropbox.com/scl/fi/auh5wmpsigzlrt0ew56vr/VONTAR-H618.zip?rlkey=y00w06w1d3u1ojzl3tuw2nlct&e=1&st=7pwisv8d&dl=0

i installed in a device and extracted the files.
but are the same anyway here you have.

files_from_android_2024.zip

But no bluetooth neither. there are the same files.

Edited by MMorales
0
Link to comment
Share on other sites
rafman

rafman

Posted
Posted
59 minutes ago, Nick A said:

Try the firmware from here.

https://forums.linuxmint.com/viewtopic.php?p=1994357#p1994357

Negative / Crash

 

I have deleted  everything from my /lib/firmware/brcm and i reverse the android (fw)

now i have only theese files and bluetooth working as previous.

 

rafman@orion-8k:~$ ls -l /lib/firmware/brcm/    
total 512
-rw-r--r-- 1 rafman rafman  53957 Jan  1  2009 BCM4334B0.hcd
-rw-r--r-- 1 rafman rafman 457249 Jan  1  2009 brcmfmac4334-sdio.transpeed,8k618-t.bin
-rw-r--r-- 1 rafman rafman   2019 Jan  1  2009 brcmfmac4334-sdio.transpeed,8k618-t.txt
-rw-r--r-- 1 rafman rafman   2019 Jan  1  2009 brcmfmac4334-sdio.txt

 

I will unpack/decopmpose now the newer android firmware . (H618.apollo-p3.T-H618_100M_12_FD650.2023.09.13.17.20.img)

 

0
Link to comment
Share on other sites
rafman

rafman

Posted
Posted (edited)

Hmm Unpacked Firmware files for Bluetooth, seems to be the same and on newer firmware.

 

But this time i will share the whole vendor/etc folder because i see that it contains some configuration files about bt and wifi and other hardware from the vendor

so probably we may extract very useful information about box configuration by study on it.

 

You can download it here : https://easyupload.io/sdd0a0


My current Bluetooth state is this: 

rafman@orion-8k:~$ bluetoothctl
Agent registered
[bluetooth]# show
Controller 43:34:B0:00:1F:AC (public)
    Name: orion-8k
    Alias: orion-8k
    Class: 0x00000000
    Powered: yes
    Discoverable: yes
    DiscoverableTimeout: 0x00000000
    Pairable: yes
    UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
    UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
    UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
    UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
    UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
    UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
    UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
    UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
    UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
    UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
    UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
    UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
    UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
    Modalias: usb:v1D6Bp0246d0542
    Discovering: no
    Roles: central
    Roles: peripheral
Advertising Features:
    ActiveInstances: 0x00 (0)
    SupportedInstances: 0x05 (5)
    SupportedIncludes: tx-power
    SupportedIncludes: appearance
    SupportedIncludes: local-name

 

Edited by rafman
0
Link to comment
Share on other sites
MMorales

MMorales

Posted
Posted

@rafman these files are the same of here https://github.com/armbian/firmware/tree/master so i think they are irrelevant.
But the bluetooth of the android image works nice. So we are not seeing anything in that rom. 
Im not an expert but it posible to get the starting system log on that android installation and look how the drivers and firmware is loading?. I have a live vontar in the living room with android.

0
Link to comment
Share on other sites
rafman

rafman

Posted
Posted
13 minutes ago, MMorales said:

these files are the same of here https://github.com/armbian/firmware/tree/master so i think they are irrelevant.
But the bluetooth of the android image works nice. So we are not seeing anything in that rom. 
Im not an expert but it posible to get the starting system log on that android installation and look how the drivers and firmware is loading?. I have a live vontar in the living room with android.

if vontar has the same chip Every information/log will be usefull. But i don't have any live android (Transpeed-k8-t box).

 

I attach here my partial working firmware files, if you want to test it with your kernel.

part-working-fw.tar.gz

0
Link to comment
Share on other sites
MMorales

MMorales

Posted
Posted

@rafman After copying your files. the result is:
  

root@transpeed-8k618-t:~# dmesg | grep -i bluetooth
[    6.247309] Bluetooth: Core ver 2.22
[    6.247463] NET: Registered PF_BLUETOOTH protocol family
[    6.247467] Bluetooth: HCI device and connection manager initialized
[    6.247487] Bluetooth: HCI socket layer initialized
[    6.247494] Bluetooth: L2CAP socket layer initialized
[    6.247510] Bluetooth: SCO socket layer initialized
[    6.271803] Bluetooth: HCI UART driver ver 2.3
[    6.271847] Bluetooth: HCI UART protocol H4 registered
[    6.271851] Bluetooth: HCI UART protocol BCSP registered
[    6.272026] Bluetooth: HCI UART protocol LL registered
[    6.272031] Bluetooth: HCI UART protocol ATH3K registered
[    6.272063] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    6.272291] Bluetooth: HCI UART protocol Intel registered
[    6.272407] Bluetooth: HCI UART protocol Broadcom registered
[    6.272451] Bluetooth: HCI UART protocol QCA registered
[    6.272455] Bluetooth: HCI UART protocol AG6XX registered
[    6.272516] Bluetooth: HCI UART protocol Marvell registered
[    6.633454] Bluetooth: hci0: BCM: chip id 68
[    6.635949] Bluetooth: hci0: BCM: features 0x0f
[    6.659453] Bluetooth: hci0: BCM4334B0
[    6.659501] Bluetooth: hci0: BCM4334B0 (002.001.013) build 0000
[    6.661385] Bluetooth: hci0: BCM4334B0 'brcm/BCM4334B0.hcd' Patch
[   12.446784] Bluetooth: hci0: BCM: features 0x0f
[   12.470398] Bluetooth: hci0: BCM4334B0 37.4MHz Class1.5 Samsung Note8-1675
[   12.470428] Bluetooth: hci0: BCM4334B0 (002.001.013) build 1718
[   13.079670] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   13.079706] Bluetooth: BNEP filters: protocol multicast
[   13.079726] Bluetooth: BNEP socket layer initialized
[   13.090355] Bluetooth: MGMT ver 1.22
[   13.434862] Bluetooth: RFCOMM TTY layer initialized
[   13.434921] Bluetooth: RFCOMM socket layer initialized
[   13.434952] Bluetooth: RFCOMM ver 1.11
[   15.460611] Bluetooth: hci0: Opcode 0x0c56 failed: -110
[   15.460703] Bluetooth: hci0: command 0x0c56 tx timeout
[   17.476600] Bluetooth: hci0: command 0x0c56 tx timeout
[   17.476678] Bluetooth: hci0: Opcode 0x0c52 failed: -110
[   19.492752] Bluetooth: hci0: command 0x0c56 tx timeout
[   19.492814] Bluetooth: hci0: Opcode 0x0c52 failed: -110
[   21.508663] Bluetooth: hci0: command 0x0c56 tx timeout
[   21.510448] Bluetooth: hci0: Opcode 0x0c52 failed: -110
[   23.460485] Bluetooth: hci0: Opcode 0x0c24 failed: -110
[   23.460577] Bluetooth: hci0: command 0x0c56 tx timeout
[   25.475854] Bluetooth: hci0: Opcode 0x0c24 failed: -110
[   25.475889] Bluetooth: hci0: command 0x0c56 tx timeout
[   27.491587] Bluetooth: hci0: Opcode 0x0c52 failed: -110
[   27.491652] Bluetooth: hci0: command 0x0c56 tx timeout
[   27.491688] Bluetooth: hci0: Opcode 0x0c24 failed: -110
[   29.511589] Bluetooth: hci0: command 0x0c56 tx timeout
[   29.511586] Bluetooth: hci0: Opcode 0x0c13 failed: -110
[   31.523635] Bluetooth: hci0: Opcode 0x0c52 failed: -110
[   31.523658] Bluetooth: hci0: command 0x0c56 tx timeout
[   33.539704] Bluetooth: hci0: command 0x0c56 tx timeout
[   33.539812] Bluetooth: hci0: Opcode 0x0c13 failed: -110
[   35.555751] Bluetooth: hci0: command 0x0c56 tx timeout
[   35.555883] Bluetooth: hci0: Opcode 0x0c52 failed: -110
[   37.571821] Bluetooth: hci0: command 0x0c56 tx timeout

root@transpeed-8k618-t:~# bluetoothctl show
Controller 43:34:B0:00:1F:AC (public)
	Name: transpeed-8k618-t
	Alias: transpeed-8k618-t
	Class: 0x00000000
	Powered: no
	PowerState: on
	Discoverable: no
	DiscoverableTimeout: 0x000000b4
	Pairable: no
	UUID: SIM Access                (0000112d-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Volume Control            (00001844-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0542
	Discovering: no
	Roles: central
	Roles: peripheral
Advertising Features:
	ActiveInstances: 0x00 (0)
	SupportedInstances: 0x05 (5)
	SupportedIncludes: tx-power
	SupportedIncludes: appearance
	SupportedIncludes: local-name
	SupportedCapabilities Key: MaxAdvLen
	SupportedCapabilities Value: 0x1f (31)
	SupportedCapabilities Key: MaxScnRspLen
	SupportedCapabilities Value: 0x1f (31)
Advertisement Monitor Features:
	SupportedMonitorTypes: or_patterns

root@transpeed-8k618-t:~# bluetoothctl scan on
Failed to start discovery: org.bluez.Error.NotReady

root@transpeed-8k618-t:~# uname -r
6.9.12-edge-sunxi64

 

0
Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept