DFU SoftDevice s140 from 6.1.1 to 7.0.1

RE: DFU SoftDevice s140 from 6.1.1 to 7.0.1

bjorn-spockeli — Sun, 08 Mar 2020 08:59:40 GMT

Happy to hear that you were able to successfully perform a DFU. You are correct, the bootloader start address cannot change as this start address is "hardcoded" in the UICR and/or in the MBR when you flash the original bootloader and is used by the MBR to forward interrupts to the bootloader. This is not the case with the application as the SoftDevice will forward interrupts to the application as long as the application is placed directly after the SoftDevice.

Best regards

Bjørn

RE: DFU SoftDevice s140 from 6.1.1 to 7.0.1

rpasichnyk — Fri, 06 Mar 2020 20:42:13 GMT

Thank you Bjørn!

I was able to perform DFU according to your instructions. I was not sure if this was possible and worth the effor, since I noticed that application FLASH start address has changed to 0x27000 with new SoftDevice. But apparently this is OK. I was not sure because I know that bootloader start address can not be changed, I assumed the same applies to application (it doesn't).

RE: DFU SoftDevice s140 from 6.1.1 to 7.0.1

bjorn-spockeli — Thu, 05 Mar 2020 13:00:45 GMT

HI Roman,

its fully possible to update from the S140 v6.1.1 to the S140 v7.0.1, but you will have to update the application as well as the bootloader so that they are compatible with the new SoftDevice. Otherwise you may "brick" your device if the bootloader or application uses the incorrect SoftDevice API. So you need to do the following:

Re-compile your application to use the S140 v7.0.1 headers and adjust the linker script to accomodate the larger SoftDevice
Re-compile your bootloader to use the S140 v7.0.1 header or use the bootloader from SDK v16.x.x
Create a combined SoftDevice( S140 v7.0.1), Bootloader( from step 2) and Application image( from step 1), using nrfutil.

Best regards

Bjørn