I have been trying to make the Raspberry Pi work regarding Bluetooth using the command bluetoothctl
. I've been using Wheezy
before and now I started using Jessie
, because I couldn't find an image for Wheezy
anymore for my Raspberry Pi 1
after it got infected by malware.
What I want to say by this is that regarding hardware, it worked, so it is a software issue.
I've been trying to pair my Bluetooth A2DP
transmitter B-speech TX2
for quite some time with my pi-1 and my plugged in Belkin Bluetooth 4.0 USB Adapter
BT-USB-dongle and everything it says is this:Attempting to pair with 00:0A:1D:16:60:50
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
I even got that far to reach the authentication failed
but I don't remember how I managed to do this. The thing is that this is very time consuming and I would like to know, where I can get some logs
, more information about why it doesn't work and maybe some troubleshooting
regarding bluetoothctl
.
This is the bluetooth part of the dmesg
output:
[ 11.362733] Bluetooth: Core ver 2.22
[ 11.362870] Bluetooth: HCI device and connection manager initialized
[ 11.362900] Bluetooth: HCI socket layer initialized
[ 11.362919] Bluetooth: L2CAP socket layer initialized
[ 11.362971] Bluetooth: SCO socket layer initialized
[ 11.680116] Bluetooth: hci0: BCM: chip id 63
[ 11.697233] Bluetooth: hci0: BCM20702A
[ 11.699286] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 11.704076] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2
[ 11.704105] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e8.hcd not found
[ 17.110718] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 17.110733] Bluetooth: BNEP filters: protocol multicast
[ 17.110841] Bluetooth: BNEP socket layer initialized
sudo journalctl -f
("follow" mode) in a window will show you all log messages generated on the system. – cjs Apr 15 '17 at 20:22bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2
andBluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e8.hcd not found
? – Vitalis Hommel Apr 15 '17 at 20:25