proxmox-mirrors/fwupd
1
0
Fork 0
mirror of https://git.proxmox.com/git/fwupd synced 2025-05-21 07:16:30 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
4a156deee2
fwupd/plugins/dfu-csr
History
Richard Hughes faa35e430b Show a warning if the device has no GType and the plugin has no default 
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
2021-04-15 16:52:56 +01:00
..
data csr: Rename plugin to dfu-csr as it depends on the prefixed plugin 2021-02-18 14:46:20 +00:00
dfu-csr.quirk Simplify the quirk file format 2021-03-03 08:30:34 +00:00
fu-dfu-csr-device.c Remove FuFirmwareImage and just use FuFirmware instead 2021-03-09 21:14:12 +00:00
fu-dfu-csr-device.h csr: Rename plugin to dfu-csr as it depends on the prefixed plugin 2021-02-18 14:46:20 +00:00
fu-plugin-dfu-csr.c Show a warning if the device has no GType and the plugin has no default 2021-04-15 16:52:56 +01:00
meson.build Move the plugin build logic to the plugins themselves 2021-02-18 14:46:20 +00:00
README.md Add a new internal flag to opt-in to GUID matching 2021-02-25 15:47:25 +00:00

README.md

DFU CSR Support

Introduction

CSR is often called “driverless DFU” and is used only by BlueCore chips from Cambridge Silicon Radio (now owned by Qualcomm). The driverless just means that it's DFU like, and is routed over HID.

CSR is a ODM that makes most of the Bluetooth audio chips in vendor hardware. The hardware vendor can enable or disable features on the CSR microcontroller depending on licensing options (for instance echo cancellation), and there’s even a little virtual machine to do simple vendor-specific things.

All the CSR chips are updatable in-field, and most vendors issue updates to fix sound quality issues or to add support for new protocols or devices.

Firmware Format

The daemon will decompress the cabinet archive and extract a firmware blob in DFU file format.

This plugin supports the following protocol ID:

  • com.qualcomm.dfu

GUID Generation

These devices use the standard USB DeviceInstanceId values, e.g.

  • USB\VID_0A12&PID_1337&REV_2520
  • USB\VID_0A12&PID_1337
  • USB\VID_0A12

Update Behavior

A DFU device usually presents in runtime mode (or with no interfaces defined), but if the user puts the device into bootloader mode using a physical button it then enumerates with a HID descriptor. On attach the device returns to runtime mode which may mean the device "goes away".

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, in this instance set to USB:0x0A12

External interface access

This plugin requires read/write access to /dev/bus/usb.