nrf24lu1p USB hid ReportDescriptor size greater than 255

RE: nrf24lu1p USB hid ReportDescriptor size greater than 255

ovrebekk — Fri, 05 Jan 2018 10:08:04 GMT

Then you have to find some way to fit your descriptor in 255 bytes or less.

Depending on the data you are trying to send there might be ways to optimize the descriptor.

What kind of device are you making?

Best regards

RE: nrf24lu1p USB hid ReportDescriptor size greater than 255

jinsheng20 — Fri, 05 Jan 2018 02:02:13 GMT

Thank you for your answer.That's what I did. if I don't change a limitation in the nRF24LU1+ USB stack. What am I supposed to do?

RE: nrf24lu1p USB hid ReportDescriptor size greater than 255

ovrebekk — Thu, 04 Jan 2018 08:53:51 GMT

You might be able to change the hid_report_desc_size field to a uint16_t and make it work, but you will have to make additional changes to all the code that uses this field.

With USB you can also some times run into endianness issues, where 16-bit values (or larger) need to be swapped. The reason for this is that the Keil C51 compiler uses big endian values, while USB uses little endian values.

Best regards

RE: nrf24lu1p USB hid ReportDescriptor size greater than 255

jinsheng20 — Thu, 04 Jan 2018 05:09:28 GMT

Thank you for your answer. I want to send more than 255 bytes of data, what do you suggest I do to give an example? if I change uint8_t variable and so on to uint16_t , Is there going to be a problem?

RE: nrf24lu1p USB hid ReportDescriptor size greater than 255

ovrebekk — Wed, 03 Jan 2018 15:30:14 GMT

This is a limitation in the nRF24LU1+ USB stack.

If you take a look at the hal_usb_hid_t struct you can see that the report descriptor size is stored in a uint8_t variable, which means the maximum size is 255.

typedef struct {
hal_usb_hid_desc_t* hid_desc;
uint8_t* hid_report_desc;
uint8_t hid_report_desc_size;
} hal_usb_hid_t;

Best regards
Torbjørn Øvrebekk