Asus Bt-400 bluetooth cannot get working

Ask questions about Arch Linux ARM. Please search before making a new topic.

Asus Bt-400 bluetooth cannot get working

Postby dcs3spp » Wed Mar 21, 2018 6:17 pm

Hi,

I have a Raspberry Pi Model B (v1) and have a bluetooth dongle (Asus Bt-400) that I cannot seem to get working. When I run the following bleutoothctl commands no controller is found.

Code: Select all
bluetoothctl
Agent registered
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# list
[bluetooth]#


Can anyone can help get this working?

I am running armv6l Linux 4.14.27-1-ARCH and the details of the usb device when I run lsusb is :

Code: Select all
Bus 001 Device 006: ID 0b05:17cb ASUSTek Computer, Inc. Broadcom BCM20702A0 Bluetooth


I have tried the following:
1. Installed the firmware file from the AUR repository package bcm20702a1-firmware.
2. Downloaded the Asus windows driver and inspected the inf file to identify the correct hex driver file for the device. Subsequently I used hex2hcd for my device and installed the firmware file (BCM20702A1-0b05-17cb.hcd) at /usr/lib/firmware/brcm

When I run
Code: Select all
dmesg | egrep -i 'blue|firm'
I get the following dmesg output....

Code: Select all
[    1.816784] raspberrypi-firmware soc:firmware: Attached to firmware from 2018-03-16 16:17
[   25.250290] Bluetooth: Core ver 2.22
[   25.301799] Bluetooth: HCI device and connection manager initialized
[   25.432350] Bluetooth: HCI socket layer initialized
[   25.539945] Bluetooth: L2CAP socket layer initialized
[   25.657534] Bluetooth: SCO socket layer initialized
[   26.034466] Bluetooth: hci0: BCM: chip id 63
[   26.138468] Bluetooth: hci0: BCM: features 0x07
[   26.276530] Bluetooth: hci0: BCM20702A
[   26.291533] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[   28.889841] Bluetooth: hci0 command 0xfc4c tx timeout
[   36.230097] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   36.244019] Bluetooth: BNEP filters: protocol multicast
[   36.470289] Bluetooth: BNEP socket layer initialized
[   36.970529] Bluetooth: hci0: BCM: Patch command fc4c failed (-110)
[   39.209790] Bluetooth: hci0 command 0x1001 tx timeout
[   39.537967] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[   39.844410] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
[   47.209794] Bluetooth: hci0: BCM: Reading local version info failed (-110)


Sometimes I also get the following...
Code: Select all
dmesg | egrep -i 'blue|firm'
[    1.816785] raspberrypi-firmware soc:firmware: Attached to firmware from 2018-03-16 16:17
[   25.002668] Bluetooth: Core ver 2.22
[   25.066306] Bluetooth: HCI device and connection manager initialized
[   25.189457] Bluetooth: HCI socket layer initialized
[   25.289129] Bluetooth: L2CAP socket layer initialized
[   25.397880] Bluetooth: SCO socket layer initialized
[   25.793880] Bluetooth: hci0: BCM: chip id 63
[   27.908806] Bluetooth: hci0 command 0xfc6e tx timeout
[   35.353127] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   35.353140] Bluetooth: BNEP filters: protocol multicast
[   35.353177] Bluetooth: BNEP socket layer initialized
[   36.329932] Bluetooth: hci0: BCM: Read controller features failed (-110)
[   37.389283] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[   37.453147] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36


I have also tried modifying the systemd bluetooth.service to be configured and run before the networking service as suggested at https://wiki.archlinux.org/index.php/Bluetooth#Troubleshooting. Furthermore, if I run rfkill the device is unblocked.

Code: Select all
sudo rfkill list
[sudo] password for alarm:
0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no


Anybody any idea how to get bluetooth working?

Cheers
Simon
dcs3spp
 
Posts: 3
Joined: Wed Mar 14, 2018 12:41 pm

Re: Asus Bt-400 bluetooth cannot get working

Postby dcs3spp » Wed Apr 11, 2018 10:02 am

For info, I have also logged this as an issue with Raspberry Pi kernel, Issue #2494.

The dwc_otg warning messages mentioned in this post, occurs with other USB devices for kernels 4.14.x. Please refer to Issue #2408.
dcs3spp
 
Posts: 3
Joined: Wed Mar 14, 2018 12:41 pm


Return to User Questions

Who is online

Users browsing this forum: Google [Bot] and 3 guests