DFU mesh light example face ERROR_BUSY (134)

[badidearock]

I have merged Light and DFU examples(Light_DFU), and test DFU update both blinky and Light_DFU.

It is always getting ERROR_BUSY (134) while update Light_DFU, but success with blinky zip.

RTT log:

I am using 52840, SDK: s140_v7.0.1.

Attached is all image and zip files in case you want to reproduce.

s140_nrf52_7.0.1_softdevice.hex

mesh_bootloader_serial_gccarmemb_nrf52840_xxAA.hexlight_switch_client_nrf52840_xxAA_s140_7.0.1.hexdevice_page_client_40.hexdfu_light_client_40.zipdfu_blinky_client_40.zip

[badidearock]

ERROR_BUSY (134) is from mesh_flash_in_progress().

Shall we just skip this and try again till progress is done?

Why Blinky one has no issue?

[tesc]

Hi,

What version of nrfutil is this? (Run "nrfutil version" on the command line.)

You mention SoftDevice s140 v7.0.1, but what version of the nRF5 SDK for Mesh are you using?

Regards,
Terje

[badidearock]

nrfutil version is 0.3.0.0

mesh nrf5 SDK version is 4.0.0

[tesc]

Hi,

Sorry for the long delay on this one. Is the issue still not resolved?

I have done some testing, but I am unable to reproduce the same error message as the one you report. Instead I get "Failed to upgrade target. Error is: Crashed on start packet". One way to get more information from nrfutil about what is happening, is to run with the --verbose flag, e.g. "nrfutil --verbose dfu serial -pkg <packet zip file> -p <com port> -b 115200 -fc --mesh". Then we can see the serial communication between pc and device as well, from the nrfutil output.

One significant difference between the blinky update and the light switch update is the application size, however for the nRF52840 I doubt this would be an issue because of the 1 MB Flash. (The light switch application in your update is around 140 kB.)

Regards,
Terje