Mesh Provisioning Data is lost after BLE DFU

[mesh777]

After performing firmware update (of application) using nRF Connect app, device running Mesh becomes unprovisioned.

Mesh SDK is v5.0.0, nRF52 SDK 17.0.2.

Bootloader looks similar to \examples\dfu\secure_bootloader\pca10040_s132_ble.

Is provisioning data stored in Application Data region? How to check its location?

There is also NRF_DFU_APP_DATA_AREA_SIZE 16384 defined in bootloader project, however I do not see where it is used.

Is it possible to read out (dump) application data region to compare content before and after device update?

[Elfving]

Hello!

Is provisioning data stored in Application Data region? How to check its location?

Take a look at this response by Terje describing it. More info on the DSM can be found here.

There is also NRF_DFU_APP_DATA_AREA_SIZE 16384 defined in bootloader project, however I do not see where it is used.

I will have to get back to you on that.

After performing firmware update (of application) using nRF Connect app, device running Mesh becomes unprovisioned.

For secure DFU bootloader I believe this is the setting you are looking for.

Is it possible to read out (dump) application data region to compare content before and after device update?

Yes, you can use nrfjprog for this. 

nrfjprog --readcode dump.hex

Best regards,

Elfving