UWP custom pairing nrf52840 with static passkey , PairingKind ？

RE: UWP custom pairing nrf52840 with static passkey , PairingKind ？

hector_leon — Thu, 28 Sep 2023 00:50:11 GMT

Hello dahai2018

How did you manage to develop WP(Universal windows platform) app for the nrf52840? I need to do the same in order to put nRF52840 in advertise mode, set a service and a characteristic. I don't know how to start.

The nRF52840 dongle appears in the windows device manager in the Ports (COM $ LPT) section as a nRF Connect USB CDC ACM (COM9) instead of a Bluetooth device.

Thanks in advance!

RE: UWP custom pairing nrf52840 with static passkey , PairingKind ？

Vidar Berg — Mon, 03 Aug 2020 07:15:05 GMT

Yes, it looks to be correct. Remember that you can use your Android phone to verify that it works

RE: UWP custom pairing nrf52840 with static passkey , PairingKind ？

dahai2018 — Sun, 02 Aug 2020 06:59:57 GMT

Yes, you are right.
The marco "SEC_PARAM_IO_CAPABILITIES" should be defined "as BLE_GAP_IO_CAPS_DISPLAY_ONLY".
In addition, the next five places are setted to SEC_MITM, is it correct?

// Add the RX Characteristic.
memset(&add_char_params, 0, sizeof(add_char_params));
add_char_params.uuid = BLE_UUID_NUS_RX_CHARACTERISTIC;
add_char_params.uuid_type = p_nus->uuid_type;
add_char_params.max_len = BLE_NUS_MAX_RX_CHAR_LEN;
add_char_params.init_len = sizeof(uint8_t);
add_char_params.is_var_len = true;
add_char_params.char_props.write = 1;
add_char_params.char_props.write_wo_resp = 1;

add_char_params.read_access = SEC_MITM; ////////// It was the SEC_OPEN
add_char_params.write_access = SEC_MITM; ////////// It was the SEC_OPEN

err_code = characteristic_add(p_nus->service_handle, &add_char_params, &p_nus->rx_handles);
if (err_code != NRF_SUCCESS)
{
return err_code;
}

// Add the TX Characteristic.
/**@snippet [Adding proprietary characteristic to the SoftDevice] */
memset(&add_char_params, 0, sizeof(add_char_params));
add_char_params.uuid = BLE_UUID_NUS_TX_CHARACTERISTIC;
add_char_params.uuid_type = p_nus->uuid_type;
add_char_params.max_len = BLE_NUS_MAX_TX_CHAR_LEN;
add_char_params.init_len = sizeof(uint8_t);
add_char_params.is_var_len = true;
add_char_params.char_props.notify = 1;

add_char_params.read_access = SEC_MITM; ////////// It was the SEC_OPEN
add_char_params.write_access = SEC_MITM; ////////// It was the SEC_OPEN
add_char_params.cccd_write_access = SEC_MITM; ////////// It was the SEC_OPEN

return characteristic_add(p_nus->service_handle, &add_char_params, &p_nus->tx_handles);
/**@snippet [Adding proprietary characteristic to the SoftDevice] */

RE: UWP custom pairing nrf52840 with static passkey , PairingKind ？

Vidar Berg — Wed, 29 Jul 2020 11:48:21 GMT

The IO capabilities are referring to what IO capabilities are available to the user. And with a static passkey, you could print the key on the final product and thus claim to have display capabilities.

RE: UWP custom pairing nrf52840 with static passkey , PairingKind ？

dahai2018 — Wed, 29 Jul 2020 07:45:45 GMT

OK, but from the literal meaning of a macro，I think SEC_PARAM_IO_CAPABILITIES should be defined as BLE_GAP_IO_CAPS_KEYBOARD_ONLY or BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY. I will try it in the weekend.

RE: UWP custom pairing nrf52840 with static passkey , PairingKind ？

Vidar Berg — Wed, 29 Jul 2020 07:32:26 GMT

I think the fact that it works with android indicates that your nrf device is correctly set up for passkey pairing and that the problem is on the windows side. So I think it would be better if you ask Microsoft about this. I don't have experience with windows app dev unfortunately.

RE: UWP custom pairing nrf52840 with static passkey , PairingKind ？

dahai2018 — Wed, 29 Jul 2020 07:05:10 GMT

yes, the passkey pairing works with Android phone by providing an input PIN dialog box, but didnot in win10 UWP. The UWP app cannot register PairingRequestedHandler, for the nrf52840 device do not support "providepin" option.

RE: UWP custom pairing nrf52840 with static passkey , PairingKind ？

Vidar Berg — Wed, 29 Jul 2020 06:57:47 GMT

You should set it to "BLE_GAP_IO_CAPS_DISPLAY_ONLY when using static passkey. Have you tried to see if the passkey pairing works with an iOS or Android phone?

RE: UWP custom pairing nrf52840 with static passkey , PairingKind ？

dahai2018 — Wed, 29 Jul 2020 06:52:45 GMT

yes, I have defined SEC_PARAM_IO_CAPABILITIES as BLE_GAP_IO_CAPS_DISPLAY_ONLY, and configured the static passkey with the sd_ble_opt_set() function.

oh, should I defined SEC_PARAM_IO_CAPABILITIES as BLE_GAP_IO_CAPS_KEYBOARD_ONLY or BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY to get UWP "providepin" option ?

RE: UWP custom pairing nrf52840 with static passkey , PairingKind ？

Vidar Berg — Wed, 29 Jul 2020 06:34:28 GMT

Sorry for the delayed response. I think your description is clear enough. On the nRF side, have you defined SEC_PARAM_IO_CAPABILITIES as BLE_GAP_IO_CAPS_DISPLAY_ONLY, and did you configure the static passkey with the sd_ble_opt_set() function?

// Setting a static passkey

    ble_opt_t opt;

    opt.gap_opt.passkey.p_passkey ="123456"

    err_code = sd_ble_opt_set(BLE_GAP_OPT_PASSKEY, &opt);
    APP_ERROR_CHECK(err_code);

RE: UWP custom pairing nrf52840 with static passkey , PairingKind ？

dahai2018 — Wed, 29 Jul 2020 01:03:24 GMT

Didn't I describe the problem clearly? Who can reply?

I haven't got a technical response yet