Losing Bonding and FDS info on DFU

[Randy Lee]

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

[Randy Lee]

no need.  none of that data is proprietary...  Or even interesting to anything but Nordic code.

[Randy Lee]

Theory: Because the bootloader isn't requiring bonding, the peer manager is deleting what bonding info it has here so when my application comes back online, there is no bonding info saved.  Is it possible that the bootloader isn't erasing the are but that other things are deleting what's there because it doesn't need it?

[Vidar Berg]

The peer manager should only delete bonding information when the application explitely requests it through pm_peer_data_delete()/pm_peers_delete(), or if you have run out of FDS space and call pm_handler_flash_clean()/pm_handler_flash_clean_on_return().

I initally assumed that pm_init() failed after DFU because that's usally what happens if the bootloader has corrupted the filesystem. Is that not what happens in your case?

[Randy Lee]

I don't think it's failing.... Looking at the code, it should hang if it does and I'm not seeing hangs.  I'll have to verify that when next I can run a debugger there but I'm pretty sure it isn't.

[Randy Lee]

This is plenty complex behaviour so let me note what I've done here....  Not sure I understand what's going on exactly..  First off, I've attached the dump you've requested.  Then let me explain what I did...3264.flash.txt