Can anyone get S110 v7 to pair with Windows 8.1 (desktop)?

[Peter Myerscough-Jackopson]

I am trying to get the proximity example to pair with Windows, but it fails, requesting me to refer to the manufacturer.

I am using gcc in Eclipse on Windows 8.1 desktop, and a bluetooth usb adapter.

I am also seeing advertisements that are corrupt, (failed CRC) about 1-2% of the time when analysing using the nRfSniffer and a PCA10000 board.

The pairing from windows seems to request MITM bonding initially, then no MITM after an error/denial from the proximity device.

any help / tips / guidance / shared experience welcome,

Peter

[Peter Myerscough-Jackopson]

It appears that the example for the HID profile works and with a support case a solution has been found:

You must add this to application before starting advertising.

==

{

ble_gap_addr_t m_ble_addr;

uint32_t err_code;

err_code = sd_ble_gap_address_get(&m_ble_addr);

APP_ERROR_CHECK(err_code);

err_code = sd_ble_gap_address_set(BLE_GAP_ADDR_CYCLE_MODE_NONE, &m_ble_addr);

APP_ERROR_CHECK(err_code);

}

==

This allows pairing to occur, if somewhat slowly, hopefully Microsoft will work on speeding up the pairing as they focus more on the BLE stack.....

[Gilson]

Awesome,

I was having the same issue and after applying the code above I was able to pair my nRF51822 device to Win 8.1

I would like to understand why this made a difference.

I found the Windows 8.1 sample app with heart rate, blood pressure and thermometer. In the Windows 8.1 sample app, I get this output: "Getting the device failed with error: 80070057"

[Ulrich Myhre]

It is one of the known bugs in S110 7.0. The keys/id info given to the peer during bonding is not initialized properly without that piece of code. This makes the peer want to reconnect to a non-existing device.

[Petter Myhre]

Thank you for answering your own question.