Out of the box I am having great difficulty connecting my beaglebone blue to any other device via bluetooth using the command line bluetoothctl module.
In brief, from the command line I can go into the bluetoothctl utility. From there I have been able to successfully pair to my phone. I can then momentarily connect to my phone with this command:
[bluetooth]# connect AC:37:43:80:C5:DD
after I verify the confirmation code from both phone and beaglebone it initially connects giving me this line:
[CHG] Device AC:37:43:80:C5:DD Connected: yes
Then 10 seconds later it notifies me that I have been disconnected with this line:
[CHG] Device AC:37:43:80:C5:DD Connected: no
Typing:
[bluetooth]# info AC:37:43:80:C5:DD
Gives:
Device AC:37:43:80:C5:DD
Name: Pixel
Alias: Pixel
Class: 0x5a020c
Icon: phone
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-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)
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: PANU (00001115-0000-1000-8000-00805f9b34fb)
UUID: NAP (00001116-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: SIM Access (0000112d-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v00E0p1200d1436
I’ve tried to connect to a couple of different devices with the same results.
Linux beaglebone 4.4.59-ti-r96 #1 SMP Tue Apr 4 17:39:20 UTC 2017 armv7l GNU/Linux
Bluetoothctl version 5.23
I ended trying the latest June 2018 beaglebone image along with the latest Bluetoothctl version. But that didn’t work either. I was getting ‘no controller available’ messages when I issued any command within bluetoothctl.
I welcome any and all suggestions for getting through this…
Thanks.