fwupd/plugins/cros-ec
Benson Leung e8fd2cdfa4 cros-ec: Restructure to allow RO update first
Our update flow prior to this was:
1. On detach, reboot to RO.
2. From Old RO, Update RW.
3. Reboot to New RW
4. From New RW, Update RO.
5. Reboot to finish

This flow has a flaw, which is that the Old RO may be buggy (especially
during development, before it's actually locked down and actually Read-Only).

This change will do the following instead:
1. On detach, do not reboot to RO if RO is writeable, and we are in RW
2. From old RW, Update RO
3. Reboot to new RO
4. From New RO, update RW
5. Reboot to finish.

This has a speed advantage as well, as we save one reboot cycle (2 vs 3).
2020-10-11 07:34:49 +01:00
..
data cros-ec: Initial skeleton 2020-05-29 06:55:40 +01:00
cros-ec.quirk cros-ec: Initial skeleton 2020-05-29 06:55:40 +01:00
fu-cros-ec-common.c cros-ec: Parse version number into triplet 2020-05-29 06:55:40 +01:00
fu-cros-ec-common.h trivial: cros-ec: Use fu-memcpy-safe 2020-06-20 07:24:32 +01:00
fu-cros-ec-firmware.c cros-ec: Save new firmware version on successful write 2020-08-28 10:48:03 -07:00
fu-cros-ec-firmware.h cros-ec: Save new firmware version on successful write 2020-08-28 10:48:03 -07:00
fu-cros-ec-usb-device.c cros-ec: Restructure to allow RO update first 2020-10-11 07:34:49 +01:00
fu-cros-ec-usb-device.h cros-ec: Add usb_findit functionality 2020-05-29 06:55:40 +01:00
fu-plugin-cros-ec.c cros-ec: Add cros-ec-firmware 2020-06-20 07:24:32 +01:00
meson.build cros-ec: Add cros-ec-firmware 2020-06-20 07:24:32 +01:00
README.md cros-ec: Set protocol for cros-ec-usb-device 2020-07-09 07:44:19 +01:00

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

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

[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