Hi Brian,
Thanks for the response. Yes, I am using PB-GATT barrier. With
bluetooothd running, I am able to provision my device.
I also tried mesh-cfgclient but unsuccessful. I launched the shell with
mesh-cfgclient (with bluetooth-meshd running) and I gave create command
in the shell. I see segmentation fault. Any steps I am missing?
Is mesh-cfgclient only for provisioning or also for sending mesh
messages also?
Rgds,
Venkat.
On 28/11/19 4:22 am, Gix, Brian wrote:
Hi Venkat,
Are you attempting to provision a device that requires PB-GATT provisioning? If so, the bluetoothd daemon must be up and running. However, this tool is old, and will probably be deprecated at some point.
However most Mesh devices should support Advertising based provisioning.
The Mesh daemon (Bluetooth-meshd) and the mesh-cfgclient tool (in the tools directory) has been undergoing modification even since v5.52, so you will want to checkout the tip.
./tools/mesh-cfgclient is the tool most appropriate for mesh development today.
On Nov 26, 2019, at 8:16 PM, Venkat Vallapaneni <vallapaneni@xxxxxxxxxxxxxx> wrote:
Hi,
I am trying to use bluez 5.52 for provisioning a bluetooth mesh capable device. When I gave provision <uuid>, I get this below error. Please let me know what I am missing.
I am using ell 0.26 on ubuntu 18.04. I am able to provision successfully with bluez 5.50.
AcquireWrite success: fd 8 MTU 69
GATT-TX: 03 00 10
*sendmsg: Socket operation on non-socket*[Zephyr]#
Rgds,
Venkat.
