Jump to content

CSR Bluetooth 2.0 dongle


The_Loko

Recommended Posts

Anyone using any of those cheap bluetooth dongles?

 

I have been trying to get it working but when connecting it freezes the OPi PC (the heartbeat led stops blinkng). The dongle is fine as it works on other Linux and Windows computers.

 

This is the lsusb output:

Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 14b2:3c22 Ralink Technology, Corp. Conceptronic C54RU v3 802.11bg Wireless Adapter [Ralink RT2571W]
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It seems that no matter what usb port I use it's detected as usb 1.1 device, so maybe this is why it fails? As it freezes the board there is not any relevant log saved.: 694, stack limit = 0xee1c42f8)

 

Today after pairing a device, I received the "sunxi oops" attached as output on bluetoothctl, it didn't froze the board as the led was still blinking but it was unresponsive and lost the network connection.

 

Any idea what's producing this? I think it could be the btusb driver because on 3.4 kernel it had some CSR dongles blacklisted.

sunxioops.txt

Link to comment
Share on other sites

I try to use a CSR bt dongle on bpi m2+ but I cannot make it register by bluetoothd :

 

hciconfig show hci0 device, I can make it discover by another bt host, but bluetoothctl does not see it. When it start, bluetoothd complains with the following message in daemon.log :

 

localhost bluetoothd[3278]: Failed to read info for index 65535: Invalid Index (0x11)

 

(Error comes from adaptor.c in bluez source)

 

 

If I unload bcmdhd module bcmdhd , error change to :

 

localhost bluetoothd[3373]: Failed to read info for index 16: Invalid Index (0x11)

 

rfkill list also sunxi-bt device but I don't know how to disable it and I Cannot find in kernel config an option to buid or not a driver for on board bt.

 

Is it a mess in drivers or a bug in bluez5 ? (forums already mention such problems but without any response as usual with bluez bugs - they suggest endian pb - recompiled bluez with no change ...)

 

(My kernel is the last one with patch for enabling g_ether)

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines