Home/Support/Support Forum/Bluetooth Continually times out on ConnectCore8x SBC
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Bluetooth Continually times out on ConnectCore8x SBC

0 votes
I'm running into an issue on my ConnectCore 8x where bluetooth continually times out when trying to do hcitool -i hci0 scan.

I'm running the dey3.0 (zeus) digi image for the board (have reverted to this to rule out changes I made with my own images, still no joy)

BT is present during boot:
root@ccimx8x-sbc-pro:~# dmesg | grep -i bluetooth
[ 0.148355] Bluetooth: Core ver 2.22
[ 0.148410] Bluetooth: HCI device and connection manager initialized
[ 0.148422] Bluetooth: HCI socket layer initialized
[ 0.148432] Bluetooth: L2CAP socket layer initialized
[ 0.148452] Bluetooth: SCO socket layer initialized
[ 1.839183] Bluetooth: HCI UART driver ver 2.3
[ 1.843636] Bluetooth: HCI UART protocol H4 registered
[ 2.307730] Bluetooth: RFCOMM TTY layer initialized
[ 2.312638] Bluetooth: RFCOMM socket layer initialized
[ 2.317838] Bluetooth: RFCOMM ver 1.11
[ 2.321602] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 2.326927] Bluetooth: BNEP filters: protocol multicast
[ 2.332186] Bluetooth: BNEP socket layer initialized
[ 2.337163] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 2.343114] Bluetooth: HIDP socket layer initialized


but then when i try to do hcitool scan I get errors like this:
======================
root@ccimx8x-sbc-pro:~# hcitool -i hci0 scan
Scanning ...
[ 1130.985535] Bluetooth: hci0: command 0x0401 tx timeout
Inquiry failed: Connection timed out
root@ccimx8x-sbc-pro:~#


bluetoothctl shows the device is there:
======================================
root@ccimx8x-sbc-pro:~# bluetoothctl
Agent registered
[bluetooth]# show
Controller 00:04:F3:25:33:0E (public)
Name: ccimx8x-sbc-pro
Alias: ccimx8x-sbc-pro
Class: 0x00000000
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
[bluetooth]#
=================
hci tool sees it also:
root@ccimx8x-sbc-pro:~# hcitool dev
Devices:
hci0 00:04:F3:25:33:0E

==========

bluetoothctl scan does not work either:
============================
root@ccimx8x-sbc-pro:~# bluetoothctl
Agent registered
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]#


Is this a hardware issue? if not does anyone have any idea how I can resolve it?
thanks
asked Sep 23 in Linux by kenmc New to the Community (2 points)

Please log in or register to answer this question.

1 Answer

0 votes
I was running on revB hardware. Moving to revC seems to have made this go away
answered Oct 7 by kenmc New to the Community (2 points)
...