Is Raspberry Pi 3B bluetooth supported on NetBSD 10.0

hsw

I cannot seem to find any details of how to set this up. The NetBSD Wiki implies that it can work, but I could not find any example config. I found an old post the mentioned adding a config line and downloading some firmware files.
The config line was already in /etc/bluetooth/btattach.conf and was commented out. I added an uncommented version then later added a "d" for debugging. I also found some firmware files on Github

# Raspberry Pi 3 Bluetooth UART
#bcm43xx-3wire  /dev/dplcom0    921600          -FPi 115200
bcm43xx-3wire   /dev/dplcom0    921600          -dFPi 115200

arm64# ls -l /libdata/firmware/bcm43xx/
total 280
-rw-r--r--  1 root  wheel  30049 May 15 14:41 BCM43430A1.hcd
-rw-r--r--  1 root  wheel  44376 May 15 14:41 BCM43430B0.hcd
-rw-r--r--  1 root  wheel  38630 May 15 14:41 BCM43438A0.hcd
-rw-r--r--  1 root  wheel  33376 May 15 14:41 BCM43438A1.hcd
-rw-r--r--  1 root  wheel  63806 May 15 14:41 BCM4345C0.hcd
-rw-r--r--  1 root  wheel  55676 May 15 14:41 BCM4345C5.hcd

Looking at the debug output: I see some hex strings: (which I converted to ASCII)

…42 43 4d 34 33 34 33 30 41 31…
BCM43430A1

…42 43 4d 34 33 34 33 38 41 31 20 33 37 2e 34 4d 48 7a 20 52 61 73 70 62 65 72 72 79 20 50 69 20 33 2d 30 30 34 33 4f…
BCM43438A1 37.4MHz Raspberry Pi 3-0043O

so I think the bcm43xx/BCM43430A1.hcd should be the right firmware, though I do not see any indication if it was loaded.

But the boot up just shows:

attaching Bluetooth controller to dplcom0
…hex code here…
btattach: bth5: Device not configured
configuring Bluetooth controllers:.
starting Bluetooth Link Key/PIN Code manager
attaching Bluetooth HSET service from "speaker"
btdevctl: sbt0: Device not configured
attaching Bluetooth HSET service from "speaker"
btdevctl: ubt0: Device not configured
starting Bluetooth Service Discovery server

the btconfig command does not list any devices.
Does anyone have any suggestions?

rvp

hsw Can you ask on port-arm@. Maybe someone there has tried this out. I have no ARM HW at all, so don't know much about this arch...

hsw

I found a suggestion from Gentoo Wiki to add this kline to /boot/config.txt

dtparam=krnbt=on

Does not help though. I suspect the the necessary driver is not part of the default kernel config. perhaps that is what the message about bth5: Device not configured means.

hsw

rvp I subscribed and posted this message: https://mail-index.netbsd.org/port-arm/2024/05/19/msg008713.html I will report here if I receive any info

hsw

Progress so far: I found out that GENERIC64 does not have bluetooth drivers so I made a modified GENERIC64BT and built a kernel. This does allow the bthfive0 interface to come up at boot sometimes, adding a sleep 3 into /etc/rc.d/bluetooth between the attach loop and the btconfig loop made the on boot appear to be reliable.

That dtparam line inconfig.txt is not needed.

I can now used btconfig bthfive0 inquiry to list nearby devices as long as they are in pair mode, and use btpin to pair with a speaker device.

However I could not get bta2dp to connect to the Speaker it would normally hang until the speaker timed out and powered down. It was trying to do something because it would error immediately I powered off the speaker.

the possible errors being:

A2DP: Required sdp record not found
A2DP: Could not open sdp session
init client: Operation timed out

I will next try with the Arm V7 image to see if that is any difference using a 32 bit system. Though this image seems to have problems with a stable console - not sure if its the USB→serial or the USB power that is problem yet.

Edited to add:
Console much more stable with different USB adaptor. but the bthfive0 does not load, added -d to the attach command to get debugging output. as far as I remember the response to the firs packet should be the device version (for firmware load), but the response seems to be a zero byte.

attaching Bluetooth controller to dplcom0
<< 01 03 0c 00
btattach: unknown packet type 0x00
>> 00configuring Bluetooth controllers:.
starting Bluetooth Link Key/PIN Code manager
starting Bluetooth Service Discovery server

rvp

hsw However I could not get bta2dp to connect to the Speaker

Does it respond to A2DP or the newer AVRCP. I have an Xbox headset which Linux connects to using AVRCP. I'll see what NetBSD does with it--maybe this weekend.

hsw attaching Bluetooth controller to dplcom0

Hmm. Is that btattach to dplcom0 needed? That's only for Bluetooth serial controllers, I think? What does

btconfig -l

report? (ubt0 on my amd64 laptop).

rvp

rvp Does it respond to A2DP or the newer AVRCP. I have an Xbox headset which Linux connects to using AVRCP. I'll see what NetBSD does with it--maybe this weekend.

OK. So tested this, and my Xbox headset does A2DP too so this works on NetBSD (after you (warm) reboot into NetBSD from Linux to get the Bluetooth controller firmware loaded). But, the volume is way too low--even with bta2dpd -V2.

$ uname -a
Linux CoreBook 6.5.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Mon May 20 15:55:15 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

$ bluetoothctl
Agent registered
[CHG] Controller 10:F6:0A:E4:C2:57 Pairable: yes
[CHG] Device 4C:3B:DF:C5:F3:DA Connected: yes
[NEW] Endpoint /org/bluez/hci0/dev_4C_3B_DF_C5_F3_DA/sep1 
[NEW] Transport /org/bluez/hci0/dev_4C_3B_DF_C5_F3_DA/fd3 
[CHG] Transport /org/bluez/hci0/dev_4C_3B_DF_C5_F3_DA/fd3 Delay: 0x0906 (2310)
[CHG] Transport /org/bluez/hci0/dev_4C_3B_DF_C5_F3_DA/fd3 State: active
[CHG] Transport /org/bluez/hci0/dev_4C_3B_DF_C5_F3_DA/fd3 Volume: 0x006b (107)
[Xbox Wireless Headset]# info
Device 4C:3B:DF:C5:F3:DA (public)
        Name: Xbox Wireless Headset
        Alias: Xbox Wireless Headset
        Class: 0x0024041c (2360348)
        Icon: audio-card
        Paired: yes
        Bonded: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacaff)
        UUID: Serial Port               (00001101-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v045Ep0B16d0000
[Xbox Wireless Headset]# ^D

$