how to store bonding key manually

[makouda]

I'm using sdk10, I tried the bonding feature using device_manager and it's working. but then when I perform DFU, the bonding information is erased. I can't modify the bootlader DFU_APP_DATA_RESERVED setting because the product is already hit the market, so my only solution is to store the key manually (I need only one bonded device).

how can I sue the bonding key manuly, for my understanding, the key is stored on p_sec_keyset structure and then provide it on sd_ble_gap_sec_params_reply() in BLE_GAP_EVT_SEC_PARAMS_REQUEST.

my question is

1 - at when event the key is retrieved? whatevent triggered when I bond using nrf master control for example ?? I think it's on BLE_GAP_EVT_AUTH_STATUS event, but then how can I implement that? is there any example??

2 - how can I save the key on flash using an array of uint8_t (how it is casted)?

[Vidar Berg]

It's possible to change the DFU_APP_DATA_RESERVED size through DFU if you make some changes to the bootloader as mentioned in this thread.

Making a "device manager" is quite comprehensive, but you can find the message sequence charts for the security procedures in the SD API reference, and the device manager and peer manager shows how the SD events are handled.

[makouda]

I noticed that the device manager store the key on flash at @0x39000. on the bootlader, I kept 2 pages with DFU_APP_DATA_RESERVED, I have one page free. can I specify the address on which the device_manager stores data??.

[Vidar Berg]

The location of the bond page depends on the order the pstorage instances are registered and the start address of the bootloader (pstorage - memory layout) but you can't specify it directly.

[makouda]

yes I succedded to init the device manager where I wanted, I moved my pstorage personnal inits to dm_init and registered according to my desired sequence, thanks