Merging sensor/server with ble_app_uart_coexist (52840 DK). Won't finish provisioning.

[ccasebeer]

Hi

I've taken the ble_app_uart_coexists and ported it to the 52840 DK with S140 softdevice.

Works great.

Now I am trying to swap out the on/off mesh model for what is done in the sensor/server example.

However, I seem to be hanging during provisioning with the static provisioner and I don't know why.

Can I take the sensor/server/nrf_mesh_config_app.h unaltered into my project?

Any hints on debugging this?

Nordic SDK is 17.0.2

Mesh SDK is 5.0

Regards.

[tesc]

Hi,

The static provisioner is hard coded to configure each example from the SDK in a particular way, and if you change the models of the example there will be a mismatch regarding what the provisioner expects. Each example uses a unique Uniform Resource Identifier (URI), and the provisioner configures the node based on what URI it has. You can read more about that in the documentation for the Provisioner Example on Infocenter.

Before changing the provisioner example into configuring your new node, I recommend configuring the node manually with the nRF Mesh app. Once you get it to work with the smartphone app it would be easier to know what to do with the static provisioner. If anything fails when using the app, it should also be easier to pinpoint the issue.

Regards,
Terje

[ccasebeer]

I was under the impression I could not use PG-GATT provisioning (nRF Mesh IOS App) to provision:

From the ble_app_uart_coexist docs:

Software requirements

This example does not support PB-GATT for provisioning. For this purpose, use the static provisioner example: <InstallFolder>/examples/provisioner. See the provisioner example page for more information.

[ccasebeer]

Would this help at all?

This is about as far on the static provisioner as I can get:

<t:      86301>, main.c,  376, Button 1 pressed
<t:      86303>, main.c,  262, Start provisioning procedure ...
<t:      86305>, provisioner_helper.c,  326, Scanning For Unprovisioned Devices
<t:     320575>, provisioner_helper.c,  168, UUID : 0DE82BA8C4E94351A94AEA85622C3A3A
<t:     320578>, provisioner_helper.c,  171, ^RSSI: -47
<t:     320580>, provisioner_helper.c,  177, ^URI Hash: FB611461
<t:     320617>, provisioner_helper.c,  332, Stop Scanning For Unprovisioned Devices
<t:     320620>, provisioner_helper.c,  183, URI hash matched to ¹URI for Sensor Server example. Provisioning ...
<t:    1114244>, provisioner_helper.c,  300, Provisioning link established
<t:    1128577>, provisioner_helper.c,  295, Static authentication data provided
<t:    1210226>, provisioner_helper.c,  233, Provisioning completed received
<t:    1210229>, provisioner_helper.c,  238, Adding device address, and device keys
<t:    1210256>, provisioner_helper.c,  251, Addr: 0x0801 addr_handle: 0 netkey_handle: 0 devkey_handle: 2
<t:    1216136>, provisioner_helper.c,  192, Local provisioning link closed: prov_state: 2  remaining retries: 2
<t:    1216144>, main.c,  200, Provisioning successful
<t:    1216151>, provisioner_helper.c,  216, Provisioning complete. ¹URI for Sensor Server example - address: 0x0801 elements: 1
<t:    1216156>, node_setup.c,  779, Configuring Node: 0x0801
<t:    1216159>, node_setup.c,  675, Config client setup: devkey_handle:2 addr_handle:0
<t:    1216163>, node_setup.c,  430, Getting composition data
<t:    1219949>, main.c,  253, Config client event
<t:    1219952>, node_setup.c,  439, Updating network transmit: count: 2 steps: 1
<t:    1222399>, main.c,  253, Config client event
<t:    1222402>, node_setup.c,  450, Adding appkey
<t:    1227071>, main.c,  253, Config client event
<t:    1227073>, node_setup.c,  282, opcode status field: 0 
<t:    1227076>, node_setup.c,  492, App key bind: Health server on element address 0x0801
<t:    1229558>, main.c,  253, Config client event
<t:    1229560>, node_setup.c,  282, opcode status field: 0 
<t:    1229576>, node_setup.c,  511, Setting publication address for Health server to 0x0001
<t:    3195656>, main.c,  253, Config client event
<t:    3195658>, node_setup.c,  723, Acknowledged message status not received 
<t:    3195661>, node_setup.c,  727, Retry ...
<t:    3195677>, node_setup.c,  511, Setting publication address for Health server to 0x0001
<t:    5161757>, main.c,  253, Config client event
<t:    5161759>, node_setup.c,  723, Acknowledged message status not received 
<t:    5161762>, node_setup.c,  727, Retry ...
<t:    5161778>, node_setup.c,  511, Setting publication address for Health server to 0x0001
<t:    7127858>, main.c,  253, Config client event
<t:    7127860>, node_setup.c,  723, Acknowledged message status not received 
<t:    7127864>, main.c,  191, Configuration of device 0 failed.
<t:    7127866>, main.c,  192, Press Button/RTT 1 to retry configuration.

This is about as far on the sensor/server (merged to ble_app_uart_coexist)

		 Button/RTT 4) Increase mocked sensor valu<t:      24740>, mesh_main.c,  404, Device identification started
<t:      27480>, mesh_main.c,  413, Device identification stopped
<t:     121631>, mesh_main.c,  520, Successfully provisioned
<t:     121637>, mesh_main.c,  515, Node Address: 0x0801 
<t:     132805>, config_server.c,  630, dsm_appkey_add(appkey_handle:0 appkey_index:0)
<t:     137479>, config_server.c, 2553, Access  Info:
		element_index=0		model_id = 2-FFFF		model_handle=1

[ccasebeer]

Any advice appreciated on this.

I did find a couple MESH debug defines which might allow me a better debug on this problem.

Again, it seems to fail in provisioning of the new merged sensor/server merged to ble_app_uart_coexist.

PROV_DEBUG_MODE in /mesh/prov/src/prov_provisionee.c seems helpful. I'll turn that on and get a trace with that.

Thanks.

[Kaja]

Hi,

Terje is out of office at the moment, have you solved your problem? If not can you create a new case?

Best regards,
Kaja