static passkey with SDK 10

RE: static passkey with SDK 10

FormerMember — Mon, 04 Apr 2016 12:29:50 GMT

The tutorial "migrating to peer manager" may also be useful.

RE: static passkey with SDK 10

FormerMember — Mon, 04 Apr 2016 12:28:03 GMT

As you probably know, there is a UART central example in the SDK, ble_app_uart_c (without bonding implemented). This tutorial shows how to include the device manager module in an project. However, the device manager module was replaced by the peer manager in SDK 11. But I would think that adding the peer manager module to a project should be done approximately the same way as adding the device manager module to a project.

The experimental central example ble_app_rscs_c uses the peer manager module, it can be useful to take a look that example as well.

RE: static passkey with SDK 10

Punit — Mon, 04 Apr 2016 10:58:32 GMT

Thanks for the answer Kristin.Now i atleast understand connection-bonding.I will try to use the SDK11 for my application.My other question is how to setup a master[NUS] on the nRF51-DK with a static passkey mechanism.I just need a headstart and i will try to implement it myself.....

RE: static passkey with SDK 10

FormerMember — Mon, 04 Apr 2016 10:11:39 GMT

You can implement static passkey by following the this message sequence chart.

For development, I would recommend you to use the latest version of the SDK, SDK 11. Also note that the module that handles bonding, the peer_manager, is not included in the ble_app_uart example in the SDK.

Connecting: Initiating a connection sets up a connection between two devices.

Bonding: Setting up an encrypted link between two devices. When bonding, the encryption information is stored in the devices so that there will not be any key exchange upon a re-connection.

2) When setting up the characteristics, you have to set the security required to interact with that characteristic using the macros BLE_GAP_CONN_SEC_MODE_SET_MACROS.