.. | ||
ccgx-ids.quirk | ||
ccgx.quirk | ||
fu-ccgx-common.c | ||
fu-ccgx-common.h | ||
fu-ccgx-dmc-common.c | ||
fu-ccgx-dmc-common.h | ||
fu-ccgx-dmc-device.c | ||
fu-ccgx-dmc-device.h | ||
fu-ccgx-dmc-firmware.c | ||
fu-ccgx-dmc-firmware.h | ||
fu-ccgx-firmware.c | ||
fu-ccgx-firmware.h | ||
fu-ccgx-hid-device.c | ||
fu-ccgx-hid-device.h | ||
fu-ccgx-hpi-common.c | ||
fu-ccgx-hpi-common.h | ||
fu-ccgx-hpi-device.c | ||
fu-ccgx-hpi-device.h | ||
fu-plugin-ccgx.c | ||
fu-self-test.c | ||
meson.build | ||
README.md |
Cypress
Introduction
This plugin can flash firmware on Cypress CCGx USB-C controller family of devices used in docks.
Supported Protocols
This plugin supports the following protocol IDs:
- com.cypress.ccgx
- com.cypress.ccgx.dmc
Device Flash
There are four kinds of flash layout. Single image firmware is not currently supported in this plugin.
Symmetric Firmware
In symmetric firmware topology, FW1 and FW2 are both primary (main) firmware with identical sizes and functionality. We can only update FW1 from FW2 or FW2 from FW1. This does mean we need to update just one time as booting from either firmware slot gives a fully functional device.
After updating the "other" firmware we can just use CY_PD_DEVICE_RESET_CMD_SIG
to reboot into the new firmware, and no further action is required.
Asymmetric Firmware
In asymmetric firmware topology, FW1 is backup and FW2 is primary (main) firmware with different firmware sizes. The backup firmware may not support all dock functionality.
To update primary, we thus need to update twice:
Case 1: FW2 is running
- Update FW1 -> Jump to backup FW
CY_PD_JUMP_TO_ALT_FW_CMD_SIG
-> reboot - Update FW2 -> Reset device
CY_PD_DEVICE_RESET_CMD_SIG
-> reboot -> FW2
Case 2: FW1 is running (recovery case)
- Update FW2 -> Reset device
CY_PD_DEVICE_RESET_CMD_SIG
-> reboot -> FW2
The CY_PD_JUMP_TO_ALT_FW_CMD_SIG
command is allowed only in asymmetric FW, but
CY_PD_DEVICE_RESET_CMD_SIG
is allowed in both asymmetric FW and symmetric FW.
DMC(Dock Management Controller) Composite Firmware
In composite firmware topology, a single firmware image contains metadata and firmware images of multiple devices including DMC itself in a dock system.
Firmware Format
There are two kinds of firmware format.
Cyacd firmware format
The daemon will decompress the cabinet archive and extract several firmware blobs in cyacd file format. See https://community.cypress.com/docs/DOC-10562 for more details.
DMC composite firmware format
The daemon will decompress the cabinet archive and extract several firmware blobs in a combined image file format. See 4.4.1 Single Composite (Combined) Dock Image at https://www.cypress.com/file/387471/download for more details.
GUID Generation
These devices use the standard USB DeviceInstanceId values, e.g.
USB\VID_1234&PID_5678
Devices also have additional instance IDs which corresponds to the silicon ID, application ID and device mode, e.g.
USB\VID_1234&PID_5678&SID_9ABC
USB\VID_1234&PID_5678&SID_9ABC&APP_DEF1
USB\VID_1234&PID_5678&SID_9ABC&APP_DEF1&MODE_FW2
Update Behavior
The device usually presents in runtime HID mode, but on detach re-enumerates with with a DMC or HPI interface. On attach the device again re-enumerates back to the runtime HID mode.
For this reason the REPLUG_MATCH_GUID
internal device flag is used so that
the DMC/HPI and runtime modes are treated as the same device.
Vendor ID Security
The vendor ID is set from the USB vendor, for example set to USB:0x04B4
External Interface Access
This plugin requires read/write access to /dev/bus/usb
.