fwupd/plugins/cros-ec
Richard Hughes 28678235cd Move the fuzzing files into the plugin directories
We only had to pile everything into the src/fuzzing/firmware directory
because honggfuzz could not cope with more than one input path.

This way each plugin is self contained and easy to copy.
Also, install the fuzzing builder objects as this fixes the installed
tests when srcdir does not exist.

Based on a patch by Jan Tojnar <jtojnar@gmail.com>, many thanks.
2021-10-22 15:24:05 +01:00
..
data cros-ec: Initial skeleton 2020-05-29 06:55:40 +01:00
tests Move the fuzzing files into the plugin directories 2021-10-22 15:24:05 +01:00
cros-ec.quirk cros-ec: Add D501 Baklava device support 2021-03-18 14:29:42 -07:00
fu-cros-ec-common.c trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
fu-cros-ec-common.h trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
fu-cros-ec-firmware.c trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
fu-cros-ec-firmware.h trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
fu-cros-ec-usb-device.c Lower the GUsb dep to allow compiling on RHEL-8 2021-09-24 06:50:59 -05:00
fu-cros-ec-usb-device.h trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
fu-plugin-cros-ec.c trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
meson.build Move the plugin build logic to the plugins themselves 2021-02-18 14:46:20 +00:00
README.md trivial: update markdown for pre-commit style 2021-07-18 14:42:47 -05:00

Chrome OS EC

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.

Information about the USB update protocol is available here.

Firmware Format

The daemon will decompress the cabinet archive and extract a firmware blob in the Google fmap 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.