Driver error when trying to pair with Windows 10 computer

RE: Driver error when trying to pair with Windows 10 computer

Hung Bui — Tue, 26 Jul 2016 08:35:35 GMT

@grzegorz: well it's not obligated to have the app timer running for BLE to function. However, some of the modules use app timer, such as the connection parameter module. This could be the reason why you had driver error.

RE: Driver error when trying to pair with Windows 10 computer

grzegorz — Mon, 25 Jul 2016 18:27:51 GMT

@hungbui: I've finally found the problem. It was this line: APP_TIMER_INIT(APP_TIMER_PRESCALER, APP_TIMER_OP_QUEUE_SIZE, false); I thought it's needed by sensor simulator for updating simulated measurements and I removed the line. But it turns out it's neccessary for Bluetooth as well.

RE: Driver error when trying to pair with Windows 10 computer

Hung Bui — Mon, 25 Jul 2016 13:25:09 GMT

@Emil: I guess it will be the same for the UART profile, if you disconnect when Windows discovery service you will also get Driver error?

RE: Driver error when trying to pair with Windows 10 computer

Hung Bui — Thu, 21 Jul 2016 09:05:03 GMT

@Grzegorz: What do you have with your attribute table and advertising packet ? Which profiles and services ?

I suspect Windows detected some Bluetooth adopted profile and try to do some procedure defined by the spec when your device can't support it, probably.

RE: Driver error when trying to pair with Windows 10 computer

grzegorz — Wed, 20 Jul 2016 22:17:44 GMT

I think Windows naming convention is a bit confusing here. Pairing means in this case adding and installing a BLE device, even if there is no pairing in BLE sense. I've added screenshots showing how it applies to UART example. The board gets paired when running UART example, there is "driver error" when running my code. I'll try to modify Nordic example once again and see what I've missed.

RE: Driver error when trying to pair with Windows 10 computer

Hung Bui — Wed, 20 Jul 2016 14:01:12 GMT

I don't think it would actually pair. You mentioned above "Windows can't pair with it" but then now it worked ? If you want to check if it's paired or not you can try to use the sniffer.

Note that that there are many examples in the SDK that support pairing that you can use as the base project to modify. ble_app_proximity for example.

RE: Driver error when trying to pair with Windows 10 computer

grzegorz — Wed, 20 Jul 2016 13:42:29 GMT

@hungbui: I don't have the dongle so I couldn't try MCP on PC. I noticed this app doesn't support pairing and it notifies about that (BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP), but when I compiled and ran the example Windows paired without any problem. Maybe it didn't conduct real pairing but at least the board was reported as paired and there were no errors. I already have the application for PC, it works but needs the device to be paired first. BlueNRG-MS gets paired and the app works with it.

RE: Driver error when trying to pair with Windows 10 computer

Hung Bui — Wed, 20 Jul 2016 11:41:05 GMT

@grzegorz : Have you tried to use Master Control panel on the PC ? You would need a nRF5 dongle/DK to use it.

Note that the ble_app_nus doesn't support pairing, this could be the reason why windows 10 doesn't like it. You can try to test with the ble_app_proximity for example.

Note that Windows 10 natively doesn't know what to do with the ble_app_uart. You need an application on the PC to interact with the board.