PASSKEY

[katyon]

 I’ve downloaded     nRF5_SDK_11.0.0_89a8197 and starting with examples from \examples\ble_peripheral\???\pca10040\s132\arm5_no_packs\

 I would like the other device to request a passkey (constant) at pairing (the passkey on my side is constant - no display needed)

After   gap_params_init();I’ve added the following code:

 

{

 static ble_opt_t optS;

   static uint8_t passw[]="123456";           

 optS.gap_opt.passkey.p_passkey=passw;

   err_code =sd_ble_opt_set(BLE_GAP_OPT_PASSKEY, &optS);

}

 

err_code returned :  0  

 

Still the module will pair and communicate without requesting a passkey.

I've tried to find an answer in Q&A . in some answers there was a reference to fields : io_caps,mitm. cant make out what does it mean. 

(these fields belong to structs relevant to services, not pairing)

 

Thanks for any help

   Yona

[Vidar Berg]

Hi Yona,

You can change the permission/security level on the BLE characteristics to require MITM pairing. The central does not need to pair with the device if security level is set to "open".

E..g, change BLE_GAP_CONN_SEC_MODE_SET_OPEN(&attr_md.read_perm) to BLE_GAP_CONN_SEC_MODE_SET_ENC_WITH_MITM (&attr_md.read_perm) if you want to limit read access to a certain characteristic. 

 

[katyon]

thank you for the answer.

making this change - finally  "produces"  the  events:

BLE_GAP_EVT_SEC_PARAMS_REQUEST,   BLE_GAP_EVT_AUTH_STATUS

how should I deal with them ?

(as the cellphone application does not know that passkey is needed- so reading the characteristic results in a  BLE disconnection)

Yona

[katyon]

one more thing:

I've tried  using  nRF5_SDK_15xxxxx package  with ble_app_hrs example project.

its way too heavy . too many elements to remove (and than it gives some internal error).

so I still need your help regarding the resets/BLE dying .

I'd prefer not to call  sd_power_system_off if I can avoid it

Thanks

Yona

[bjorn-spockeli]

If you do not want the ble_app_hrs example to go to SYSTEM OFF, then simply comment out the sleep_mode_enter(); call under the BLE_ADV_EVT_IDLE case in on_adv_evt() and under the  BSP_EVENT_SLEEP case in bsp_event_handler().

Best regards

Bjørn 

[katyon]

me again, new issue 

now that a peripheral BLE is working (including the passkey), I'm requested to develop a tester for that unit.

For that I need A BLE central .

so I started with nRF5_SDK_11.0.0_89a8197\examples\ble_central\ble_app_multilink_central .

all is fine.the only issue is again: how to operate the passkey (as a central unit)

thanks

Yona

[bjorn-spockeli]

HI Yona, 

you need to reply to the BLE_GAP_EVT_AUTH_KEY_REQUEST with sd_ble_gap_auth_key_reply with the passkey as a parameter, see the Bonding: Passkey Entry, User Inputs on Central or OOB MSC.

You can also take a look at this post. 

Best regards

Bjørn

[katyon]

thanks for your reply

I fail to find the received event  BLE_GAP_EVT_AUTH_KEY_REQUEST

in the functions :   on_ble_evt    (main.c)

                              ble_conn_state_on_ble_evt,ble_conn_params_on_ble_evt  (ble_conn_params.c)

  could you please tell me where to expect this event

  also looked in your other links, cant make out- where to expect,how to respond

thanks again

Yona

[bjorn-spockeli]

You will have to add it as a case in on_ble_evt and respond as shown in the Bonding: Passkey Entry, User Inputs on Central or OOB. Note you also have to set the IO params in the central to  BLE_GAP_IO_CAPS_KEYBOARD_ONLY or BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY.

[katyon]

ever so sorry- still fail to receive the event  BLE_GAP_EVT_AUTH_KEY_REQUEST anywhere

I'm using the project ble_app_hrs (nRF5_SDK_11.0.0_89a8197)

some of the code:

#define SEC_PARAM_BOND 1
#define SEC_PARAM_MITM 1
#define SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY // 
#define SEC_PARAM_OOB 0
#define SEC_PARAM_MIN_KEY_SIZE 7
#define SEC_PARAM_MAX_KEY_SIZE 16
#define SEC_PARAM_LESC 0 /**< LE Secure Connections not enabled. */
#define SEC_PARAM_KEYPRESS 0 /**< Keypress notifications not enabled. */

the function dealing with these defines is   device_manager_init()

after it filles the params- it calls dm_register()

can you please guide me to what I'm doing wrong?

thanks again

Yona 

[bjorn-spockeli]

But have you set the  IO params in the central to  BLE_GAP_IO_CAPS_KEYBOARD_ONLY or BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY ? It is the central that will send the AUTH_KEY_REQUEST to the peripheral. 

[katyon]

please note  the lines:

#define SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_KEYBOARD_DISPLAY

the function dealing with these defines is   device_manager_init()

after it filles the params- it calls dm_register()

I've wrote these lines in my question

Yona

[bjorn-spockeli]

Yes, i am aware of that but you stated that you're using the ble_app_hrs example which is a peripheral example. Hence, I am asking if you have configured the CENTRAL example to have one of the two mentioned IO capabilities?