I am running a buildroot-generated linux image (kernel 4.11.2) on a nanopi NEO air board, and I struggle to connect to my ruwido remote control.
I can see it when I scan the devices using hcitool :
# hcitool lescan
LE Scan ...
<snip>
5C:F8:21:85:8E:67 ruwido
<snip>
But I cannot get a connection (it acts like the remote is not here) :
# hcitool cc 5C:F8:21:85:8E:67
Can't create connection: Input/output error
The only thing I can do is get some information about it :
# hcitool leinfo 5C:F8:21:85:8E:67
Requesting information ...
Handle: 64 (0x0040)
LMP Version: 4.0 (0x6) LMP Subversion: 0x140
Manufacturer: Texas Instruments Inc. (13)
Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
I also cannot use bluetoothctl since it doesn't detect my interface, even though it's initialized, bluetoothd is running and the modules are loaded :
# lsmod
Module Size Used by
bnep 20480 2
hci_uart 61440 1
btbcm 16384 1 hci_uart
btqca 16384 1 hci_uart
btintel 16384 1 hci_uart
bluetooth 348160 12 hci_uart,btintel,btqca,bnep,btbcm
brcmfmac 245760 0
brcmutil 16384 1 brcmfmac
sunxi_cir 16384 0
# ps -e | grep bluetooth
553 root /usr/sbin/bluetoothd
731 root grep bluetooth
# sudo hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: F7:93:3E:74:CF:62 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:12593 acl:7 sco:0 events:292 errors:0
TX bytes:2050 acl:4 sco:0 commands:155 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'NanoPi-NEO-Air'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.1 (0x7) Revision: 0x0
LMP Version: 4.1 (0x7) Subversion: 0x2209
Manufacturer: Broadcom Corporation (15)
# bluetoothctl
Agent registered
[bluetooth]# power on
No default controller available
My question is, how do I get the remote paired and connected to the board ? It doesn't matter if it's through hcitool, bluetoothctl or another tool.
Update
Thanks to Prabhakar Lad's comment, bluetoothctl is now detecting the interface, however the problem still remains and the problem seems to have narrowed :
# rfkill unblock all
# hciconfig hci0 up
# hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: AA:AA:AA:AA:AA:AA ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:1930 acl:0 sco:0 events:101 errors:0
TX bytes:1587 acl:0 sco:0 commands:103 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'BlueZ 5.47'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.1 (0x7) Revision: 0x0
LMP Version: 4.1 (0x7) Subversion: 0x2209
Manufacturer: Broadcom Corporation (15)
# bluetoothctl
[NEW] Controller F7:93:3E:74:CF:62 BlueZ 5.47 [default]
[NEW] Device 5C:F8:21:85:8E:67 ruwido
Agent registered
[bluetooth]# agent on
Agent is already registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller F7:93:3E:74:CF:62 Discovering: yes
<snip>
[NEW] Device 5C:F8:21:85:8E:67 ruwido
<snip>
[bluetooth]# scan off
<snip>
[CHG] Device 5C:F8:21:85:8E:67 RSSI is nil
<snip>
[CHG] Controller F7:93:3E:74:CF:62 Discovering: no
Discovery stopped
[bluetooth]# pair 5C:F8:21:85:8E:67
Attempting to pair with 5C:F8:21:85:8E:67
[CHG] Device 5C:F8:21:85:8E:67 Connected: yes
[ruwido]# [ 501.424858] Bluetooth: hci0 unexpected SMP command 0x0b from 5c:f8:21:85:8e:67
[CHG] Device 5C:F8:21:85:8E:67 Connected: no
[bluetooth]# pair 5C:F8:21:85:8E:67
Attempting to pair with 5C:F8:21:85:8E:67
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
The SMP error seems to be related to bluetooth low-energy security, so am I supposed to use a different tool for pairing ?
Additional information
I actually use the busybox init system with bluetooth init scripts I found in the manufacturer's image (which is nanopi-neo-air_FriendlyCore-Xenial_4.11.2_20171113.img) and adapted so that they could be used with busybox init (the init system on the image is systemd/upstart).
So I have two files :
/etc/init.d/S35brcm_patchram_plus : patches firmware (the card uses an AMPAK ap6212 bluetooth/wifi combo module)
/etc/init.d/S38bluetooth : starts bluetoothd
I use bluez 5.47 with the following options in buildroot 2017.08.1 :
BR2_PACKAGE_BLUEZ_TOOLS=y
# BR2_PACKAGE_BLUEZ_UTILS is not set
BR2_PACKAGE_BLUEZ5_UTILS=y
BR2_PACKAGE_BLUEZ5_UTILS_OBEX=y
BR2_PACKAGE_BLUEZ5_UTILS_CLIENT=y
BR2_PACKAGE_BLUEZ5_UTILS_DEPRECATED=y
# BR2_PACKAGE_BLUEZ5_UTILS_EXPERIMENTAL is not set
# BR2_PACKAGE_BLUEZ5_PLUGINS_HEALTH is not set
# BR2_PACKAGE_BLUEZ5_PLUGINS_MIDI is not set
# BR2_PACKAGE_BLUEZ5_PLUGINS_NFC is not set
# BR2_PACKAGE_BLUEZ5_PLUGINS_SAP is not set
BR2_PACKAGE_BLUEZ5_UTILS_TEST=y
# BR2_PACKAGE_BLUEZ5_UTILS_GATTTOOL is not set
You didnt go through my complete post, you need to perform following
steps after you have done with rfkill and service restart:
a] bluetoothctl
Start the tool, this should detect the controller
b] [bluetooth]# agent on
Turn on the pairing agent
c] [bluetooth]# scan on
Let bluez detect your device, look in my post it should print you baddr (5C:F8:21:85:8E:67)
d] [bluetooth]# scan off
Turn off scanning once your device is discovered
e] [bluetooth]# pair 5C:F8:21:85:8E:67
Now pair to the device
It should now be paired.
Note: you cannot pair a device until the bluez has scanned it.
Related
I am trying connect Ubuntu pc with device. While command entered, it returns various error including rfcomm connect address already in use 、 host is down 、 rfcomm connect now in progress.
Device environment and procedure as below
Device environment
Linux 3.4
Bluez 5.19
bt addr xx:xx:xx:xx:38:A4
PC environment
Ubuntu 14.04
bluez 4
bt addr xx:xx:xx:xx:CF:F0
steps
device
insmod rfcomm.ko rtk_btusb.ko
dbus-daemon --config-file=/etc/dbus-1/system.conf
bluetoothd -C &
hciconfig hci0 up
hciconfig hci0 piscan
sdptool add SP
bluetoothctl scan on
bluetoothctl agent on
bluetoothctl default-agent
bluetoothctl trust xx:xx:xx:xx:CF:F0
bluetoothctl pair xx:xx:xx:xx:CF:F0
rfcomm bind 0 xx:xx:xx:xx:CF:F0 1
chmod 666 /dev/rfcomm0
rfcomm connect 0 xx:xx:xx:xx:CF:F0 1
PC
sdptool add SP
rfcomm bind 0 xx:xx:xx:xx:38:A4 1
chmod 666 /dev/rfcomm0
rfcomm watch 0 1
Device show Can't connect RFCOMM socket: Host is down
hciconfig -a output
hci0: Type: BR/EDR Bus: USB
BD Address: 5C:F3:70:1B:38:A4 ACL MTU: 820:8 SCO MTU: 255:16
UP RUNNING PSCAN ISCAN
RX bytes:6888 acl:88 sco:0 events:230 errors:0
TX bytes:4341 acl:84 sco:0 commands:87 errors:0
Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ 5.19'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.0 (0x6) Revision: 0xe2f
LMP Version: 4.0 (0x6) Subversion: 0x9f73
Manufacturer: Realtek Semiconductor Corporation (93)
Is any step missed in my procedure?
below steps works for me.
PC side
sdptool add SP
rfcomm -i hci0 watch 0 1 ./picocom /dev/rfcomm0
Device side
sdptool add SP
rfcomm connect 0 xx:xx:xx:xx:xx:F0 1 &
picocom /dev/rfcomm0
reference
Can't make my bluetooth work on Ubuntu.
The toggle is active.But it means nothing. Since system is not reacting on it
rfkill list output is normal:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
hciconfig -a gives the following info
hci0: Type: Primary Bus: USB
BD Address: 9C:D2:1E:0D:2F:B2 ACL MTU: 1021:4 SCO MTU: 128:2
DOWN
RX bytes:1160 acl:0 sco:0 events:62 errors:0
TX bytes:742 acl:0 sco:0 commands:62 errors:0
Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Typping of sudo hciconfig hci0 up results in:
Can't init device hci0: Invalid request code (56)
The output of hcitool dev command is empty:
Devices:
This is hcitool scan output
Device is not available: No such device
I seached for similar problems, checked their solutions if it works in my case, but failed - nothing has helped me. So I've decided to ask it here
There may be another usefull information which is not given here for now. But I don't know yet what should be provided in order to make the problem be solved easier.
Download the driver for the Mediatek MT7630E wireless card here
https://community.linuxmint.com/tutorial/view/1796
and execute the commands to compile and install the driver.
If wifi works after installing the driver but bluetooth doesn't, you should check "Readme.md" in driver file directory (/Downloads/MT7630E-release).
It worked for me in Linux Mint 18.3. Both wifi and bluetooth. But wifi only at 2.4GHz
I am using QN9021 SoC working in controller mode (BLE Bluetooth core specification v4.0). It supports some standard HCI commands as well as some vendor specific commands. I am trying to attach it in my ubuntu laptop.
The command that i have used is hciattach.
hciattach -s 9600 /dev/ttyUSBx any 9600 noflow nosleep
The hcidump shows while executing sudo hciconfig hci1 up.
HCI sniffer - Bluetooth packet analyzer ver 5.37
device: hci1 snap_len: 1500 filter: 0xffffffffffffffff
> HCI Event: Command Complete (0x0e) plen 12
Read Local Supported Features (0x04|0x0003) ncmd 11
status 0x00
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> HCI Event: Command Complete (0x0e) plen 12
Read Local Version Information (0x04|0x0001) ncmd 11
status 0x00
HCI Version: 4.0 (0x6) HCI Revision: 0x400
LMP Version: 4.0 (0x6) LMP Subversion: 0x400
Manufacturer: Quintic Corp. (142)
> HCI Event: Command Complete (0x0e) plen 10
Read BD ADDR (0x04|0x0009) ncmd 11
status 0x00 bdaddr 08:7C:BE:3E:34:BB
> HCI Event: Command Complete (0x0e) plen 11
Read Buffer Size (0x04|0x0005) ncmd 11
status 0x00
ACL MTU 0:0 SCO MTU 0:0
> HCI Event: Command Complete (0x0e) plen 4
Read Class of Device (0x03|0x0023) ncmd 11
status 0x01 class 0x000000
Error: Unknown HCI Command
The hciconfig command shows:
hci1: Type: BR/EDR Bus: UART
BD Address: 08:7C:BE:3E:34:BB ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:192 acl:0 sco:0 events:15 errors:0
TX bytes:60 acl:0 sco:0 commands:15 errors:0
hci0: Type: BR/EDR Bus: USB
BD Address: C4:8E:8F:66:3B:0E ACL MTU: 820:8 SCO MTU: 255:16
UP RUNNING PSCAN
RX bytes:2457 acl:0 sco:0 events:196 errors:0
TX bytes:24646 acl:0 sco:0 commands:196 errors:0
I would like to know how to prevent the kernel or some bluetooth kernel module to send non-supported HCI commands. Do i need to patch linux kernel source code or write a module for my SoC.
Note:- Changing the SoC or writing firmware for it to support all necessary commands is not possible for this project.
EDIT:
I know the list of HCIcommand supported by my SoC. I am thinking of creating a module to tell the kernel and daemons running to send only supported commands to the SoC. I have a look at linux kernel source (specifically at this hci_core.c). I think modifying it may solve the problem after going through this link. In this link, some developer has provided a patch to support a bluetooth dongle. The patch prevents the hci_core.c file to send a specific HCI command to a dongle of a particular manufacturer.
All i want is suggestion to resolve this problem. Do i need to modify the linux kernel or write a module for my SoC?
NOTE:- The application will run on openwrt linux.
Okay, today we found out the solution:
# hciattach -r /dev/ttyS0 bcsp 115200
Maybe it helps somebody
Helpful Tips:May this link will be helps to you.
I will give two links for more details
and for bluetooth click here
and for kernel configuration click here
I have solved this problem few years back. I was using Linux version 4.4.14 and Bluez stack 5.38. Looks like QN9021 had some bugs. The problem wasn't with Read Class of Device but with the response given by QN9021 for the command: Read Local Supported Features. Since, it's the BLE controller chip, it shouldn't be sending Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 as the response to the above command.
The issue is kernel detects it as Classic Bluetooth controller chip and then sends non-supported HCI commands to the chip. The chip should have set the 5th and 6th bits (LMP_NO_BREDR and LMP_LE bits) of the 4th byte in the Features to the command Read Local Supported Features and then kernel detects it as a BLE controller mode chip and won't send any unsupported commands to a ble controller mode chip.
Since, I can't change the firmware of the chip, I had to patch the kernel.
Here are my patches:
*** hci_event.c 2017-02-10 00:05:13.149974000 +0530
--- bluetooth/hci_event.c 2016-06-24 22:48:38.000000000 +0530
***************
*** 588,597 ****
if (rp->status)
return;
-
memcpy(hdev->features, rp->features, 8);
- hdev->features[0][4] |= LMP_NO_BREDR;
- hdev->features[0][4] |= LMP_LE;
/* Adjust default settings according to features
* supported by device. */
--- 588,594 ----
I have also tired the following command but it didn't helped:
hciattach -r /dev/ttyS0 bcsp 115200
I have two Bluetooth adapters, an old internal adapter and a new Bluetooth 4.0 adapter.
I am writing an application that uses a socket(PF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_L2CAP) to connect to a Bluetooth LE device on Linux. When I call connect() with a sockaddr_l2 {.l2_family = AF_BLUETOOTH, .l2_bdaddr = {...}, .l2_cid = L2CAP_CID_ATT, .l2_bdaddr_type = BRADDR_LE_PUBLIC}, connect fails with errno=0x38000000=939524096 Unknown error, because Linux arbitrarily chooses the old adapter that only supports Bluetooth 2.1, not Bluetooth 4.0. The solution is to bind the socket to the bd_addr of the adapter that supports Bluetooth 4.0.
Question: How to tell which adapter is the Bluetooth 4.0 adapter? hciconfig does not tell which one is the one to use; they both say BR/EDR and not LE.
$ hciconfig
hci1: Type: BR/EDR Bus: USB
BD Address: 00:25:00:F6:97:F0 ACL MTU: 1021:5 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:1074 acl:0 sco:0 events:56 errors:0
TX bytes:1462 acl:0 sco:0 commands:56 errors:0
hci0: Type: BR/EDR Bus: USB
BD Address: 00:02:72:D6:A0:BF ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:146505 acl:328 sco:0 events:4189 errors:0
TX bytes:6213 acl:215 sco:0 commands:83 errors:0
$ modinfo bluetooth | grep ^version:
version: 2.17
$ modinfo btusb | grep ^version:
version: 0.6
$ lsb_release --description
Description: Ubuntu 14.04.1 LTS
$ uname --kernel-release
3.13.0-40-generic
To answer your question there is btmgmt info which will list the HCI version (on the same line as addr), you will have to look into Host Controller Interface Assigned numbers for the meaning of the numbers, version 6 below mean Bluetooth 4.0.
# btmgmt info
hci0: Primary controller
addr 5C:F3:70:XX:XX:XX version 6 manufacturer 15 class 0x1c010c
supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy configuration static-addr
current settings: powered bondable ssp br/edr le secure-conn
name BlueZ 5.47
short name
If you need to know if the adapter support LE, you will have to look for le in Supported settings: because LE is not mandatory in bluetooth 4.0/4.1.
Try: hciconfig hci[0|1] version
I am experiencing this issue on my raspberry pi.
After a while of my python program running, it seems like one (or more) of the bluetooth adapters will "lock up" and hciconfig -a will output:
: Connection timed out (110)
root ~ # hciconfig -a
hci3: Type: BR/EDR Bus: USB
BD Address: 5C:F3:70:61:CA:D6 ACL MTU: 9000:8 SCO MTU: 64:1
UP RUNNING
RX bytes:5315773 acl:178107 sco:0 events:287995 errors:0
TX bytes:487424645 acl:527773 sco:0 commands:13454 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Can't read local name on hci3: Connection timed out (110)
The problem seems to manifest more frequently when multiple adapters are used.
The project I am working on involves using multiple (and sometimes single) USB bluetooth adapters to obex-push files to phones.
The python program that does the following things:
1.automatically detects adapters - #hciconfig -a
2.configures them - #hciconfig CMD
3.Inquires devices - #hcitool -i inq
4.Obex push files on (possibly simultaneously with other threads and other ) - bluez dbus
Some info from my system:
root ~ # modinfo btusb
filename: /lib/modules/3.12.29-1-ARCH/kernel/drivers/bluetooth/btusb.ko.gz
license: GPL
version: 0.6
description: Generic Bluetooth USB driver ver 0.6
author: Marcel Holtmann <marcel#holtmann.org>
srcversion: 61D6539530170376DCAF49C
alias: usb:v*p*d*dcE0dsc01dp01ic*isc*ip*in*
...
depends: bluetooth
intree: Y
vermagic: 3.12.29-1-ARCH preempt mod_unload modversions ARMv6
...
root ~ # pacman -Q
...
bluez 5.24-1
bluez-utils 5.24-1
...
dbus 1.8.0-1
dbus-glib 0.102-1
...
libusb 1.0.18-1
...
linux-api-headers 3.13.2-1
linux-firmware 20140217.343e460-1
linux-raspberrypi 3.12.29-1
Any ideas/or suggestions?
Is there a newer version of btusb? I looked, but I came up mostly empty handed
Note: I am somewhat of a Linux newb (though I am learning) =-)
...
PS:
These forums seem to suggest that something similar may have been fixed:
https://bbs.archlinux.org/viewtopic.php?id=183411
https://bbs.archlinux.org/viewtopic.php?id=183038
but the referenced problem appears to be specifically with the Atheros adapter chipset and I am using Broadcom chipset. Also, it appears the latest version of linux I can get for the rpi is 13.13 headers and linux-raspberrypi 13.12