bonding issue

RE: bonding issue

Balaji Srinivasan — Thu, 27 Nov 2014 09:29:12 GMT

you are welcome. The API accepts only ASCII values. This is documented here -> developer.nordicsemi.com/.../a00228.html

RE: bonding issue

sruthiraj koodathil — Thu, 27 Nov 2014 09:25:29 GMT

thnks ....

is it necessary to use ascii values? why?

RE: bonding issue

Balaji Srinivasan — Thu, 27 Nov 2014 09:20:20 GMT

Those are the ASCII values of 0x01, 0x02 etc. In your case, you should use 0x35, 0x36, 0x37, 0x38, 0x39, 0x30.

RE: bonding issue

sruthiraj koodathil — Thu, 27 Nov 2014 08:43:22 GMT

wat is behind in using 0x31,0x32.... instead of 0x01,0x02....? i dnt knw whether dis is a stupid question...

if i want to use no.s 567890 ,what shud i realy use instead of dis

RE: bonding issue

Balaji Srinivasan — Tue, 18 Nov 2014 10:54:39 GMT

Example code for passkey 123456.

#define STATIC_PASSKEY          {0x31, 0x32, 0x33, 0x34, 0x35, 0x36}

ble_opt_t      opt;
static uint8_t config_passkey[BLE_GAP_PASSKEY_LEN]  = STATIC_PASSKEY;

opt.gap_opt.passkey.p_passkey = m_config_passkey;

err_code = sd_ble_opt_set(BLE_GAP_OPT_PASSKEY, &opt);

RE: bonding issue

Balaji Srinivasan — Tue, 18 Nov 2014 10:54:12 GMT

@ dis is the passkey i have to enter while bonding ryt? :

Yes.

@ in dm_ble_evt_handler i have assingned array passkey[6] as {1,2,3,4,5,6}.

It looks to me that you want to have a static pass key (i.e you want both the devices to use a preconfigured passkey). Is this correct? In this case, you will need to use the options API (sd_ble_opt_set with opt_id = BLE_GAP_OPT_PASSKEY) to set the passkey before you start advertising.

A typical use case of this is defined as an MSC here -> developer.nordicsemi.com/.../a00861.html

Refer here for documentation of this option -> developer.nordicsemi.com/.../a00228.html

RE: bonding issue

sruthiraj koodathil — Tue, 18 Nov 2014 10:38:41 GMT

p_ble_evt->evt.gap_evt.params.passkey_display.passkey..... dis is the passkey i have to enter while bonding ryt? in dm_ble_evt_handler i have assingned array passkey[6] as {1,2,3,4,5,6}... nd try to bond by entering dis key... mcp shows bonded true.. but connection is getting lost

RE: bonding issue

Balaji Srinivasan — Tue, 18 Nov 2014 09:26:41 GMT

The i/o capabilities are checked by the stack. You can either use display the passkey on a terminal window on your PC (you need to send the passkey over UART) or set your SEC_PARAM_IO_CAPABILITIES to BLE_GAP_IO_CAPS_NONE (no keyboard/no display).

RE: bonding issue

sruthiraj koodathil — Tue, 18 Nov 2014 09:07:40 GMT

when i tried to bond from master control panel,which part of the code checking the i/o capabilities and displaying pairing code... actually am working on nrf51822 eveluation board with no lcd no keyboard,

RE: bonding issue

Balaji Srinivasan — Thu, 13 Nov 2014 13:35:36 GMT

Hi Sruthiraj,

What is the IO Capability of your Master Control Panel? If you have not changed it, then it will be the default 'Keyboard And Display'. So you will be in a situation where the initiator (Master) has a 'Keyboard And Display' and the responder (Slave) has 'DisplayYesNo'. In this case, as per spec, the responder will have to display and the initiator will have to input. And this is probably what is happening for you.

There are two things you can do now.

1 . On the slave side, check if you are getting a BLE_GAP_EVT_PASSKEY_DISPLAY event. When you do, you will have to get the passkey contained in p_ble_evt->evt.gap_evt.params.passkey_display.passkey and enter it when the Master Control Panel prompts you for the key.

2 . On the Master Control Panel, change the IO Capabilities to 'No Keyboard or display'. (You can do it in File -> Options -> Security) and then do 'Bond' from Master Control Panel. If Master Control Panel log says 'Bond already exists with the device', then please restart Master Control Panel, and try again (you will need to set the IO capabilities again). Please note that in this case, the generated key will be 'unauthenticated no MITM protection' key. If you want MITM, then please use the 1st approach.

See Table 2.5 (Mapping of IO Capabilities to STK Generation Method) of Bluetooth Specification Vol 3, Part H Section 2.3.5.1 for more information.

Cheers, Balaji