Windows 8.1 bonding/pairing error

RE: Windows 8.1 bonding/pairing error

Matt — Fri, 23 Oct 2015 09:24:07 GMT

@Hung Bui: I only have iPhone to test iOS, not Win8.1 to test.

RE: Windows 8.1 bonding/pairing error

Hung Bui — Thu, 22 Oct 2015 13:16:26 GMT

@Matt: Please confirm if it works on Windows 8.1 or not. If it's only the issue with iOS we will continue in the other case.

RE: Windows 8.1 bonding/pairing error

Matt — Thu, 22 Oct 2015 07:11:46 GMT

@Hung Bui: sec_param.bond = 1, I have test ble_app_proximity and nRF Toolbox in iOS9.1(Apple just release), have this issue. I have asked the question: link text

RE: Windows 8.1 bonding/pairing error

Hung Bui — Tue, 20 Oct 2015 13:59:14 GMT

@Matt: It's not configurable with the previous SDKs, but have you made sure you have set .sec_param.bond = 1 when call sd_ble_gap_sec_params_reply() ? This will force the peripheral to send LTK. Have you tried to test with the ble_app_proximity for example ?

RE: Windows 8.1 bonding/pairing error

Matt — Tue, 20 Oct 2015 01:36:32 GMT

@Hung Bui: In SDK6.1 and SD7.0.0, have this issue, but the SD have not the "kdist_periph" struct of m_sec_params!!

RE: Windows 8.1 bonding/pairing error

Hung Bui — Thu, 16 Jul 2015 14:37:24 GMT

@Valer_I: It's great that you found. I actually forgot that, if we don't set the m_sec_params.kdist_periph.enc = 1; we will not distribute LTK and will not do bonding. I think Windows won't accept pairing without bonding. And this explained the issue you encounted.

m_sec_params.kdist_periph.id = 1; is not needed since we don't use resolvable random address.

RE: Windows 8.1 bonding/pairing error

Valer_I — Thu, 16 Jul 2015 13:03:38 GMT

The solution found!

in static void sec_params_init(void)

I've just add:

m_sec_params.kdist_periph.enc   = 1;
m_sec_params.kdist_periph.id    = 1;
m_sec_params.kdist_periph.sign  = 0;

And now it works.

RE: Windows 8.1 bonding/pairing error

Hung Bui — Wed, 15 Jul 2015 13:50:19 GMT

@Valer_l: It's pretty strange to see auth_status 0x88 which mean BLE_GAP_SEC_STATUS_UNSPECIFIED.

Could you track and send me a sniffer trace ? It would help a lot. Do you have the same issue when testing with other examples that use the device manager ?

You should set the break point in the content of the app_error_handler() function, It's defined in the app_error.c file. You should add "DEBUG" in the compiler flag so that it won't reset when there is an assert.

RE: Windows 8.1 bonding/pairing error

Valer_I — Wed, 15 Jul 2015 11:19:00 GMT

I add BP to case:

case BLE_GAP_EVT_AUTH_STATUS:
    m_auth_status = p_ble_evt->evt.gap_evt.params.auth_status;
					break;

and I caught:

m_auth_status: 
 auth_status 0x88
 error_src 0x01
 bonded 0x00

The same result I've got previously before asking the question.

Following your advice, I tried to set BP to assert handler, is it app_error_handler(DEAD_BEEF, line_num, p_file_name); for this project? I couldn't set the breakpoint ot this line, debugger shows icon on this line like (!) and it seems that this code does not execute. Could you please point me in to more details how to debug with assert handler.

RE: Windows 8.1 bonding/pairing error

Hung Bui — Wed, 15 Jul 2015 09:41:57 GMT

@Valer_I: Could you let me know what didn't work when testing with Windows 8.1 ? For debugging, you can either add a breakpoint in the assert handler to track back which error code, line number, file name cause the assertion. Or you can use UART debug, as you mentioned. You can either use simple uart library or use app_uart.

You can have a look at ble_app_uart on how to use it.

RE: Windows 8.1 bonding/pairing error

Valer_I — Wed, 15 Jul 2015 08:13:54 GMT

Thank you for the responce! the ble_app_template it's really nice project for my application. However it doesn't work with windows 8.1. I have just compiled it as is and downloaded to the chip.:( I plan to add USART functionality to it to make some debug and investigate the issue.

RE: Windows 8.1 bonding/pairing error

Hung Bui — Mon, 13 Jul 2015 13:37:53 GMT

@Valer_I : If you have SDK v8.x you can have a look at the ble_app_template. In that template we don't use device manager and the distributed keys can be retreived with m_keys when the bonding is finished (BLE_GAP_EVT_AUTH_STATUS event). In the ble_app_template, we don't store the key to flash, (erased when restart) but you can implement that.

I don't think you would have any issue with Android testing with this example.