Setting a PASSKEY

RE: Setting a PASSKEY

yiran — Thu, 30 Jul 2015 03:08:22 GMT

So what if I neither set IO capabilities to BLE_GAP_IO_CAPS_NONE nor use UART? Central device will be rejected directly?

RE: Setting a PASSKEY

julian — Sun, 30 Mar 2014 01:54:38 GMT

for BLE_GAP_IO_CAPS_DISPLAY_YESNO device, can the passkey be generated on device, and entered in the phone?

RE: Setting a PASSKEY

Elca — Mon, 05 Aug 2013 03:58:00 GMT

Hi, Audun, The final application is using the PASSKEY with smart phone while the device has no keyboard. In initial step, if we use an UART connected to the PCA10001, and save the PASSKEY in a non-volatile memory then remove the UART. The next time pairing with another smart phone, will PCA10001 request this 2nd smart phone for the PASSKEY? Of couse the PASSKEY value is identical with the first time pairing we saved in PCA10001.

RE: Setting a PASSKEY

Audun — Fri, 02 Aug 2013 09:37:18 GMT

Hi, the passkey is needed every time the smartphone pairs with the device. The pairing/bonding procedure happens the first time the devices are connected. Once they are paired they can be disconnected/connected freely without needing to enter the passkey again.

However if you remove the device from the smartphone device list, or if your PCA10001 application doesn't save the pairing information in non-volatile memory, the pairing information will be lost and a new pairing procedure (with passkey entry) has to be performed the next time you want to connect the devices. The "Bond manager" SDK component can be used to store pairing information (keys, addresses) to Flash.

RE: Setting a PASSKEY

Bastiaan — Thu, 01 Aug 2013 23:53:00 GMT

Once the PASSKEY has been saved in PCA10001, can it pair with the smart phone by PASSKEY if we remove the UART connection?

RE: Setting a PASSKEY

Guest — Thu, 01 Aug 2013 23:53:00 GMT

Once the PASSKEY has been saved in PCA10001, can it pair with the smart phone by PASSKEY if we remove the UART connection?

RE: Setting a PASSKEY

Ole Morten — Thu, 01 Aug 2013 11:49:29 GMT

To clean things up, I'd be happy if you could evaluate the answers you have received and accept one of them if you feel it's sufficient. If not, it might be useful to expand your question a little and provide further information.

RE: Setting a PASSKEY

Elca — Tue, 30 Jul 2013 01:49:43 GMT

thanks for the reply, and I'll check it.

RE: Setting a PASSKEY

Guest — Tue, 30 Jul 2013 00:40:04 GMT

thanks for the answers, and I'll check it.

RE: Setting a PASSKEY

Bastiaan — Tue, 30 Jul 2013 00:40:04 GMT

thanks for the answers, and I'll check it.

RE: Setting a PASSKEY

Audun — Mon, 29 Jul 2013 09:58:44 GMT

As Mihail pointed out, the IO capability flags are used to specify how the user can interface with the peripheral. If the peripheral has a numerical keyboard a 6-digit passkey can be used in the pairing process. The passkey is typically generated randomly and displayed on the Central device (iPhone), and the user has to enter the passkey on the Peripheral device. If the keys match, the pairing process succeeds.

For devices without any displays/keyboards/buttons, "Just Works" encryption is used in the pairing process. This is basically pairing with a static key.

By setting IO capabilities to BLE_GAP_IO_CAPS_NONE the iPhone won't ask for a passkey to be entered. However, if you want to use passkey in your application, you can for example use the UART to enter the passkey on your connected PC and transmit the passkey to the PCA10001.

Note that it's up to the application to read user input and notify the SoftDevice (see sd_ble_gap_auth_key_reply())

RE: Setting a PASSKEY

Mihail — Mon, 29 Jul 2013 05:33:00 GMT

Just to say that you cannot have static PASSKEY and next are the answers:

Question 1, Did I erase anything so that original "ble_app_hrs" code can not work?

Example does use: #define SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_NONE /**< No I/O capabilities. */ So device does not have capabilities for entering PASSKEY, in this case another association model is used.

Question 2, what is the proper way to add the PASSKEY for the pairing? This depends on your device capabilities, in other words does it has keyboard.

#define BLE_GAP_IO_CAPS_DISPLAY_ONLY      0x00   /**< Display Only. */
#define BLE_GAP_IO_CAPS_DISPLAY_YESNO     0x01   /**< Display and Yes/No entry. */
#define BLE_GAP_IO_CAPS_KEYBOARD_ONLY     0x02   /**< Keyboard Only. */
#define BLE_GAP_IO_CAPS_NONE              0x03   /**< No I/O capabilities. */
#define BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY  0x04   /**< Keyboard and Display. */

Question 3: Check the ble_app_gls example from documentation.