May be due to a mismatch between PRI/Modem images? Could you run these commands to see the details of that state?
# qmicli -d /dev/cdc-wdm0 --dms-swi-get-current-firmware
# qmicli -d /dev/cdc-wdm0 --dms-get-firmware-preference
# qmicli -d /dev/cdc-wdm0 --dms-list-stored-images
root@OpenWrt:~# qmi-firmware-update -t /dev/ttyUSB0 -U /tmp/fw/SWI9X50C_01.09.04.00.cwe
/tmp/fw/SWI9X50C_01.09.04.00_GENERIC_002.019_000.nvu -v
[27 Jun 2019, 12:22:32] [Debug] [qfu-utils] couldn't ping ModemManager:
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.ModemManager1"
does not exist
[27 Jun 2019, 12:22:32] [Debug] [qfu-image] loading file info...
[27 Jun 2019, 12:22:32] [Debug] [qfu-image] opening file for reading...
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] reading image headers...
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [0,79664946]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [400,7360]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 400 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [7360,407216]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [7760,14640]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 7760 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [14640,407216]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 14640 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 7360 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [407216,39478680]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [407616,414576]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 407616 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [414576,871292]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 414576 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [871292,1038880]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 871292 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [1038880,39478680]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 1038880 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 407216 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [39478680,79664946]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [39479080,39486040]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 39479080 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [39486040,39937028]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 39486040 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [39937028,72274126]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 39937028 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [72274126,79664946]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 72274126 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 39478680 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] validating data size...
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] preloading firmware/config/carrier...
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] firmware version: 01.09.04.00
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] config version: unknown
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] carrier: unknown
[27 Jun 2019, 12:22:32] [Debug] [qfu-image] loading file info...
[27 Jun 2019, 12:22:32] [Debug] [qfu-image] opening file for reading...
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] reading image headers...
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [0,10081]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [400,7680]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [800,7680]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 800 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 400 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [7680,10081]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image offset range: [8080,10081]
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 8080 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] image at offset 7680 is valid
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] validating data size...
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] preloading firmware/config/carrier...
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] firmware version: 01.09.04.00
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] config version: 002.019_000
[27 Jun 2019, 12:22:32] [Debug] [qfu-image-cwe] carrier: GENERIC
[27 Jun 2019, 12:22:32] [Debug] [qfu-sahara-device] opening TTY: /dev/ttyUSB0
[27 Jun 2019, 12:22:32] [Debug] [qfu-sahara-device] setting terminal in raw mode...
[27 Jun 2019, 12:22:32] [Debug] [qfu-sahara-device] waiting time for device to boot properly...
[27 Jun 2019, 12:22:34] [Debug] [qfu-sahara-device] initializing sahara protocol...
[27 Jun 2019, 12:22:37] [Debug] [qfu-updater] sahara device creation failed: no sahara response received
[27 Jun 2019, 12:22:37] [Debug] [qfu-qdl-device] opening TTY: /dev/ttyUSB0
[27 Jun 2019, 12:22:37] [Debug] [qfu-qdl-device] setting terminal in raw mode...
[27 Jun 2019, 12:22:37] [Debug] [qfu,dload-message] sent sdp:
[27 Jun 2019, 12:22:37] [Debug] [qfu-qdl-device] >> 70:00:00 [3, unframed]
[27 Jun 2019, 12:22:37] [Debug] [qfu-qdl-device] >> 7E:70:00:00:14:46:7E [7]
[27 Jun 2019, 12:22:37] [Debug] [qfu-qdl-device] << 13:70:00:00:6A:9A:7E [7]
[27 Jun 2019, 12:22:37] [Debug] [qfu-qdl-device] << 13:70:00:00 [4, unframed]
[27 Jun 2019, 12:22:37] [Debug] [qfu-updater] qdl device creation failed: unexpected response received in
dload sdp: 0x13
error: unsupported download protocol
root@OpenWrt:~# qmicli -d /dev/cdc-wdm0 --dms-swi-get-current-firmware
[/dev/cdc-wdm0] Successfully retrieved current firmware:
Model: EM7565
Boot version: SWI9X50C_01.07.02.00
AMSS version: SWI9X50C_01.07.02.00
SKU ID: 1103520
Package ID: unknown
Carrier ID: 1
Config version: 002.004_000
root@OpenWrt:~# qmicli -d /dev/cdc-wdm0 --dms-get-firmware-preference
firmware preference successfully retrieved:
[image 0]
Image type: 'modem'
Unique ID: '002.019_000'
Build ID: '01.09.04.00_GENERIC'
[image 1]
Image type: 'pri'
Unique ID: '002.019_000'
Build ID: '01.09.04.00_GENERIC'
root@OpenWrt:~# qmicli -d /dev/cdc-wdm0 --dms-list-stored-images
[/dev/cdc-wdm0] Device list of stored images retrieved:
[0] Type: 'modem'
Maximum: '4'
[modem0]
Unique ID: '?_?'
Build ID: '01.07.02.00_?'
Storage index: '1'
Failure count: '0'
[1] Type: 'pri'
Maximum: '50'
[pri0]
Unique ID: '002.004_000'
Build ID: '01.07.02.00_GENERIC'
root@OpenWrt:~#@LateParrot when you run qmi-firmware-update -t /dev/ttUSB0, is the modem in “download mode”? does it have only one ttyUSB0 exposed, or does it expose more than one TTY and also the cdc-wdm port? This is key to understand, because you may be trying to run qmi-firmware-update on the wrong place.
The “manual” update procedure in openwrt involves 3 steps:
Unfortunately this process is a bit hacky in openwrt because we don’t have udev… In a normal Linux system with udev, all this is automagically handled by qmi-firmware-update --update (instead of --update-download).
@LateParrot to recover from the “low-power stuck”, try to set firmware preference on the firmware you already have installed:
# qmicli -d /dev/cdc-wdm0 --dms-set-firmware-preference="01.07.02.00,002.004_000,GENERIC"
# qmicli -d /dev/cdc-wdm0 --dms-set-operating-mode=offline
# qmicli -d /dev/cdc-wdm0 --dms-set-operating-mode=resetroot@OpenWrt:~# qmicli -d /dev/cdc-wdm0 -p --dms-set-firmware-reference="01.09.04.00,002.019_000,GENERIC"
[/dev/cdc-wdm0] Firmware preference successfully selected
You may want to power-cycle the modem now, or just set it offline and reset it:
$> sudo qmicli ... --dms-set-operating-mode=offline
$> sudo qmicli ... --dms-set-operating-mode=reset
After reset, the modem will wait in QDL mode for new firmware.
Images to download: 'modem, pri'
root@OpenWrt:~# qmicli -d /dev/cdc-wdm0 -p --dms-set-operating-mode=offline
[/dev/cdc-wdm0] Operating mode set successfully
root@OpenWrt:~# qmicli -d /dev/cdc-wdm0 -p --dms-set-operating-mode=reset
[/dev/cdc-wdm0] Operating mode set successfully
root@OpenWrt:~# /etc/init.d/modemmanager stop
root@OpenWrt:~# qmicli -d /dev/cdc-wdm0 -p --dms-get-operating-mode
error: couldn't create QmiDevice: Couldn't query file info: Error when getting information for file “/dev/cdc-wdm0”: No such file or directory
root@OpenWrt:~# qmi-firmware-update -t /dev/ttyUSB0 -U /tmp/fw/SWI9X50C_01.09.04.00.cwe /tmp/fw/SWI9X50C_01.09.04.00_GENERIC_002.019_000.nvu
error: unsupported download protocol
root@OpenWrt:~# qmi-firmware-update -t /dev/ttyUSB0 -U /tmp/fw/SWI9X50C_01.09.04.00.cwe /tmp/fw/SWI9X50C_01.09.04.00_GENERIC_002.019_000.nvu -v
[27 Jun 2019, 13:23:21] [Debug] [qfu-utils] couldn't ping ModemManager: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.ModemManager1" does not exist
[27 Jun 2019, 13:23:21] [Debug] [qfu-image] loading file info...
[27 Jun 2019, 13:23:21] [Debug] [qfu-image] opening file for reading...
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] reading image headers...
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [0,79664946]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [400,7360]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 400 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [7360,407216]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [7760,14640]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 7760 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [14640,407216]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 14640 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 7360 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [407216,39478680]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [407616,414576]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 407616 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [414576,871292]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 414576 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [871292,1038880]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 871292 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [1038880,39478680]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 1038880 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 407216 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [39478680,79664946]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [39479080,39486040]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 39479080 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [39486040,39937028]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 39486040 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [39937028,72274126]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 39937028 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [72274126,79664946]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 72274126 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 39478680 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] validating data size...
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] preloading firmware/config/carrier...
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] firmware version: 01.09.04.00
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] config version: unknown
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] carrier: unknown
[27 Jun 2019, 13:23:21] [Debug] [qfu-image] loading file info...
[27 Jun 2019, 13:23:21] [Debug] [qfu-image] opening file for reading...
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] reading image headers...
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [0,10081]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [400,7680]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [800,7680]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 800 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 400 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [7680,10081]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image offset range: [8080,10081]
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 8080 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] image at offset 7680 is valid
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] validating data size...
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] preloading firmware/config/carrier...
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] firmware version: 01.09.04.00
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] config version: 002.019_000
[27 Jun 2019, 13:23:21] [Debug] [qfu-image-cwe] carrier: GENERIC
[27 Jun 2019, 13:23:21] [Debug] [qfu-sahara-device] opening TTY: /dev/ttyUSB0
[27 Jun 2019, 13:23:21] [Debug] [qfu-sahara-device] setting terminal in raw mode...
[27 Jun 2019, 13:23:21] [Debug] [qfu-sahara-device] waiting time for device to boot properly...
[27 Jun 2019, 13:23:23] [Debug] [qfu-sahara-device] initializing sahara protocol...
[27 Jun 2019, 13:23:26] [Debug] [qfu-updater] sahara device creation failed: no sahara response received
[27 Jun 2019, 13:23:26] [Debug] [qfu-qdl-device] opening TTY: /dev/ttyUSB0
[27 Jun 2019, 13:23:26] [Debug] [qfu-qdl-device] setting terminal in raw mode...
[27 Jun 2019, 13:23:26] [Debug] [qfu,dload-message] sent sdp:
[27 Jun 2019, 13:23:26] [Debug] [qfu-qdl-device] >> 70:00:00 [3, unframed]
[27 Jun 2019, 13:23:26] [Debug] [qfu-qdl-device] >> 7E:70:00:00:14:46:7E [7]
[27 Jun 2019, 13:23:26] [Debug] [qfu-qdl-device] << 01:00:00:00:30:00:00:00:02:00:00:00:01:00:00:00:00:04:00:00:02:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 [48]
[27 Jun 2019, 13:23:26] [Debug] [qfu-updater] qdl device creation failed: HDLC trailing control character not found
error: unsupported download protocol
I actually did try resetting the firmware preference then resetting the modem the first time I tried after updating libqmi, saw your reply before work and hastily printed it again. Setting the firmware preference to the installed version and resetting the modem was the very first thing I tried after I realized power-cycling wasn’t going to fix the issue. -set-firmware-preference still wanted to update the pri.
As of now I’ve flashed it via a usb to m.2 adapter on a windows machine and it’s working again. I very much appreciate your help, as I would have preferred not to remove the modem from the router and I wonder whether it was me or libqmi’s issue.
I’d eventually like to solve the problem as this functionality(along with many things available only in Goldenorb and other forks) needs to be accessible via luci in the main openwrt releases. I’m intending on getting in touch with Nick and seeing what his plans were and where I can start.
This is key to understand, because you may be trying to run qmi-firmware-update on the wrong place.
This is what I am expecting to be the problem, 9/10 times computer issues are a lack of understanding. Is there a good place I can read up on how these modems work and the ways to communicate with them?
hey @LateParrot the debug logs is good, but I’m afraid it doesn’t tell much 
Your log shows how when you open the ttyUSB0, there is no data received in the program, and that’s a problem. The way the protocol detection works in qmi-firmware-update is quite simple, it just opens the TTY and waits for the “hello request” sent by the modem, there is no data sent by the program beforehand, it just waits for the modem to speak first (this is done on purpose, if anything is sent to the ttyUSB0 before the hello request, the process will fail later on).
I’m still thinking that your issue could be a problem on the ttyUSB you’re using to run qmi-firmware-update, I have two theories:
I acknowledge that all this is prone to error, but again this only happens in openwrt because it doesn’t have udev. In a normal system with udev you don’t need to do all these manual steps, just running --update with the files to update and everything is automagically done, even device detection. There may be a way to improve this in openwrt, e.g. by doing some busy wait to look for the device coming back, e.g. checking every 5s for it to be exposed. That is probably a better thing than requiring all the manual steps done by the user, truth be told.
I’ve opened a new Issue in fd.o gitlab to track this enhancement qmi-firmware-update: when udev not used, loop waiting for the device reboot (#18) · Issues · Mobile broadband connectivity / libqmi · GitLab
@aleksander0m I figured it was fairly useless, just trying to show you I was actually running those commands. I definitely waited long enough, five minutes on my second go. Don’t know why I didn’t think to check dmesg though. Couldn’t see the forest for the trees I suppose. I have to spend to much time in windows, due to a lack of effective linux CNC/CAM software.
I don’t know why it would have been anywhere other than ttyUSB0. Only had the power and the ethernet cables plugged to it, and the only other package I selected in menuconfig besides luci and modemmanager was luci-proto-qmi(having problems building the latest proto-modemmanager). But I’m still new to openwrt and these cellular modems and I don’t really know what all communicates over the ttyUSB interfaces, nor have I ever seen them populated by anything other than the modem or a tethered cell phone.
Speculation is useless so I’ll take another shot at it this weekend. Can I just attempt to downgrade in a similar fashion? I’d use the last At&t release.
Hello @LateParrot I would like to update the EM7565 under OpenWRT too, did you finally find a way to properly accomplish it?
@hadrien.toma what issues are you having? I’ve done myself lately a couple of upgrades without issues.
Hello @aleksander0m , for the moment I am searching for information on how to do it in the rules of art, may you point me to the correct procedure?
I first need to update the EM7565 then to make a bridge between it and a Wi-Fi modem (in case you have documentation for this configuration too).
I documented my last EM7565 update on OpenWrt here:
https://lists.freedesktop.org/archives/libqmi-devel/2019-November/003166.html
Ignore the first part with the debug output. Look for the prompts (root at wrt1900ac-1) to find the 3 necessary commands. File names, versions and device names must be changed of course.
Note in particular that my QDL device is ttyUSB4 because I have 4 other USB serial ports. Yours will probably be ttyUSB0, but this must be verified by eg looking at dmesg after resetting the modem.
Also, run qmi-firmware-update --help-examples to get several examples of how to upgrade the device. The example that applies to the EM7565 should be equivalent to the MC7354 one.
Thank you very much to both of you 
! I will check this out and come back here to share feedbacks.
Hi,
I have a similar problem, even though the debug output looks a bit different. I have issued the -U command from single-TTY mode, it’s an EM7565 and the current FW is rather old. I understand it may be easier to plug the modem into an USB adapter, but I’s like to do it in OpenWRT 
[/dev/cdc-wdm0] Successfully retrieved current firmware:
Model: EM7565
Boot version: SWI9X50C_01.00.02.00
AMSS version: SWI9X50C_01.00.02.00
SKU ID: 1103520
Package ID: unknown
Carrier ID: 1
Config version: unknown
# qmi-firmware-update -t /dev/ttyUSB0 -U SWI9X50C_01.14.02.00.cwe SWI9X50C_0
1.14.02.00_GENERIC_002.035_000.nvu --ignore-mm-runtime-check --verbose
[18 Apr 2021, 20:48:30] [Debug] [qfu-image] loading file info...
[18 Apr 2021, 20:48:30] [Debug] [qfu-image] opening file for reading...
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] reading image headers...
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [0,80241623]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [400,7360]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 400 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [7360,411416]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [7760,14640]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 7760 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [14640,411416]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 14640 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 7360 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [411416,39979141]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [411816,418776]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 411816 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [418776,875492]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 418776 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [875492,1043080]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 875492 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [1043080,39979141]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 1043080 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 411416 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [39979141,80241623]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [39979541,39986501]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 39979541 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [39986501,40437529]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 39986501 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [40437529,72856949]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 40437529 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [72856949,80241623]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 72856949 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 39979141 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] validating data size...
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] preloading firmware/config/carrier...
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] firmware version: 01.14.02.00
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] config version: unknown
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] carrier: unknown
[18 Apr 2021, 20:48:30] [Debug] [qfu-image] loading file info...
[18 Apr 2021, 20:48:30] [Debug] [qfu-image] opening file for reading...
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] reading image headers...
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [0,10159]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [400,7680]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [800,7680]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 800 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 400 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [7680,10159]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image offset range: [8080,10159]
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 8080 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] image at offset 7680 is valid
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] validating data size...
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] preloading firmware/config/carrier...
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] firmware version: 01.14.02.00
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] config version: 002.035_000
[18 Apr 2021, 20:48:30] [Debug] [qfu-image-cwe] carrier: GENERIC
[18 Apr 2021, 20:48:30] [Debug] [qfu-sahara-device] opening TTY: /dev/ttyUSB0
[18 Apr 2021, 20:48:30] [Debug] [qfu-sahara-device] setting terminal in raw mode...
[18 Apr 2021, 20:48:30] [Debug] [qfu-sahara-device] waiting time for device to boot properly...
[18 Apr 2021, 20:48:32] [Debug] [qfu-sahara-device] initializing sahara protocol...
[18 Apr 2021, 20:48:35] [Debug] [qfu-updater] sahara device creation failed: no sahara response received
[18 Apr 2021, 20:48:35] [Debug] [qfu-qdl-device] opening TTY: /dev/ttyUSB0
[18 Apr 2021, 20:48:35] [Debug] [qfu-qdl-device] setting terminal in raw mode...
[18 Apr 2021, 20:48:35] [Debug] [qfu,dload-message] sent sdp:
[18 Apr 2021, 20:48:35] [Debug] [qfu-qdl-device] >> 70:00:00 [3, unframed]
[18 Apr 2021, 20:48:35] [Debug] [qfu-qdl-device] >> 7E:70:00:00:14:46:7E [7]
[18 Apr 2021, 20:48:35] [Debug] [qfu-qdl-device] << 04:00:00:00:10:00:00:00:07:00:00:00:01:00:00:00 [16]
[18 Apr 2021, 20:48:35] [Debug] [qfu-updater] qdl device creation failed: HDLC trailing control character not found
error: unsupported download protocol```This looks like a SAHARA transfer error with status code 1 - “invalid command”. But I can’t tell why from the log you sent. Maybe @aleksander0m knows what goes on here?
This looks like the module didn’t reboot into download mode, and the ttyUSB0 you’re talking to is really DIAG/QCDM. In this state, does the module also expose the cdc-wdm port and the wwan port? That would confirm this assumption, as in download mode there is only one single port exposed.
Could you retry with the additional --override-download option? That should request to force downloading, even if all the images already exist in the module.
I seem to not be able to perform the reset operation anymore (it worked in my last attempt).
I tried:
root@LEDE:/mnt/tmp# qmicli -d /dev/cdc-wdm0 -p --dms-set-firmware-
preference=“01.00.02.00,001.012_000,GENERIC”
root@LEDE:/mnt/tmp# qmicli -d /dev/cdc-wdm0 --dms-set-operating-mode=offline
[/dev/cdc-wdm0] Operating mode set successfully
root@LEDE:/mnt/tmp# qmicli -d /dev/cdc-wdm0 --dms-set-operating-mode=reset
[/dev/cdc-wdm0] Operating mode set successfully
but the 3 ttyUSB interfaces don’t anymore disappear, I also tried:
root@LEDE:~# qmi-firmware-update -t /dev/ttyUSB0 -b --ignore-mm-runtime-check
error: reseter operation finished: couldn't run reset operation
but I keep on having the 3 ttyUSB devices ?!
On top --override-download doesn’t seem to be a known optione to “qmi-firmware-update”. qmi-firmware-update 1.24.12
Tried once more (I didn’t even notice that the download mode was finally active), then it seemed to work, uploaded up to 9x %, but then:
root@LEDE:/mnt/sda1# cd /mnt/sda1;qmi-firmware-update -t /dev/ttyUSB0 -U SWI9X50C_01.14.02.00.cwe SWI9X50C_01.14.02.00_GENERIC_002.035_000.nvu --ignore-mm-runtime-check
downloading cwe image: SWI9X50C_01.14.02.00.cwe (80.2 MB)...
finalizing download... (may take several minutes, be patient)
error: error downloading image: couldn't teardown download: unexpected firehose response received: value=NAK, rawmode=false
Now I’m back to “unsupported download protocol”