Re: [Zephyr-devel] Zephyr Based Bluetooth Mesh implementation on nRF52840-PDK boards


Steve Brown
 

It looks like you have some kind of problem on the bluez end.

I get the following on the same board.

[meshctl]# discover-unprovisioned on
set_scan_filter_uuids 00001827-0000-1000-8000-00805f9b34fb
SetDiscoveryFilter success
Discovery started
Adapter property changed
[CHG] Controller B8:27:EB:06:2E:57 Discovering: yes
Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb)
Device UUID: dddd0000000000000000000000000000
OOB: 0000


Are you sure you have a 5.47 bluetoothd running?

Steve

On Wed, 2017-11-15 at 16:29 +0530, Vikrant More wrote:
Thank very much !!

I used your suggested commands. And I got following response -

[meshctl]# discover-unprovisioned on
set_scan_filter_uuids 00001827-0000-1000-8000-00805f9b34fb
SetDiscoveryFilter failed: org.bluez.Error.InvalidArguments
Discovery started
Adapter property changed
[CHG] Controller F0:03:8C:B7:5A:18 Discovering: yes



meshctl]# provision dddd0000000000000000000000000000
Device with UUID dddd0000000000000000000000000000 not found.
Stale services? Remove device and re-discover


On Wed, Nov 15, 2017 at 2:32 PM, Steve Brown <sbrown@cortland.com>
wrote:
Hi Vikrant,

On Wed, 2017-11-15 at 13:58 +0530, Vikrant More wrote:
Hello,
I to want build Zephyr based lighting system & for testing I have
3
nRF52840-PDK boards.

I've flashed zephyr/samples/bluetooth/mesh firmware on all three
board.
They are advertising themselves as any other GATT peripheral
devices.

As per my understanding they are in unprovisioned state.

Using "NRF connect" Android app I can send data to service (Mesh
Provisioning Service) running on it.

I think this service is for provisioning purpose. Am I right ?

How to do provisioning using meshctl utility (BlueZ 5.47) ?

When I execute meshctl on my ubuntu laptop it gives me following
error -

Local config directory not provided.
Failed to parse local node configuration file local_node.json

I assume you built the bluez 5.47 from source.

The json files live in bluez/mesh. You either have to run meshctl
in
that directory or point to it with the "-c" option.

Once in meshctl, the commands:
discover-unprovisioned on
provision <Device UUID>

should get you going.

In the mesh sample the UUID is hardwired to
"dddd0000000000000000000000000000"

Steve

Join users@lists.zephyrproject.org to automatically receive all group messages.