My BLE application uses my own firmware update algorithm and bootloader, as well as the Peer Manager module. To ensure that I do not delete peer data during the update process, I need to know how the position of the peer data in flash is determined, so I can either re/define it myself or work around it.
I am aware that the Peer Manager uses FDS, and that FDS uses wear-leveling, which my application does not require.
