OpenLogi0x00d0 · dfu
Stream a signed firmware image to a device already in DFU mode — write chunks, track progress, and trigger verification and restart.
A HID++ 2.0 feature that carries the Device Firmware Upgrade (DFU) protocol
itself — the data-transfer phase that streams new firmware images to a device
after it has already entered DFU mode. It applies to the full range of
Logitech HID++ peripherals (mice, keyboards, headsets, receivers, and
touchpads) that support in-field firmware updates. It works in conjunction
with 0x00c2 dfuControlSigned, which governs the mode-transition step that
precedes the actual image transfer.
Not implemented in OpenLogi
OpenLogi's vendored hidpp crate does not provide a typed wrapper for this feature yet. The notes below summarise the HID++ feature in general terms, not OpenLogi behaviour. OpenLogi instead relies on 0x00c2 dfuControlSigned where applicable.
What it does
0x00d0 dfu handles the low-level mechanics of transferring a signed firmware
image to a device that is already in DFU mode. In general terms it provides:
- A means to initiate a firmware transfer, including communicating the target firmware entity (main application, bootloader, hardware module) and the expected image size.
- Chunked data-write operations that stream the firmware payload to the device in fixed-size blocks over HID++ reports.
- Status and progress queries so the host can track how much of the image has been accepted and whether any transfer error has occurred.
- A command to finalise the transfer and trigger the device to verify, commit, and restart with the new firmware.
The feature operates only while the device is in DFU mode (entered via
0x00c2 dfuControlSigned); it is not available during normal operation.
Images must be cryptographically signed by Logitech — the device rejects
unsigned or tampered payloads before committing them.
Status: Not implemented · Feature ID:
0x00d0· See also: 0x00c2 dfuControlSigned