fds_init returns FDS_ERR_NO_PAGES after a DFU upgrade

[Aurele]

Hello,

We are facing recently an issue that is very weird because it is not occuring every time. Indeed, the issue occurs after a DFU update, sometimes when the application starts the FDS, it returns a FDS_ERR_NO_PAGES. A a result, it prevents the device from using its whitelist and other things like that. The FDS is using 32 virtual pages. 

Here a mapping of our application : 

Bootloader settings                             0x0007 F000 - 0x0008 0000 (4 kB)

MBR parameter storage                     0x0007 F000 - 0x0008 0000 (4 kB)

Bootloader                                          0x0007 0000 - 0x0007 E000 (56 kB)

FDS                                                    0x0005 0000 - 0x0006 FFFF (128 kB)

Application area (incl. free space)      0x0002 6000 - 0x0004 FFFF (168 kB)

SoftDevice                                          0x0000 1000 - 0x0002 6000 (152 kB)

Master Boot Record (MBR)                0x0000 0000 - 0x0000 1000 (4 kB)

Is the DFU able to corrupt my FDS ?

If you have any idea about this issue, feel free to share ;)

Best regards,

Aurélien

[tesc]

Hi,

In order for data to be kept through DFU, you need to configure DFU_APP_DATA_RESERVED in nrf_dfu_types.h. See the Preserving application data section of the DFU bootloader documentation for details.

Regards,
Terje

[Aurele]

Hello tesc

Thank you very much for your answer, indeed it seems ti was what you have said.You 've saved our 30 prototypes that was needing an update.

As a result, firstly i update the bootloader and then i update the application and all seems to work.

Thank's again,

Best regards,

Aurélien