Problem with Mesh V5.0.0 lpn example DFU function

[Hik]

Hi,all

I'm develop with the nRF SDK for Mesh v5.0.0 and a nRF52832 DK V17.0.2 , with the LPN example.
I want to enable BLE DFU support so I followed the instructions from the infocenter
The problem is when I flash the application by SES ,it work fine,but when I update app by phone transmit zip package, the application gets stuck in the initialization process and I get mesh assert in the RTT log as below

00> <t: 0>, main.c, 580, ----- BLE Mesh LPN Demo -----
00> <t: 11577>, app_error_weak.c, 105, Mesh assert at 0x0002E37C (:0)

As this topic said
devzone.nordicsemi.com/.../mesh-lpn-example-ble-dfu
I found Mesh V5.0.0 already patched bladdr_fix_patch.patch
but problem still exsit
I'm try to disable PERSISTENT STORAGE, problem did fixed ,but I need enable PERSISTENT STORAGE, how to resolve this
Is there still have a dfu bug with Mesh V5.0.0 lpn example?

Appreciate for any reply.

[Hik]

My operation procedure is:

1、flash app+sd by SES Targe ->download lpn project

2、use lpn_example.hex for generate bootloader setting

3、merge bl_setting.hex and bootloader.hex(generate by nRF5_SDK_17.0.2\examples\dfu\secure_bootloader)

4、flash merged bl+bl_setting.hex and reset board, it works fine

5、change lpn's led blink frequncy to 1Hz(default 5Hz) and build

6、generate app_dfu_pack.zip with changed_lpn_example.hex

7、trigger board into DFU mode 

8、send app_dfu_pack.zip , at last the connect_app show download successfully

then application get stucked and RTT show Mesh assert

Am I doing it right？

[Hik]

I resolved it.

I try to regenerate private.key and rebuild security_boot_loader_example.hex

finally,alfter dfu update,it works fine.

I copyed private.key and security_boot_loader_example.hex from other project early ,not generate it.

maybe that's reason

[Hieu]

Hi Hik,

It's good to know that the issue has been resolved.

I would like to inform you that the nRF5 SDK for Mesh is currently in maintenance mode, and we do not recommend it for new projects. If possible, please consider using our nRF Connect SDK.

For more information, please see:  nRF Connect SDK and nRF5 SDK statement .

Hieu