Bluetooth Missing in Console after 3.60~65 and ~66

Beta testing Venus OS beta testing
1

  • How its expected to work
    Bluetooth should be present in menu.

  • How it doesn’t work as expected
    Bluetooth adapter is missing from menu entirely

  • Details on the system
    Cerbo GX, Multiplus II 24v / 120v
    Testing beta since old UI versions. BT working fine in previous beta up through 3.60~60
    Temp at system location reported by Cerbo temp sensor = 12.7C

  • What you’ve already tried to make sure its not a setting or other
    issue.
    Reverted to 3.55, Bluetooth device shows up again. Went back to 3.60~66 Bluetooth device missing.

Running top in SSH reveals similar CPU load %, but unsure of actual impact there. 3.55 idle 10%, during FW upgrade 14-19%. 3.60~66 idle = 12-14% idle, seeing 19% occasionally.

3.60~66
Temp from SSH:
root@einstein:~# cat /sys/class/thermal/cooling_device0/subsystem/thermal_zone0/temp .
42300
=42.3C
root@einstein:~# cat /sys/class/thermal/thermal_zone0/temp
42400
=42.4C

image
image658×636 16.7 KB

2

Edit, sorry pasted twice previously. Removed the middle bit. It just keeps going.

Here’s more console output:

root@einstein:~# dmesg|grep Bluetooth
[ 7.662721] Bluetooth: Core ver 2.22
[ 7.677105] Bluetooth: HCI device and connection manager initialized
[ 7.683506] Bluetooth: HCI socket layer initialized
[ 7.688503] Bluetooth: L2CAP socket layer initialized
[ 7.751845] Bluetooth: HCI UART driver ver 2.3
[ 7.756529] Bluetooth: HCI UART protocol H4 registered
[ 7.765905] Bluetooth: HCI UART protocol Broadcom registered
[ 8.178960] Bluetooth: hci0: BCM: chip id 94
[ 8.185843] Bluetooth: hci0: BCM: features 0x2e
[ 8.214155] Bluetooth: hci0: BCM43430A1
[ 8.218064] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000
[ 8.226244] Bluetooth: hci0: BCM43430A1 ‘brcm/BCM43430A1.hcd’ Patch
[ 13.593930] Bluetooth: hci0: command 0xfc18 tx timeout
[ 13.599168] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[ 15.674051] Bluetooth: hci0: command 0xfc18 tx timeout
[ 15.679316] Bluetooth: hci0: BCM: Reset failed (-110)
[ 48.153975] Bluetooth: hci0: command tx timeout
[ 56.164450] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[ 56.171242] Bluetooth: hci0: Failed to set baudrate
[ 66.394151] Bluetooth: hci0: BCM: Reset failed (-110)
[ 66.930296] Bluetooth: hci0: BCM: chip id 94
[ 66.938118] Bluetooth: hci0: BCM: features 0x2e
[ 66.966807] Bluetooth: hci0: BCM43430A1
[ 66.970721] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000
[ 67.007252] Bluetooth: hci0: BCM43430A1 ‘brcm/BCM43430A1.hcd’ Patch
[ 72.234031] Bluetooth: hci0: command 0xfc18 tx timeout
[ 72.239445] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[ 74.313993] Bluetooth: hci0: command 0xfc18 tx timeout
[ 74.319650] Bluetooth: hci0: BCM: Reset failed (-110)
[ 76.634033] Bluetooth: hci0: command tx timeout
[ 84.964020] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[ 84.970810] Bluetooth: hci0: Failed to set baudrate
[ 95.195550] Bluetooth: hci0: BCM: Reset failed (-110)
[ 95.549073] Bluetooth: hci0: BCM: chip id 94
[ 95.555897] Bluetooth: hci0: BCM: features 0x2e
[ 95.584511] Bluetooth: hci0: BCM43430A1
[ 95.588424] Bluetooth: hci0: BCM43430A1 (001.002.009) build 0000
[ 95.594935] Bluetooth: hci0: BCM43430A1 ‘brcm/BCM43430A1.hcd’ Patch

keeps repeating…

[ 1890.313918] Bluetooth: hci0: command 0xfc18 tx timeout
[ 1890.319174] Bluetooth: hci0: BCM: Reset failed (-110)
[ 1892.553903] Bluetooth: hci0: command tx timeout
[ 1900.633895] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[ 1900.640654] Bluetooth: hci0: Failed to set baudrate

3

Is this topic any use. Do you have an older Cerbo with serial number prior to HQ2207. Do you have an external USB Bluetooth dongle or just using the internal one.

The limitation in the manual for older devices:
Note for Cerbo GX units built up to and including serial number HQ2207; The built-in Bluetooth connection is disabled when the internal CPU temperature exceeds 53 degrees C (influenced by load and/or ambient temperature). For reliable operation it is necessary to use a USB Bluetooth adapter. Devices manufactured later (HQ2208 and later) do not require an additional USB Bluetooth adapter.

4

I am not sure there is a need for such a long log dump, it is repetitive and it will discourage people from scrolling through.

5

Internal, I don’t believe this is a temperature issue. I have posted the Cerbo internal temp of being at under 43C. This was read in SSH.

I understand that the manual has been updated since this issue was discovered. However this ‘old’ hardware was produced and sold through 2024. Victron states a 5 year warranty and “Robust products that keep performing” Not "You are out of luck and go buy a questionable USB device and likely hub and use that instead of your industry-leading, less than 5 year old hardware.

Regarding the dump, yes, I agree. I was hoping for a ‘code’ option that would hide it until clicked. I was editing this as you were replying trying to fix that. I’ll strip out the middle and note.

6

Hi all, we tested on a Cerbo GX with a serial number prior to HQ2207, and bluetooth works as it did before the recent changes in Venus OS: it works, mostly, but not when the microprocessor is too warm - and in general is unreliable as has been documented and discussed in many places.

The solution remains to add a small few dollar USB bluetooth adapter and/or otherwise contact your distributor to see if its eligible for warranty.

All the best!

7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.