ota dfu bootloader+softdevice+app

[Stas]

Hello! I couldn't find somewhere on devzone, github how to update bootloader(bl), softdevice(sd), app together. The deal is I have some devices with prior version of sd and bl based on experimental buttonless app from sdk_13 (sd 3), now I want update to app based on buttonless example from sdk_14 (sd 5).

this instruction on github only tells that we need to do it with 2 connections.

in this blog I've found how to update only app + sd

Could someone explain that moment step by step. Thanks for helping in advance

[Hung Bui]

Hi Stas,

The reason I mentioned in the blog that you can update the softdevice and application is that, there will be still 2 phases, first updating the softdevice (and bootloader most likely), then after the softdevice+bootloader running, updating the application.

It's just the DFU master make the process transparent as it's just one shot, but it's actually 2 connections under the hood.

When you change the softdevice, and if it's major change (from SD v3 to SD v4 for example) you need to update the bootloader as well, because old bootloader won't work on new softdevice.

@Nguyen Hoang Hoan: It's fine now to update major softdevice version as long as the MBR are the same. It was the limitation long ago where the location of the application ( size of softdevice) is hard coded in UICR.

[Rita]

Hello all, I have the same problem to update major softdevice version. I want to update S132 v3.0 -> S132 v5.0, I think the location of the bootloader is the same. Now I meet the situation is I can update the SD+AP+BL with the nRFconnect APP and the APP doesn't show any error and update to 100%. But after that, I can't scan any device anymore. Also I try to update only SD+BL. The result is the same. How can I do next step? Thanks.

[Hung Bui]

Please create a new case, with more information, sniffer trace and debug log on the bootloader.