Result code 3 - INVALID_PARAMETER error when flashing application to unit with nRF Connect

[berrag]

Hello!

I am working on updating from SDK 15.2.0 to the SDK 16.0.0 and have encountered some problems when trying to use DFU OTA to flash my unit with the application.

I'm using a nRF52832 with the latest SDK (16.0.0) and SoftDevice (s132_nrf52_7.0.1). 

There is no problem flashing the bootloader, softdevice and application using a JLink. But when trying to update using DFU OTA I encounter the above mentioned problem:

It happens just when it seems to be finished.

I have debugged the bootloader and narrowed the issue down to happening in nrf_dfu_req_handler -> on_data_obj_write_request because s_dfu_settings.progress.data_object_size = 0

[Vidar Berg]

It happens just when it seems to be finished.

 As you may know, a full sd+bl+app upgrade is performed in two steps where DFU of the app can only start after DFU of the new SD and bootloader has been completed. So I'm wondering if you got the error while updating SD+BL or if it happened during the app update?

I have debugged the bootloader and narrowed the issue down to happening in nrf_dfu_req_handler -> on_data_obj_write_request because s_dfu_settings.progress.data_object_size = 0

 Did you do the debugging on the original or the new bootloader? The new bootloader will take over handling of the DFU requests if you got to the app update..

I did not manage to replicate the error when I tested DFU from SDK 15.2.0 to SDK 16.0.0 here on a 52 DK. I have included the files I used for this test if you want to go over and compare settings. I tested with nrfutil v6.1.0.

dfu_from_SDK15_2_to_SDK16.zip

[berrag]

The error occured in the second step when the app is being upgraded. 

The debugging was made on the new bootloader, since the SD and BL has been successfully upgraded.

I'll see if I can find anything in your files that could lead me to the cause.