Handle HID OUT reports with no report ID #7806
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Raw HID OUT reports (to the peripheral from the host), with no report ID, were not being parsed correctly. The code assumed the first byte was the report id. However, this is not always the case.
Instead, see if there is a defined HID device with report ID 0, whose report length matches the incoming report. If so, assume the incoming report is for that device.
The long-term fix is for TinyUSB to know which reports are for which report ID's, but that requires hathach/tinyusb#1095 to be addressed.
Tested with
hidapitester
on Linux:On the CPy side:
test program (rawread.py):
boot.py: