55
ODROID C1 USER MANUAL
[
0.871245@0] Bluetooth: L2CAP socket layer initialized
[
0.876447@0] Bluetooth: SCO socket layer initialized
[
1.429422@2] Bluetooth: HCI UART driver ver 2.2
[
1.433876@2] Bluetooth: HCI H4 protocol initialized
[
1.438828@2] Bluetooth: HCI BCSP protocol initialized
[
1.443919@2] Bluetooth: HCILL protocol initialized
[
1.448782@2] Bluetooth: HCIATH3K protocol initialized
[
1.453877@2] Bluetooth: HCI Three-wire UART (H5) protocol ini-
tialized
[
3.236424@2] Bluetooth: btwake_control_init Driver Ver 1.1
[
3.366366@2] Bluetooth: RFCOMM TTY layer initialized
[
3.371156@2] Bluetooth: RFCOMM socket layer initialized
[
3.376392@2] Bluetooth: RFCOMM ver 1.11
[
3.380308@2] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[
3.385744@2] Bluetooth: BNEP filters: protocol multicast
[
3.397895@2] Bluetooth: BNEP socket layer initialized
[
3.402975@2] Bluetooth: HIDP (Human Interface Emulation) ver
1.2
[
3.409060@2] Bluetooth: HIDP socket layer initialized
You can then check the list of the installed Bluetooth modules:
$ dpkg -l | grep blue
ii blueman ... armhf Graphical bluetooth manager
ii bluez ... armhf Bluetooth tools and daemons
ii bluez-alsa:armhf ... armhf Bluetooth ALSA support
ii bluez-cups ... armhf Bluetooth printer driver for
CUPS
ii libbluetooth-dev ... armhf Dev. files for BlueZ Linux
Bluetooth lib
ii libbluetooth3:armhf ... armhf Library to use the BlueZ Li-
nux BT stack
ii libgnome-bluetooth11 ... armhf GNOME Bluetooth tools - sup-
port library
With the positive signs observed in the output so far, we can
check the presence of the Bluetooth device, which is useful for con-
nection configuration later:
$ hcitool dev
Devices:
hci0 00:02:72:CC:F4:CE
$ hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:02:72:CC:F4:CE ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:583 acl:0 sco:0 events:33 errors:0
TX bytes:898 acl:0 sco:0 commands:33 errors:0
$ sudo rfkill list all
0: hci0: Bluetooth
Soft blocked: no
Chapter 4