Saving bonds across a reset

[Caycee]

My pairing is working and shown as bonded on Android, but when the DK is reset, the bond is no longer valid. 

In studying saving of bond information, I find references to Device Manager and Peer Manager which don't seem to appear anywhere in zephyr builds. 

In my .config file under "Device Management"  CONFIG_MCUMGR is enabled and I find nothing of interest which is not already enabled.

I have NVS enabled to store just a single parameter (for now) which works fine.

All my 'SETTINGS' params are:

CONFIG_BT_SETTINGS=y
CONFIG_BT_SETTINGS_CCC_LAZY_LOADING=y
CONFIG_BT_SETTINGS_CCC_STORE_ON_WRITE=y
CONFIG_BT_SETTINGS_USE_PRINTK=y
CONFIG_PM_PARTITION_SIZE_SETTINGS_STORAGE=0x2000
CONFIG_ZTEST_MULTICORE_DEFAULT_SETTINGS=y
CONFIG_SETTINGS=y
# CONFIG_SETTINGS_RUNTIME is not set
CONFIG_SETTINGS_DYNAMIC_HANDLERS=y
CONFIG_SETTINGS_FCB=y
# CONFIG_SETTINGS_FS is not set
# CONFIG_SETTINGS_NVS is not set
# CONFIG_SETTINGS_CUSTOM is not set
# CONFIG_SETTINGS_NONE is not set
CONFIG_SETTINGS_FCB_NUM_AREAS=8
CONFIG_SETTINGS_FCB_MAGIC=0xc0ffeeee
# CONFIG_SETTINGS_SHELL is not set

[Einar Thorsrud]

Hi,

There are a few more configs that are needed for bonding. Typically, you will need these configs:

# Enable bonding
CONFIG_BT_SETTINGS=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS=y

You can refer to the implementation of the Bluetooth: Peripheral UART to see a full sample.