Getting NRF_INVALID_PARAM when hid device is not keyboard nor mouse

RE: Getting NRF_INVALID_PARAM when hid device is not keyboard nor mouse

Nguyen Hoan Hoang — Fri, 28 Mar 2014 01:10:15 GMT

I found out to get HID generic working is to comment out this line :

//if (p_hids_init->is_kb || p_hids_init->is_mouse)

in the function ble_hids_init(...) of ble_hids.c line 1060. That was the missing parameter setting.

RE: Getting NRF_INVALID_PARAM when hid device is not keyboard nor mouse

Nguyen Hoan Hoang — Wed, 26 Mar 2014 16:50:26 GMT

Hi,

I have same issue.  If I ignore the sd_ble_gatts_value_set(...) as you mention.  It will crash at ble_bondmngr_sys_attr_store(); 
When can we expect this bug resolved ?

Thanks

RE: Getting NRF_INVALID_PARAM when hid device is not keyboard nor mouse

Peeter Vois — Sun, 09 Mar 2014 13:55:12 GMT

At the moment it seems to me that on Linux, sending oversized output report (more than 22 bytes) will cause the bluetoothd not to send any more output reports (including reports with correct size) until the device is disconnected and reconnected.

RE: Getting NRF_INVALID_PARAM when hid device is not keyboard nor mouse

Peeter Vois — Fri, 07 Mar 2014 13:51:09 GMT

Yes, I am struggling with the interface and maybe there is connection with 64 bytes... I need to port a USB device to use BLE... I will think something out.

I have also faked this device to be mouse and in that case there is no assert. And I also tried to ignore the assert. With MasterControlPanel I can send and receive reports with few bytes independent of the mouse issue. Although with Linux bluez library I have issue sending output report. Input report arrives well. At the moment I have no clear understanding what can be wrong. Reducing the size to 20 bytes does not improve things.... I'll dig further.

RE: Getting NRF_INVALID_PARAM when hid device is not keyboard nor mouse

Håkon Alseth — Fri, 07 Mar 2014 13:07:18 GMT

Hi Peeter,

The ble_hids library has a bug, where it will assert if is_kb && is_mouse == false. In file ble_hids.c, function on_connect, it will try to set protocol mode (for mice and keyboard), however the characteristic is not added (as you've already found out).

This bug is reported internally and we are working on a fix. Proposed workaround: add is_kb and is_mouse to a static global inside the ble_hids library, and then do a check in function "on_connect":

if (is_kb || is_mouse)
  err_code = sd_ble_gatts_value_set(...);

Another note: I see that your usb descriptor is setup with a size of 64 byte. You will have issues with this descriptor. The maximum in BLE is 20 bytes from peripheral to central, and 22 bytes from central to peripheral.

Best regards Håkon