Home/Support/Support Forum/CC6 dev kit BlueTooth issue
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

CC6 dev kit BlueTooth issue

0 votes

I'm debugging Bluetooth functionality on a CC6 Jumpstart Dev Kit.
dey-bluetooth package is added to Yocto.

dmesg shows the Bluetooth software services are running:
Bluetooth: Core ver 2.22
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
Bluetooth: HCI UART driver ver 2.3
Bluetooth: HCI UART protocol H4 registered
Bluetooth: HCI UART protocol ATH3K registered
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Bluetooth: HIDP socket layer initialized

I traced the issue to the bluetooth-init script.
The call "hciattach ttyBt ath3k 4000000" step fails with:

Failed to Download configuration: Success
Can't initialize device: Success

Is this related to downloading the pst files?

In the kernel config, the following are defined:
Atheros AR300x serial support (CONFIG_BT_HCIUART_ATH3K)

Is this one needed too?
HCI_IBS protocol support (CONFIG_BT_HCIUART_IBS)

I would greatly appreciate any recommendations for debugging this issue.

asked Jun 25 in Linux by cnason1 New to the Community (0 points)

Please log in or register to answer this question.

1 Answer

0 votes
What Yocto version are you using?
Are you testing on stock images on SBC?
are there any BT related errors in bootlog?
can you try commands listed here:
Does it work for you?
answered Jun 26 by LeonidM Veteran of the Digi Community (3,520 points)
I'm not sure what Yocto version.  I can find out. We are using a custom version based on your bsp and trying to get Bluetooth working.

bluetoothctl does not list a bluetooth controller:

root@cmems-ccimx6sbc:/etc# bluetoothctl
Agent registered
[bluetooth]# scan on
No default controller available

My thought is this is because the hciattach command in bluetooth-init is failing.

One thing to note: the bluetooth-init script tries to source /etc/init.d/functions which doesn't exist on our system as it's using systemd services.  It looks like it's needed for killproc() def.  I got around it by defining killproc() in the script.

I don't see any BT related errors in the bootlog (messages).  Let me know if you'd like me to send it or post the contents. I don't see a way to attach files.

I would try this first with stock images.= and see if BT is working. Also, I would try your custom images on our SBC and see if it is still working.
Yes, the bluetooth hardware is working. I have confirmed BT functionality with the sdcard image here:

Do you have any ideas why hciattach command would fail for out custom image?  I'm going to look into pin mux.

Yes, among others, there is a pin that disables radio.
Do you know what pin that is?  Also, does that pin disable just BT or both BT and Wifi?  Wifi works fine on the system.
D13 https://www.digi.com/resources/documentation/digidocs/90001394/#reference/r_module_pinout.htm?Highlight=BT_DISABLE

 Does this script runs in startup in your images?
When I wanted to purposely disable BT on cc6 ,I would  try booting with the imx6q-ccimx6sbc-w.dtsDT instead of the imx6q-ccimx6sbc-wb.dts one. Bluetooth will be disabled.
/etc/init.d/bluez doesn't exist in both the custom image and image that has functional BT.  I have bluetooth-init and bluetooth instead.  

I see imx6q-ccimx6-wb.dtsi being included.

The version of yocto linux is 4.18