Mesh: problems during provisioning

[bart]

Board: PCA10040

Chip: NRF52832

SD132

SDK 15.2.0

SDK Mesh 3.1

I have added the light switch server example into my own app. I tried to run the quick demo, with 1 provisioner, 1 client, 3 example servers, and my own app. What i see is that there's often one server node that keeps failing to be provisioned. This time it's the one with my own app, and i enabled provioning logging:

<t:      52691>, prov_bearer_adv.c,  400, PB-ADV: context at 0x20006D4C added to bearer
<t:     323524>, prov_bearer_adv.c,  849, PB-ADV: Link opened.
<t:     325598>, prov_bearer_adv.c,  798, Received ACK for [ppdu1]
<t:     460162>, prov_bearer_adv.c,  739, Received start segment while already in RX mode.
<t:     599240>, prov_bearer_adv.c,  400, PB-ADV: context at 0x20006D4C added to bearer
<t:     599244>, prov_bearer_adv.c,  904, PB-ADV: Link closed.
<t:     656437>, prov_bearer_adv.c,  849, PB-ADV: Link opened.
<t:     724685>, prov_bearer_adv.c,  798, Received ACK for [ppdu1]
<t:     798715>, prov_bearer_adv.c,  798, Received ACK for [ppdu3]
<t:     799752>, prov_bearer_adv.c,  400, PB-ADV: context at 0x20006D4C added to bearer
<t:     799756>, prov_bearer_adv.c,  904, PB-ADV: Link closed.
<t:     844036>, prov_bearer_adv.c,  849, PB-ADV: Link opened.
<t:     912585>, prov_bearer_adv.c,  798, Received ACK for [ppdu1]
<t:     981925>, prov_bearer_adv.c,  739, Received start segment while already in RX mode.
<t:    1054041>, prov_bearer_adv.c,  400, PB-ADV: context at 0x20006D4C added to bearer
<t:    1054045>, prov_bearer_adv.c,  904, PB-ADV: Link closed.

Maybe related, at some point the mesh crashed every time at: bearer_event_handler(), NRF_MESH_ASSERT(p_seq->event_pending);

After i erased the flash and started over, the crash was gone though..

*edit*

The crash is back, i have some more logs:

<t:      53670>, prov_bearer_adv.c,  400, PB-ADV: context at 0x20007514 added to bearer
<t:     438726>, prov_bearer_adv.c,  849, PB-ADV: Link opened.
<t:     441656>, prov_bearer_adv.c,  734, Got the next segment before an ACK for our own (1, 1)
<t:     505696>, prov_bearer_adv.c,  955, TX RETRY: [ppdu1]
<t:     507237>, prov_bearer_adv.c,  734, Got the next segment before an ACK for our own (1, 1)
<t:     571887>, prov_bearer_adv.c,  955, TX RETRY: [ppdu1]
<t:     572823>, prov_bearer_adv.c,  798, Received ACK for [ppdu1]
<t:     710024>, prov_bearer_adv.c,  739, Received start segment while already in RX mode.
<t:     777157>, prov_bearer_adv.c,  739, Received start segment while already in RX mode.
<t:     845014>, prov_bearer_adv.c,  739, Received start segment while already in RX mode.
<t:     850921>, prov_bearer_adv.c,  798, Received ACK for [ppdu3]
<t:     851357>, prov_bearer_adv.c,  400, PB-ADV: context at 0x20007514 added to bearer
<t:     851361>, prov_bearer_adv.c,  904, PB-ADV: Link closed.
<error> app: Fatal error

[Bjørn Kvaale]

Sorry for the delayed response. Is it always the node with your own FW application that fails to get provisioned by the provisioner example? Or does it vary which of the nodes fails to get provisioned? Is your own app based on the nRF5 SDK? If so, it may be useful to take a look at this documentation to make sure you have integrated mesh correctly into your own app.

Also, when you say the mesh crashed, in which node does it crash? Is it in the provisioner code? Or on another one of the nodes? Is it always the same node that crashes?

[bart]

From what I remember, it was a random node that failed to get provisioned.

The crash always happened at the node with my own app.

It's based on the nRF5 sdk indeed, had read the documentation.

I moved on to self provisioning, so i can't test any more right now.