Windows 10 Driver Error

[mholin1]

Hello. trying to make a Bluetooth mouse/keyboard for a Windows 10 PC and starting with the "HID_test" Example from the Arduino BLEPeripheral Library on a Sparkfun nRF52832 Breakout Board using only the mouse portion of HID_test for now. The PC sees "HID" local name and starts to pair but then after few seconds displays "Driver Error" and drops the connection. A commercial Bluetooth mouse pairs and works with the same PC however.

Also found the function:

bleHID.clearBondStoreData();

from HID_test conflicts with the nRF52832 Breakout Board bootloader so just using a J-Link to program the application for now.

Hoping someone might have some insight into that Driver Error ?

[sandeepmistry]

@mholin1 I haven't tried this setup myself, but I recall the Windows pairing process being a bit weird compared to Android and iOS.

[mholin1]

Thanks for taking a look. Someone on the Nordic Developer Zone was getting a similar "Driver Error" and the resolution seemed to be something about bonding? Admittedly I am not familiar enough with the BLE spec. or the Library to know how to implement bonding.

Also, can you say if that bleHID.clearBondStoreData(); statement is necessary for pairing? And any idea why it is conflicting with the bootloader? It looks like you are putting the bond store up at the last page of flash memory which should be fine as far as I can tell.

[mholin1]

I moved the bond store to just under the bootloader (from default 0x7F000 to 0x79000) but still getting "Driver Error" messages from Windows 10 while attempting to pair. Has anybody ever used this Library successfully with a Windows 10 HID application (mouse or keyboard)?

[mholin1]

Hi Sandeep, Can you suggest any way I can get help with this? I set up Nordic's BLE Sniffer and had the Nordic guys take a look but it is not their code and so they really could not help me. Is there anyone who has used the Library on a Windows 10 HID application? Thanks, Mark

…

-------------------------------------------- On Sun, 6/18/17, Sandeep Mistry <notifications@github.com> wrote: Subject: Re: [sandeepmistry/arduino-BLEPeripheral] Windows 10 Driver Error (#160) To: "sandeepmistry/arduino-BLEPeripheral" <arduino-BLEPeripheral@noreply.github.com> Cc: "mholin1" <mholin@yahoo.com>, "Mention" <mention@noreply.github.com> Date: Sunday, June 18, 2017, 10:02 AM @mholin1 I haven't tried this setup myself, but I recall the Windows pairing process being a bit weird compared to Android and iOS. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[varunhr]

Same problem with me as well..... Would some one help us with this issue?

Regards
Varun

[mholin1]

Hello Varun, I eventually had to give up. No real support from any entity involved. Tried the Cypress PSoC 4 parts and it works fine. PSoC Creator light years simpler development environment. Cypress tech support is as abysmal as this Nordic platform but at least the parts work as advertised.

Note: At least Nordic Tech Support tried to help but it was not their code.

[RicoKirstein]

I had a problem with the GATT HID driver in windows 10 as well. Uncommenting the line
"bleHIDPeripheral.setReportIdOffset(1);" solved it for me.

[mholin1]

Thanks for your input. I don't see that line in the original Example HID_test.ino. Is it in one of the header files? Also i do recall there was a conflict between the bootloader so moving the bond store offset to 0x79000 solved that problem but I still got the Win 10 Driver Error. So does your device (mouse in my case) now work on Win 10? If so could you please attach your sketch? Thanks for posting. Mark

…

-------------------------------------------- On Fri, 12/8/17, RicoKirstein <notifications@github.com> wrote: Subject: Re: [sandeepmistry/arduino-BLEPeripheral] Windows 10 Driver Error (#160) To: "sandeepmistry/arduino-BLEPeripheral" <arduino-BLEPeripheral@noreply.github.com> Cc: "mholin1" <mholin@yahoo.com>, "Mention" <mention@noreply.github.com> Date: Friday, December 8, 2017, 7:24 AM I had a problem with the GATT HID driver in windows 10 as well. Uncommenting the line "bleHIDPeripheral.setReportIdOffset(1);" solved it for me. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[RicoKirstein]

I have my BLE nano 2 on a swd probe, so I haven't ran into any bootloader issued.
The line was in the HID_Keyboard example. I haven't had any successful inputs send from the device yet, but the driver error went away and the device is loaded correctly according to windows. I'm currently on the windows 10 1709 thing. My sketch is just the HID_Keyboard example with the ifdef surrounding bleHIDPeripheral.setReportIdOffset(1) removed.

[mholin1]

Thanks. That ifdef isn't even in HID_test. If you are having issues with Win 10 versions, I do recall one of the recent Microsoft "upgrades" no longer reports the Driver Error but the mouse still does not function. A commercial BLE mouse does function on the same PC however. Good Luck. Please post if you find anything further.

…

-------------------------------------------- On Fri, 12/8/17, RicoKirstein <notifications@github.com> wrote: Subject: Re: [sandeepmistry/arduino-BLEPeripheral] Windows 10 Driver Error (#160) To: "sandeepmistry/arduino-BLEPeripheral" <arduino-BLEPeripheral@noreply.github.com> Cc: "mholin1" <mholin@yahoo.com>, "Mention" <mention@noreply.github.com> Date: Friday, December 8, 2017, 9:15 AM I have my BLE nano 2 on a swd probe, so I haven't ran into any bootloader issued. The line was in the HID_Keyboard example. I haven't had any successful inputs send from the device yet, but the driver error went away and the device is loaded correctly according to windows. I'm currently on the windows 10 1709 thing. My sketch is just the HID_Keyboard example with the ifdef surrounding bleHIDPeripheral.setReportIdOffset(1) removed. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[varunhr]

Hai thank you very much for the info. I too moved to TI's CC2541 chip(HM 10 module). Its working in win 10 with some bugs. Trying to debug them. Regards Varun h r

…

On Fri, Dec 1, 2017 at 6:01 PM, mholin1 ***@***.***> wrote: Hello Varun, I eventually had to give up. No real support from any entity involved. Tried the Cypress PSoC 4 parts and it works fine. PSoC Creator light years simpler development environment. Cypress tech support is as abysmal as this Nordic platform but at least the parts work as advertised. Note: At least Nordic Tech Support tried to help but it was not their code. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#160 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AUX_zNrvN9sZ7ynpTPNr50npaEdElOt9ks5s7_GZgaJpZM4N0AdS> .

[RicoKirstein]

Can you post a link to the libraries you're using? Maybe it's just a problem with the descriptor used in this library.
Cheers
Rico

[mholin1]

As I recall it is just the Arduino BLEPeripheral Library downloaded straight from the Arduino IDE. Where you referring to a different Library? Thanks for the help :)

…

-------------------------------------------- On Mon, 12/11/17, RicoKirstein <notifications@github.com> wrote: Subject: Re: [sandeepmistry/arduino-BLEPeripheral] Windows 10 Driver Error (#160) To: "sandeepmistry/arduino-BLEPeripheral" <arduino-BLEPeripheral@noreply.github.com> Cc: "mholin1" <mholin@yahoo.com>, "Mention" <mention@noreply.github.com> Date: Monday, December 11, 2017, 9:02 AM Can you post a link to the libraries you're using? Maybe it's just a problem with the descriptor used in this library. Cheers Rico — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[RicoKirstein]

It seems we're missing 2 BLE reports. The standart says there should be 2 more for keyboards at least.
BootKeyboardOutputReport and BootKeyboardInputReport
For Mouse it should be BootMouseInputReport.
Can you check with a BLE explorer tool if your working devices have those services?
Cheers
Rico