Raspberry Pi 3 - Setting Up Bluetooth

From Alpine Linux
Revision as of 14:31, 10 January 2024 by Zcrayfish (talk | contribs) (Use pkg template.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
This material is proposed for merging ...

It should be merged with Raspberry Pi. or create subpages (Discuss)

The Raspberry Pi Bluetooth chip varies by model.

  • Raspberry Pi 3 has BCM2837 connected to the hardware UART
  • Raspberry Pi 3B+ has BCM4345C0 connected to the hardware UART
  • Raspberry Pi Zero W has BCM43430A1 connected to the hardware UART

You can get Bluetooth to work only if you are not using the UART (ttyAMA0) for anything else, for example serial console. Recent versions of Alpine Linux for Raspberry Pi come with the required Broadcom firmware files. If you need the UART for something else, you can use an USB Bluetooth adapter instead.

You'll need the bluez package

# apk add bluez

The Bluetooth controller is not automatically discovered on the UART. Test attaching it and check that the controller is found:

$ btattach -B /dev/ttyAMA0 -P bcm -S 115200 -N &

# rc-service bluetooth start

~$ bluetoothctl list Controller B8:27:EB:01:02:03 BlueZ 5.50 [default]

If the interface is discovered after the attach, you can make attaching persistent by uncommenting the line next to rpi bluetooth in /etc/mdev.conf.

Start the Bluetooth daemon at boot:

# rc-update add bluetooth

# lbu commit && reboot


The output from the btattach above should be

Attaching Primary controller to /dev/ttyAMA0
Switched line discipline from 0 to 15
Device index 0 attached

Then it's a matter of doing what you normally do with your Bluetooth stack.

See also