HID support evidence

HID feature report is sent but the device state does not change

A sample report for HID devices where the host sends a feature report but firmware does not apply the expected state change.

HTML preview

Evidence handoff preview

Download PDF
Failure boundary The host sent the HID feature report, but the device response or follow-up state evidence does not confirm the requested change.
Raw evidence excerpt SET_REPORT observed; report ID and payload bytes captured; follow-up GET_REPORT/status does not reflect the requested state.

Evidence screenshots

Packet detail evidence
Packet detail evidence The selected transfer keeps setup packet fields and payload bytes together for HID report review.

Evidence table

LayerFindingImplication
HID requestThe host sends SET_REPORT with a captured report ID and payload.The host-side command was issued; the next boundary is firmware parsing and state application.
Device responseFollow-up evidence does not confirm the expected device state.The report payload may not match the firmware's expected format.
HandoffThe report isolates request bytes and expected state in one case file.Support can send firmware a concrete HID payload instead of an application-level symptom.

Recommended fix

  1. Verify report ID, report length, byte order, and feature report parser behavior.
  2. Compare host payload against the HID report descriptor and firmware struct layout.
  3. Add a known-good feature report capture to the regression suite.