This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Losing Bonding and FDS info on DFU

Running 52840 with SDK 15.3, SD140 on SES Ive got an application that has a bootloader on it running DFU.  Everything works during DFU correctly but when I get into the application (same SDK version), I've lost my bonding and other FDS information. 

Application is operating peripheral only, non-bonded DFU.  The application itself uses peer manager with whitelists and storing bonding information.

There are several tickets running around here from other SDK versions on the subject and I'm not finding anything that is helping here. 

In the nrf_dfu_types.h file I've got the DFU_APP_DATA_RESERVED set at default of 3 pages which is what the FDS is set at as well so this should match up.

Maybe there is some other setting to turn on saving the area at all that isn't?

Thanks

Parents
  • Hello,

    The bootloader should not be able to write into the application data as long as the NRF_DFU_APP_DATA_AREA_SIZE setting in your bootloader's sdk_config file corresponds to the size of your FDS area allocated by the app. So please double-check that  NRF_DFU_APP_DATA_AREA_SIZE  is indeed set to 12288 in your bootloader project. 

    I see you mentioned using the DFU_APP_DATA_RESERVED define, but please note that this symbol was renamed to NRF_DFU_APP_DATA_AREA_SIZE  in this SDK version.

    Best regards,

    Vidar

  • yes, This is set in the sdk_config.h file for the bootloader:

    #define NRF_DFU_APP_DATA_AREA_SIZE 12288

    the SDK file nrf_dfu_types.h has:

    #define NRF_DFU_APP_DATA_AREA_SIZE (CODE_PAGE_SIZE * 3)

Reply Children
Related