On an armstonea9r2board, I'm trying to pair a bluetooth headphones.
On buildroot, I've enabled the following packages:
- target packages --> Networking applications --> bluez-utils 5.x
- target packages --> Networking applications --> bluez-utils 5.x --> build CLI client
- target packages --> Audio and video applications -> bluez-alsa
- target packages --> Audio and video applications -> bluez-alsa --> hcitop
- target packages --> Audio and video applications -> bluez-alsa --> rfcom
compilation and deployment on the board is successful.
I can successfully raise the hci0interface (hciconfig hci0 up) and scan for devices (hcitool scan); I can also read both the name of the device and the device info through the commands: hcitool name <device address> and hcitool info <device address>, but seems I cannot pair the headphones (hcitool cc <device addr>), as -even if the command doesn't return any error, any next command requiring an active connection raises an error (such as hcitool rssi).
Moreover, when I try to test the headphone through bluealsa-aplay the following error is raised:
bluealsa-aplay: BlueALSA connection failed: No such file or directory
and this confirm the missing connection.
When launching bluealsa (which is the bluetooth daemon, right?), the following error is raised:
bluealsa: Couldn't get managed objects: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
Looking into the /etc/dbus-1/system.d path, I can see a bluetooth.conf file allowing for the security policies of the bluetooth daemon, but Googling the above message I've found nothing applicable for an embedded system (many user reported the needs to add users into specific groups, and so on...)
Trying to tackle the problem with a completely different approach, I saw in many posts the usage of the bluetoothctl command to pair devices, which in my case opens successfully a prompt interface, but doesn't allow to enter any command.
On forums this behavior is reported to be connected with the bluetooth daemon not started (specifically bluetoothd), that effectively is missing from the active processes and can't also be found on the executable deployed on the board (which is bluealsa according to the first approach).
I've searched a way to get bluetoothd deployed on the board through buildroot, but I can't find any way.
I'm a newbie on this topic: I admit I don't have a full understanding on what is happening and surely I'm missing some steps...
Do you have any hints on how to pair a headphone and stream some audio through bluez-alsa (or other framework?)
Thanks and BR,