nRF Mesh example with provisioner board

[Flips]

Hey, I want to create a Bluetooth Mesh Network with the nRF52DK from Nordic. One board should be the provisioner and two more boards should be my nodes.

For my first test, I used the Zephyr examples "Mesh Provisioner" and "Mesh" on the nRF Connect 2.4.1 SDK and the 2.4.0 Connect Toolchain.

So I have flashed the "Mesh Provisioner" on one board and the "Mesh" example on two more boards.

I can add both nodes with the provisioner, and it seems that this part works too. (because when I added one node, I can't see his advertising anymore)

But when I click on the Botton1 of one of the Nodes, there should be a broadcast call and turn on the other LED, but I always get the Message "The Generic OnOff Client must be bound to a key before sending."

Normally, should the provisioner give the node this Key, so I'm not sure what I'm doing wrong.

This is the output of the Provisioner:

*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
Initializing...
Bluetooth initialized
Mesh initialized
Loading stored settings
Using stored CDB
Using stored settings
Waiting for unprovisioned beacon...
Device 544d4f0f3c300a690000000000000000 detected, press button 1 to provision.
Provisioning 544d4f0f3c300a690000000000000000
Waiting for node to be added...
Added node 0x0002
Configuring node 0x0002...
*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
Initializing...
Bluetooth initialized
Mesh initialized
Loading stored settings
Using stored CDB
Using stored settings
Waiting for unprovisioned beacon...
Device 544d4f0f3c300a690000000000000000 detected, press button 1 to provision.
Provisioning 544d4f0f3c300a690000000000000000
Waiting for node to be added...
Added node 0x0002
Configuring node 0x0002...
*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
Initializing...
Bluetooth initialized
Mesh initialized
Loading stored settings
Using stored CDB
Using stored settings
Waiting for unprovisioned beacon...
Waiting for unprovisioned beacon...

[Simonr]

Hi

I'll be looking into this case until Andreas is back from holiday. How have you configured the board files of your Bluetooth Mesh provisioner? Are you using the nRF52 DK board file where the button 1 is set as P0.13 or some other board/overlay file in your project? I don't see why that would cause a reset though. Is the reset triggered by you pressing the button 1 on the DK or somewhat later?

Best regards,

Simon

[Flips]

It was the standard board file without another overlay. The reset was later.

Flips said:

*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
Initializing...
Bluetooth initialized
Mesh initialized
Loading stored settings
Using stored CDB
Using stored settings
Waiting for unprovisioned beacon...
Device 544d4f0f3c300a690000000000000000 detected, press button 1 to provision.
Provisioning 544d4f0f3c300a690000000000000000
Waiting for node to be added...
Added node 0x0002
Configuring node 0x0002...

After device .... detected, press button 1...  | I pushed the button 

Waiting for node to be added                      | needed a second

and after that, it reset  (without pushing a button)

Kind regards, 

Philipp 

[AHaug]

Hi,

1. What revision is the 52DK you are using?
2. If you have any other devices, for instance a nRF52840DK or nRF5340DK, are you able to recreate the setup 
3. Are you able to trace where the crash occurs? I.e do some debugging to see in what function the fault occurs?

Kind regards,
Andreas