You are here: start » interfaces » bluetooth

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
interfaces:bluetooth [2023/12/05 11:52] – [Bluetooth] darroninterfaces:bluetooth [2023/12/15 07:45] (current) – [USB] darron
Line 1: Line 1:
 ====Bluetooth==== ====Bluetooth====
  
-Various Bluetooth device setup in Linux on RPi and similar devices.+See [[tools:bluetooth]] for Linux Bluetooth services and development.
  
 There are two standards in use known as BT classic and BT low energy. There are two standards in use known as BT classic and BT low energy.
  
-Anything other than BLE is considered obsolete now.+Anything other than BLE is considered to be legacy now.
  
 ^HCI / LMP^Version^ ^HCI / LMP^Version^
-|0| 1.0b| +|0|     1.0b| 
-|1| 1.1| +|1|     1.1| 
-|2| 1.2| +|2|     1.2| 
-|3| 2.0+EDR| +|3|     2.0+EDR| 
-|4| 2.1+EDR| +|4|     2.1+EDR| 
-|5| 3.0+HS| +|5|     3.0+HS| 
-|6| 4.0| +|6|     4.0| 
-|7| 4.1| +|7|     4.1| 
-|8| 4.2| +|8|     4.2| 
-|9| 5.0| +|9|     5.0| 
-|10| 5.1| +|10|    5.1| 
-|11| 5.2| +|11|    5.2| 
-|12| 5.3|+|12|    5.3|
  
-BT 3.0+HS utilises WiFi. BT 4.0 onward is low energy, anything prior is BDR/EDR.+BT 3.0+HS utilises WiFi. BT 4.0 onward is BLE, anything prior is BDR/EDR.
  
-===Hardware===+===RPi===
  
-==RPi==+The Raspberry Pi3/4 have built in BT BLE 5.0 but it can be awkward to setup 
 +the UART configuration. UART can be /dev/ttyS0 or /dev/ttyAMA0 depending 
 +on how you configure it in /boot/config.txt
  
-The Raspberry Pi3/4 have built in BT BLE 5.0 but it can be annoying to setup +If the device needs to be attached to a specific the UART it can be 
-with the UART configuration. UART can be /dev/ttyS0 or /dev/ttyAMA0 depending +done like this.
-upon how you configure them in boot up.+
  
-The device needs to be attached via the UART. With the Pi4 
-this can be done in config.txt (not sure about Pi3). 
- 
-Manually attachment can be done like this: 
 <code> <code>
 btattach -B /dev/ttyAMA0 -P bcm -S 3000000 btattach -B /dev/ttyAMA0 -P bcm -S 3000000
 </code> </code>
  
-Kernel attachment requires the following entry:+Alternatively, the kernel can attach with the following entry in /boot/config.txt 
 +on both the Pi3 and Pi4 (reboot to take effect). 
 <code> <code>
 dtparam=krnbt=on dtparam=krnbt=on
Line 114: Line 113:
 </code> </code>
  
-==USB==+===USB===
  
-Here is a list of obsolete BT USB adapters all of which are either BT 2.0 or 1.2.+Here is a list of legacy BT USB adapters all of which are either BT 2.0 or 1.2.
  
  
 __BARROT__ __BARROT__
  
-BT 2.0 CSR clones which are very cheap from pound stores.+CSR clones which are very cheap and found in pound stores. 
 + 
 +BT 2.0
  
 <code> <code>
Line 156: Line 157:
 __Silicon Wave__ __Silicon Wave__
  
-A very old BT 1.2 interface+A very old USB adapter. 
 + 
 +BT 1.2
  
 <code> <code>
Line 217: Line 220:
 </code> </code>
  
-BT 2.0 + EDR+BT 2.0
  
 <code> <code>
Line 244: Line 247:
         Manufacturer: Broadcom Corporation (15)         Manufacturer: Broadcom Corporation (15)
 </code> </code>
-===Services=== 
  
-==DBUS== 
- 
-I normally disable dbus with systemd and here is how to enable this service with `runit' if preferred. 
- 
-<code> 
-#!/bin/bash 
-sleep 1 
- 
-#LOG 
-exec 2>&1 
-ulimit -aH 
- 
-#RUN 
-export TZ="UTC" 
-rm -Rf /var/run/dbus 
-mkdir -p /var/run/dbus 
-exec dbus-daemon --syslog --syslog-only --nofork --config-file=/usr/share/dbus-1/system.conf 
-</code> 
- 
-==BLUETOOTHD== 
- 
-Install bluez and various tools if not already installed 
- 
-<code> 
-apt install bluez bluez-test-tools bluez-hcidump 
-</code> 
- 
-I prefer to run Bluetoothd from `runit' 
- 
-This run file can work but it  should wait until dbus is ready before starting. 
- 
-See the wait method of runit to detect /var/run/dbus/pid. 
- 
-<code> 
-#!/bin/bash 
-sleep 5 
- 
-#LOG 
-exec 2>&1 
-ulimit -aH 
- 
-#RUN 
-export TZ="UTC" 
-exec /usr/sbin/bluetoothd -n 
-</code>