faa35e430b
This also renames a symbol to make it clear that you can call it more than once. Fixes https://github.com/fwupd/fwupd/issues/3148 |
||
|---|---|---|
| .. | ||
| data | ||
| cros-ec.quirk | ||
| fu-cros-ec-common.c | ||
| fu-cros-ec-common.h | ||
| fu-cros-ec-firmware.c | ||
| fu-cros-ec-firmware.h | ||
| fu-cros-ec-usb-device.c | ||
| fu-cros-ec-usb-device.h | ||
| fu-plugin-cros-ec.c | ||
| meson.build | ||
| README.md | ||
Chrome OS EC Support
Introduction
This plugin provides support for the firmware updates for Chrome OS EC project based devices.
Initially, it supports the USB endpoint updater, but lays the groundwork for future updaters which use other update methods other than the USB endpoint.
This is based on the chromeos ec project's usb_updater2 application [1].
Information about the USB update protocol is available at [2].
Firmware Format
The daemon will decompress the cabinet archive and extract a firmware blob in the Google fmap [3] file format.
This plugin supports the following protocol ID:
- com.google.usb.crosec
GUID Generation
These devices use the standard USB DeviceInstanceId values, e.g.
USB\VID_18D1&PID_501A
Update Behavior
The device usually presents in runtime mode, but on detach re-enumerates with the same USB PID in an unlocked mode. On attach the device again re-enumerates back to the runtime locked mode.
For this reason the REPLUG_MATCH_GUID internal device flag is used so that
the bootloader and runtime modes are treated as the same device.
Vendor ID Security
The vendor ID is set from the USB vendor, which is set to various different values depending on the model and device mode. The list of USB VIDs used is:
USB:0x18D1
External interface access
This plugin requires read/write access to /dev/bus/usb.
[1] https://chromium.googlesource.com/chromiumos/platform/ec/+/master/extra/usb_updater/usb_updater2.c [2] https://chromium.googlesource.com/chromiumos/platform/ec/+/master/docs/usb_updater.md [3] https://www.chromium.org/chromium-os/firmware-porting-guide/fmap