Modifying NUS - Make it bond with smart phones

RE: Modifying NUS - Make it bond with smart phones

run_ar — Fri, 26 Feb 2016 14:55:36 GMT

About BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&cccd_md.read_perm);
If I remember correctly CCCD read permission has to be open.

RE: Modifying NUS - Make it bond with smart phones

MANGO — Wed, 24 Feb 2016 08:11:43 GMT

@Hung Bui, about changing the BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM option,

should I applyBLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM to other services?

For instance, I'm planning to use BAS or DIS with NUS.

Applying

BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&bas_init_obj.battery_level_char_attr_md.cccd_write_perm);

BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&dis_init_obj.dis_attr_md.read_perm);

will do the work?

// Edited (Feb, 25, 2016)

I took a reference.

At ble_nus.h. I made some changes (check my question script.)

However, rx_char_add returns NRF_ERROR_INVALID_PARAM (number 7).

RE: Modifying NUS - Make it bond with smart phones

MANGO — Wed, 24 Feb 2016 08:02:11 GMT

Hi Hung Bui, I asked this question quite a long time ago. I'm trying this now.

About iOS/Android system won't show your device and bond to your device if they are not HID device. You would need to have an app for that,

you mean that, even though I change the code, NUS cannot be bonded without using a custom app for the NUS?

For instance, suppose I changed the code to make the NUS bond.

Since the nRF UART 2.0 App is available, the app will discover and connect (bond) with this peripheral.

However, after disconnecting it, do you mean that this peripheral cannot be connected automatically without the app?

As you know, HID device bonds to the central (phones) directly without choosing them from the settings tab, if they had exchanged their IRK.

Even though I change the code from the NUS example, this "auto connection" won't work?

RE: Modifying NUS - Make it bond with smart phones

Hung Bui — Tue, 07 Jul 2015 09:48:53 GMT

Yes, I meant "not HID". On Android, they changed that from time to time, and also depends on the manufacturing vendors. As far as I remember Samsung device won't show it if it's not HID or bonded. But maybe in the newer version 5.1.1 they may have it.

So it's not guaranted that your device will always show up in the Bluetooth setting if it's not bonded.

RE: Modifying NUS - Make it bond with smart phones

Hung Bui — Mon, 06 Jul 2015 10:02:13 GMT

@Mango:

Pair means encrypt the link, and bond is storing the key so next time the link can be re-encrypted. If the device is not bonded, you won't see it in the Bluetooth setting. NUS by default doesn't require bonding so there will be no bond by default. On the other hand, HID keyboard requires bonding, so that explains what you observed.
Yes you can modify NUS to require bonding. To do that in the service declaration in the nRF51 firmware, instead of using BLE_GAP_CONN_SEC_MODE_SET_OPEN you should use BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM or other option depend on which type of bonding you want (Just work, Passkey, etc)

Note that the iOS/Android system won't show your device and bond to your device if they are not HID device. You would need to have an app for that. For the NUS we have the nRF UART app.