ble_app_uart_c dongle with passkey

RE: ble_app_uart_c dongle with passkey

Petter Myhre — Thu, 26 May 2016 10:47:39 GMT

Then you will get the BLE_GAP_EVT_SEC_PARAMS_REQUEST event. Since you are only pairing, you can reply with sd_ble_gap_sec_params_reply(uint16_t conn_handle, BLE_GAP_SEC_STATUS_SUCCESS, NULL, NULL); Then you will get the BLE_GAP_EVT_AUTH_KEY_REQUEST event and so on...

RE: ble_app_uart_c dongle with passkey

Petter Myhre — Thu, 26 May 2016 10:47:29 GMT

When you want the central to pair you call sd_ble_gap_authenticate(). It takes two arguments, the connection handle and a ble_gap_sec_params_t struct. If you want to pair and set that you have a keyboard you fill the struct with something like this:

ble_gap_sec_params_t sec_param;
memset(&sec_param, 0, sizeof(ble_gap_sec_params_t));

sec_param.bond = false;
sec_param.mitm = false;
sec_param.lesc = 0;
sec_param.keypress = 0;
sec_param.io_caps = BLE_GAP_IO_CAPS_KEYBOARD_ONLY;
sec_param.oob = false;
sec_param.min_key_size = 7;
sec_param.max_key_size = 16;
sec_param.kdist_own.enc = 0;
sec_param.kdist_own.id = 0;
sec_param.kdist_peer.enc = 0;
sec_param.kdist_peer.id = 0;

RE: ble_app_uart_c dongle with passkey

Milan — Wed, 25 May 2016 14:49:54 GMT

Yes. It is a lot to take. I have only seen example with device manager and I don't know how to initialise security parameters without it. It seems to be simple but every time I attempt it I get lost.

For eample: do I need to use "ble_gap_sec_params_t m_sec_params;" and "sd_ble_opt_set(BLE_GAP_OPT_PASSKEY, &ble_opt);" to start with?

What do I need to change to request passkey on connection and not on bonding?

RE: ble_app_uart_c dongle with passkey

Petter Myhre — Wed, 25 May 2016 14:41:53 GMT

Yes. Is anything still unclear?

RE: ble_app_uart_c dongle with passkey

Milan — Wed, 25 May 2016 14:31:36 GMT

This is the same answer as the topic I was referring to in my question. And it was your answer too.

RE: ble_app_uart_c dongle with passkey

Petter Myhre — Wed, 25 May 2016 12:25:51 GMT

If you use static passkey the peripheral will have display set, but it is not necessary to display the passkey, because it is static. If you want to input this static passkey on the central you shoudl set that it has a keyboard. Then when you get the BLE_GAP_EVT_AUTH_KEY_REQUEST event, you use the static passkey in sd_ble_gap_auth_key_reply().

RE: ble_app_uart_c dongle with passkey

Milan — Wed, 25 May 2016 11:38:00 GMT

I think that I have mislead you slightly. It is more simple than that. Could you please update the answer to the following scenario.

Peripheral has a static passkey so no keyboard or display.

When both devices attempt to connect then central should receive a message on uart terminal requesting to enter a passkey. Once entered (such as on mobile phone or MCP) the connection is made. That simple.

Thanks for the device manager advise.

Note: My peripheral uses S100 softdevice.

RE: ble_app_uart_c dongle with passkey

Petter Myhre — Wed, 25 May 2016 11:14:49 GMT

If you want the passkey to be sent from the central to the peripheral, the peripheral should have keyboard set and the central should have keyboard or display set.

If both peripheral and central has keyboard set both sides will receive the BLE_GAP_EVT_AUTH_KEY_REQUEST event. You will have to create the passkey in the central. Send it via uart to the peripheral. Both sides use the passkey in sd_ble_gap_auth_key_reply(). See this and this MSCs.

If the peripheral has keyboard set and the central has display set. The central will receive the BLE_GAP_EVT_PASSKEY_DISPLAY event, with the passkey. See this MSC. Send it via uart to the peripheral. The peripheral will receive the BLE_GAP_EVT_AUTH_KEY_REQUEST event, use the passkey in sd_ble_gap_auth_key_reply(). See this MSC.

The Device Manager is optional software that handles pairing and bonding. If you are only doing pairing, I wouldn't recommend using it. If you are doing bonding and it covers your use case, I would recommend using it.