ffb8fd5edc
When we install the MCFG carrier config files with QMI PDC, we were not explicitly selecting one, and that would end up reporting the "DF" (default) config is in use. Instead, we should explicitly select the carrier configuration that we were using before the firmware upgrade operation. For example, if the device originally was running with the Vodafone specific carrier configuration (e.g. T77W968.F1.0.0.3.7.VF.009) and we trigger the upgrade to the next available firmware associated to the Vodafone carrier (e.g. T77W968.F1.0.0.3.8.VF.009), we would want the device to boot with the Vodafone carrier config selected, instead of booting without any config selected (T77W968.F1.0.0.3.8.DF.009). This also fixes several upgrade problems detected by fwupd, because it may end up complaining that the target firmware that was selected to be installed (e.g. VF variant) is not the one actually reported by the device after the upgrade (e.g. DF variant). The selection of which is the config to activate is based on mapping the mcfg file name with the firmware version reported by the module before the upgrade. E.g. if the VF variant is reported by the module (T77W968.F1.0.0.3.7.VF.009), fwupd will look for a MCFG file named with the "mcfg.VF." prefix. |
||
|---|---|---|
| .. | ||
| fu-mm-device.c | ||
| fu-mm-device.h | ||
| fu-mm-utils.c | ||
| fu-mm-utils.h | ||
| fu-plugin-modem-manager.c | ||
| fu-qmi-pdc-updater.c | ||
| fu-qmi-pdc-updater.h | ||
| meson.build | ||
| README.md | ||
ModemManager
Introduction
This plugin adds support for devices managed by ModemManager.
GUID Generation
These device use the ModemManager "Firmware Device IDs" as the GUID, e.g.
USB\VID_413C&PID_81D7&REV_0318&CARRIER_VODAFONEUSB\VID_413C&PID_81D7&REV_0318USB\VID_413C&PID_81D7USB\VID_413C
Update method: fastboot
If the device supports the 'fastboot' update method, it must also report which AT command should be used to trigger the modem reboot into fastboot mode.
Once the device is in fastboot mode, the firmware upgrade process will happen as defined e.g. in the 'flashfile.xml' file. Every file included in the CAB that is not listed in the associated 'flashfile.xml' will be totally ignored during the fastboot upgrade procedure.
Update method: qmi-pdc
If the device supports the 'qmi-pdc' update method, the contents of the CAB file should include files named as 'mcfg.*.mbn' which will be treated as MCFG configuration files to download into the device using the Persistent Device Configuration QMI service.
If a device supports both 'fastboot' and 'qmi-pdc' methods, the fastboot operation will always be run before the QMI operation, so that e.g. the full partition where the MCFG files are stored can be wiped out before installing the new ones.