It seems the failure is occurring at the last chunk (#61). The status returned in "134". Please advise if any idea what this error status means?
Bjørn, I saw one of your post in the mailing list regarding qmi-firmware-update failure? Any idea what is this error? Below is the log from qmi-firmware-update with "-v" option [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] sent write-unframed-req: [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] sequence: 60 [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] chunk size: 1048576 [08 Nov 2023, 03:56:49] [Debug] [qfu-qdl-device] >> 27:3C:00:00:00:00:00:00:00:10:00:7B:7F:1D:92:DB:39:68:AE:2D:CE:8D:08:A5:12:20:BD:78:DA:6B:6F:52:21:6 [08 Nov 2023, 03:56:49] [Debug] [qfu-qdl-device] << 7E:28:3C:00:00:00:00:00:00:00:FE:EF:7E [13] [08 Nov 2023, 03:56:49] [Debug] [qfu-qdl-device] << 28:3C:00:00:00:00:00:00:00 [9, unframed] [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] received write-unframed-rsp [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] status: 0 [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] sequence: 60 [08 Nov 2023, 03:56:49] [Debug] [qfu-image] reading chunk #61 [08 Nov 2023, 03:56:49] [Debug] [qfu-image] chunk #61 size: 462805 bytes [08 Nov 2023, 03:56:49] [Debug] [qfu-image] chunk #61 offset: 63963536 bytes [08 Nov 2023, 03:56:49] [Debug] [qfu-image] chunk #61 successfully read [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] sent write-unframed-req: [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] sequence: 61 [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] chunk size: 462805 [08 Nov 2023, 03:56:49] [Debug] [qfu-qdl-device] >> 27:3D:00:00:00:00:00:D5:0F:07:00:2D:57:CF:B7:2D:1D:13:00:53:55:E6:1A:B9:C1:9D:65:78:7F:02:5E:9F:85:7 error: error downloading image: couldn't write in session: operation returned an error status: 134 [08 Nov 2023, 03:56:49] [Debug] [qfu-qdl-device] << 7E:28:3D:00:00:00:00:00:86:00:5D:B6:7E [13] [08 Nov 2023, 03:56:49] [Debug] [qfu-qdl-device] << 28:3D:00:00:00:00:00:86:00 [9, unframed] [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] received write-unframed-rsp [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] status: 134 [08 Nov 2023, 03:56:49] [Debug] [qfu,qdl-message] sequence: 61 ________________________________ From: Amol Lad <amol....@4rf.com> Sent: Tuesday, November 7, 2023 11:05 AM To: ModemManager (development) <modemmanager-devel@lists.freedesktop.org> Subject: qmicli-firmware-update failure on a batch of EM7455 Hi Aleksander, I'm facing a strange issue. I've received a new batch of Sierra EM7455 modems and trying to update firmware in the modem and I get following error message: # qmi-firmware-update -t /dev/ttyUSB0 -U SWI9X30C_02.33.03.00.cwe SWI9X30C_02.33.03.00_VERIZON_002.079_001.nvu finalizing download... (may take more than one minute, be patient) error: error downloading image: couldn't write in session: operation returned an error status: 134 Any idea what error status 134 could mean? This is definitely something to do with the modem and I am able to update EM7455 from an older lot just fine.. How to enable more debugs in qmicli-firmware-update to understand what error modem is reporting? Thanks, Amol
