Bus Scope sample reports

Evidence you can inspect before trusting the workflow.

These examples show the output buyers actually need: a failure boundary, evidence table, recommended fix, and a file that can leave the app.

Firmware enumeration handoff

USB device enumerates but the descriptor is wrong

A Bus Scope sample report that separates host driver blame from a device descriptor mismatch during enumeration.

Failure boundary: The host issued standard descriptor requests, but the device returned inconsistent interface and endpoint metadata before the driver could bind cleanly.
Likely cause: Firmware descriptor tables, endpoint declarations, or configuration selection do not match the driver expectation.

Firmware transfer failure

A sample report for a device that enumerates but stalls or times out during a bulk endpoint transaction.

Failure boundary: Enumeration succeeded, but the failure occurs after host traffic moves to the bulk endpoint used by the firmware transfer.
Likely cause: Endpoint firmware state, transfer size handling, timeout behavior, or device-side flow control is failing after setup.

HID support evidence

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

Failure boundary: The host sent the HID feature report, but the device response or follow-up state evidence does not confirm the requested change.
Likely cause: The HID report ID, payload layout, firmware parser, or state transition is mismatched with the host tool.