The question in short form is, is there any way to not use the Flash for storing bonding information and instead do this in RAM?
For the longer explanation:
We are using the nRF52832 chip, along with SDK15.0.0 and SoftDevice S132 6.0.0.
We operate a pool issue model for our devices whereby any device can belong to any operator for the duration of a "shift", this will typically be a day however may vary depending on the customer and application.
The nRF52832 chip is a slave to our main CPU and is responsible for BLE operations as well as other low level tasks. Because we require the pool model, this means that the current bonding information in any particular chip will require transplanting to another as operators are checked out. During the duration of a "shift" the nRF chip will be powered continuously (or until the battery is deemed to low), therefore storing the bonding information in the nRF chip across power boots is useless to us (the CPU already has the relevant information stored) and is instead wearing the flash without having any practical reason for doing so. In addition we are unlikely to loose power completely so storing the bonding information in always on RAM would be more appropriate.
Is there any way of disabling the use of FDS for the peer manager and instead using RAM as the backing store for the bonding information? If there is not is there an upcoming SDK that will allow this mode of operation?
