How to keep the data stored in flash after DFU

RE: How to keep the data stored in flash after DFU

bjorn-spockeli — Thu, 04 Aug 2016 12:33:15 GMT

As @adrian says, if there is a valid application, softdevice and Bootloader, and you update the bootloaderonly, then you will branch to the application and not the bootloader after the DFU is finished.

RE: How to keep the data stored in flash after DFU

Adrian Eggenberger — Wed, 03 Aug 2016 06:57:03 GMT

Hi, If i understand you right you updated the bootloader only over DFU. Why should it afterwards enter the DFU mode on startup? Your application probably is still valid and the bootloader should start into the application. Adrian

RE: How to keep the data stored in flash after DFU

Jorgewu — Wed, 03 Aug 2016 05:59:41 GMT

Hi , Yes ,the settings can be kept after modified DFU_APP_DATA_RESERVED. However, it cause new problem. If I just update this new DFU without others (Application and SoftDevice). My device will not enter DFU mode after update this DFU.. Is any item needed be modified?

Thanks...

RE: How to keep the data stored in flash after DFU

Adrian Eggenberger — Tue, 02 Aug 2016 16:38:36 GMT

Hi,

The bootloader implementation in the example of the SDK splits the full area between softdevice end and bootloader start into two sections (dual DFU). The upper section is erased at the beginning of the DFU to store the new firmware. This is the reason your data is erased. To preserve a user data region below the bootloader the define for DFU_APP_DATA_RESERVED should be modified.

In your case you should preserve at least three times the CODE_PAGE_SIZE to prevent erasing of the data above 0x77000.

Regards Adrian