Update Softdevice via DFU (2025 update)

[ms360]

I'm wondering if this feature is still supported. 
I'd like to update some devices from SD 5 to 7.1
I saw an old post and wanted fresh info. 

 Update Softdevice via DFU 

If this is the same, I can

• make a new bootloader with SD 7.1 
• create a DFU package for app + bootloader + SD 7.1

and that's still the solution ? 

Thanks!

[ms360]

I would have to build a debug bootloader from scratch on a v14.2.0 SDK. 
The thing is I'm stuck with whatever this deployed version is, so if its not a mostly stock bootloader, I may run into some problems. 

I'll reach out to the original engineer and see if I can get some more information. 

[Hieu]

Here is the v14.2.0 SDK bootloader project, with the nRF52832 Debug target that I have modified to start at 0x71000 (where the v17.1.0 debug-build bootloader starts) and log over UART. Perhaps that would help?

p01_bl-dbg_uart-addr_shifted.zip

As for the application, I think either yours or the ble_app_buttonless_dfu example would work. Perhaps your project would be better for reproduction?

[ms360]

My bootloader starts at 0x73000. I don't think this will work. 
I'm happy to share my project privately off forum. 

[Hieu]

Huh, interesting. That is the default address of the bootloader with debug options and RTT logging enabled. Do you think your bootloader maybe already have logging?

In any cases, unless your application has some data between 0x71000 and 0x73000, the bootloader starting at 0x71000 shouldn't really matter.

If necessary, you can also change the start address back to 0x73000. It just means that we can't test with the debug version of the SDK v17.1.0 bootloader.
Here is the same project I edited to start at 0x73000.

p01_bl-dbg_uart.zip

As for sending over the application, that works too, as long as it can run on a nRF52840 DK. You can open a private case, with a link to this one, and ask it to be assigned to me.

I am out of office on Monday but will return on Tuesday.