Peer Manager SDK15.2 Maximum number of bonded devices

Question

The content, format, and size of a device's Peer Data is determined by the application. I understand that when pm_peer_data_store() and there is not enough available flash to store the peer data, the return will be PM_EVT_STORAGE _FULL. I believe that the maximum number of peers is available flash/size of peer record. I further believe that the amount of available flash is set by #define FDS_VITURAL_PAGES in sdk_config.h. Is this all correct? 
 However, I have also been informed that the nrf52 can have a maximum of 8 peers. This seems contrary to the understanding that the maximum number of peers is a function of FDS_VIRTUAL_PAGE/peer data size. 
 Please let me know if I appear to misunderstand anything. In addition to the flash reserved for FDS. size of peer data, and the available number of indexs, Are there any other details that I need to be concerned with when adding peers? 
 Thanks, 
 Jeff

tesc · Accepted Answer

Hi, 
 Yes, the total amount of flash space is decided by FDS_VIRTUAL_PAGES (and FDS_VIRTUAL_PAGE_SIZE but the default ..._PAGE_SIZE is fine as it is the same as flash page size and I would not recommend changing it.) See the Configuration section of the FDS documentation. 
 The number 8 is probably earlier SoftDevices that had maximum 8 concurrent connections. Current SoftDevices can have up to 20 concurrent connections. 
 The amount of bonding data stored, however, depend on amount of flash space available for storing it. So that means as long as you do not have active connections, you can have as many stored bonds as you can fit in flash. 
 Please note that the FDS pages are used for all FDS storage, so that peer/bonding data competes with other FDS use with regards to storage space. When there is no space left you should do garbage collection and retry (which if I recall correctly Peer Manager will do automatically.) 
 Regards, Terje

Peer Manager SDK15.2 Maximum number of bonded devices

Top Replies