Custom HID over GATT device

RE: Custom HID over GATT device

John — Fri, 29 Dec 2017 07:15:35 GMT

Finally,I find that BusHound can't monitor dat from HOGP vender defined device(maybe other reason).when I use nRF Connect to debug the HOGP, I CAN receive dat from HOGP vender defined device.

RE: Custom HID over GATT device

endnode — Thu, 28 Dec 2017 11:19:52 GMT

I don't really understand what do you mean by "custom HID over GATT". There is only one HID over GATT defined by BT SIG as far as I know and if you change UUIDs or protocol on top of GATT Characteristics then it's not HID any more and no "HID compliant" device will understand it on the other side. Am I missing something? However if you just use HID over GATT as example and you modify it to serve your own - completely proprietary - application/use case then I can understand the question. It's also nice that you've extracted two simple and understandable questions, unfortunately I cannot help you (from my perspective debugging is simply done by logging of GATT flow on both sides - nRF5x and the other peer if possible - plus looking to 2.4GHz RF analyzer/BLE sniffer for the rest). Hopefully someone else on this forum can.

RE: Custom HID over GATT device

John — Thu, 28 Dec 2017 02:44:16 GMT

Hi,endnode.Thank you. Sorry for my poor english and expression.actually,my question is simply.

a. Is there a PC utility to debug HOGP(HID Over GATT).

b. is there a custom HOGP example？

RE: Custom HID over GATT device

endnode — Wed, 27 Dec 2017 22:50:10 GMT

So the question is specifically about Bus Hound? Then I'm sorry to interfere, I have no clue what it is and how it should work, I was assuming it's just another terminal app... Hope you will find someone interested in such obscure things here to help you.

RE: Custom HID over GATT device

John — Wed, 27 Dec 2017 03:47:49 GMT

I use BreakPoint debugging techniques.it seems the FW work normal，no error happen,but Bus Hound just can't receive data.

RE: Custom HID over GATT device

endnode — Tue, 26 Dec 2017 21:48:01 GMT

Basic debugging techniques: UART (or RTT) debug logging from nRF5x FW to PC console over (emulated) COM port and Radio analyzer/BLE sniffer. What at these things saying? Is your FW alive? What events and function calls/error return codes are done on top of BLE stack in your code? What is running over the radio? I'm afraid whatever you wrote to the code you will need to debug (at least for the beginning until you isolate piece of code which does something unexpected and Nordic support team can debug with you).