Raspberry Pi 3 - Setting Up Bluetooth: Difference between revisions
m (+ category: Raspberry) |
m (Use pkg template.) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Merge|Raspberry Pi|or create subpages}} | |||
The Raspberry Pi Bluetooth chip varies by model. | The Raspberry Pi Bluetooth chip varies by model. | ||
| Line 11: | Line 13: | ||
You'll need the bluez package | You'll need the bluez package | ||
{{cmd|apk add bluez}} | {{cmd|# apk add {{pkg|bluez|arch=a*}}}} | ||
The Bluetooth controller is not automatically discovered on the UART. Test attaching it and check that the controller is found: | |||
{{cmd|$ btattach -B /dev/ttyAMA0 -P bcm -S 115200 -N &}} | |||
{{cmd| | {{cmd|# rc-service bluetooth start}} | ||
<p style="background-color:#f9f9f9; border:1px dashed #2f6fab; line-height:1.1em; padding:1em; font-family:monospace; font-size:10pt; white-space:pre; overflow:auto;"><span style="color:green;">~</span>'''$''' bluetoothctl list | |||
Controller B8:27:EB:01:02:03 BlueZ 5.50 [default] | Controller B8:27:EB:01:02:03 BlueZ 5.50 [default] | ||
</ | </p> | ||
If the interface is discovered after the attach, you can make attaching persistent by uncommenting | If the interface is discovered after the attach, you can make attaching persistent by uncommenting | ||
the line next to | the line next to <code>rpi bluetooth</code> in {{Path|/etc/mdev.conf}}. | ||
Start the | Start the Bluetooth daemon at boot: | ||
{{cmd|rc-update add bluetooth}} | {{cmd|# rc-update add bluetooth}} | ||
{{cmd|lbu commit && reboot}} | {{cmd|# lbu commit && reboot}} | ||
The output from the btattach above should be | The output from the <code>btattach</code> above should be | ||
Attaching Primary controller to /dev/ttyAMA0 | |||
Switched line discipline from 0 to 15 | Switched line discipline from 0 to 15 | ||
Device index 0 attached | Device index 0 attached | ||
Then it's a matter of doing what you normally do with your Bluetooth stack. | Then it's a matter of doing what you normally do with your Bluetooth stack. | ||
== See also == | |||
* [[Bluetooth]] | |||
[[Category:Installation]] | [[Category:Installation]] | ||
[[category: Raspberry]] | [[category: Raspberry]] | ||
Latest revision as of 14:31, 10 January 2024
 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.