Application update fails after flashing SoftDevice

RE: Application update fails after flashing SoftDevice

Vidar Berg — Fri, 04 Dec 2020 09:54:57 GMT

Hello,

I did not modify nrfutil, the delay was that I manually started the APP update after having completed the SD+BL update.

RE: Application update fails after flashing SoftDevice

Crudo — Fri, 04 Dec 2020 08:50:29 GMT

Hello,

That is correct I'm using serial. Where exactly you added the delay? I'm assuming in the nrfutil code somewhere since SD+BL+APP fails and SD+BL in one package and APP in other works.

RE: Application update fails after flashing SoftDevice

Vidar Berg — Thu, 03 Dec 2020 12:46:45 GMT

Hello,

I saw 'pc_ble_driver_py' referenced in the log you posted, and assumed you were doing OTA DFU over BLE at first, not serial DFU. So I was testing BLE DFU. Now with serial DFU am able to replicate the the same, and the reason is that nrfutil sends the ping request before the new SD+BL have had time to get activated. Having a delay between SD+BL and the APP update fixes the problem.

RE: Application update fails after flashing SoftDevice

Crudo — Wed, 02 Dec 2020 18:52:31 GMT

Hello Vidar,

Thanks for testing it out and sending the files.

Just to confirm, the application on full_image.hex is evoking the bootloader, correct?

I've tried to update from the SDKv15.3.0 using my hex file to the SDK v17.0.2 using your zip files. They all fail with the error "Response Code InvalidObject" (same log as above).

I've tried to update from full_image.hex (flashed with JTAG) to your SDK v17.0.2 zip files. In those cases, they fail with the error "No ping response after opening COM port" (same log as above).

Finally, I also tried to update from full_image.hex (flashed with JTAG) to my SDK v17.0.2 BL+SD (the only file that works on my test setup), and unfortunately, this test also fails with the error "No ping response after opening COM port" (same log as above).

Could this be related to the nrfutil tool version?

RE: Application update fails after flashing SoftDevice

Vidar Berg — Wed, 02 Dec 2020 14:50:27 GMT

Hello,

A major Softdevice update requires a new bootloader to be included in the update as well. This makes it so that the Softdevice and bootloader are updated in one go (SoftDevice and bootloader), and thus guaranteeing that the activated bootloader always stays API compatible with the current Softdevice. Please see the "DFU package combinations" chapter of the nrfutil documentation for more details on this.

That said, I'm not sure why the BL+SD+APP update failed in your case considering that the same "BL+SD only" update got accepted. I did not manage to replicate this here. Attached below is the packages I used to test with. Maybe you could you go over those an see if there may be any relevant differences in how we create the packages (version numbers, etc)?

OTA DFU test from SDK v15.3.0 to v17.0.2

devzone.nordicsemi.com/.../1004.dfu_5F00_from_5F00_15.3.0_5F00_to_5F00_17_5F00_0_5F00_2.zip