Bluetooth support in new firmware for WP77xx R11 seems to be not complete:
root@swi-mdm9x28-wp:~# bluetoothctl
process 2559: arguments to dbus_connection_get_object_path_data() were incorrect, assertion “connection != NULL” failed in file …/…/dbus-1.10.10/dbus/dbus-connection.c line 5904.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Aborted
root@swi-mdm9x28-wp:~#
could you please provide patch?
The dbus recipe requests that a messagebus user and group and a netdev group be added into the system. Unfortunately, the meta-swi/common/recipes-core/initscripts/initscripts_1.0.bbappend file inserts static copies of the /etc/passwd, /etc/groups and other files into the rootfs and thus ignores the instructions from the recipes. As a result, the users/groups required by dbus were not added to these files because it wasn’t clear to me that it was necessary. I have reported this problem, and posted a patch which restores the expected behavior in yocto, but it’s stalled out in review.
what should we do to fix it and make it working on WP7702 ?
We have a workaround in our application where we fire off a script that manually starts dbus and bluetooth daemons. It is not pretty. Ideally we’d like to rely on the init scripts, but the workaround is serving us for now.
could you please share your workaround? we need to make it working in any possible way. thank you!
Take a look at this: https://github.com/mangOH/meta-mangoh/tree/master/recipes-core/initscripts
there is one file with one line. how this can be applied to WP7702 R11 ?
There are also the files in here: https://github.com/mangOH/meta-mangoh/tree/master/recipes-core/initscripts/files/etc
Basically, you need to create your own yocto layer at a higher priority than meta-swi or you need to copy the files from the etc folder linked above over top of the files in the etc folder of the initscripts recipe.