7afd7cba0d
In many plugins we've wanted to use ->prepare_firmware() to parse the firmware ahead of ->detach() and ->write_firmware() but this has the limitation that it can only return a single blob of data. For many devices, multiple binary blobs are required from one parsed image, for instance providing signatures, config and data blobs that have to be pushed to the device in different way. This also means we parse the firmware *before* we ask the user to detach. Break the internal FuDevice API to support these firmware types as they become more popular. This also allows us to move the Intel HEX and SREC parsing out of the dfu plugin as they are used by a few plugins now, and resolving symbols between plugins isn't exactly awesome. |
||
|---|---|---|
| .. | ||
| data | ||
| csr-aiaiai.quirk | ||
| fu-csr-device.c | ||
| fu-csr-device.h | ||
| fu-plugin-csr.c | ||
| meson.build | ||
| README.md | ||
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_2520USB\VID_0A12&PID_1337USB\VID_0A12