[Solved] EM7565 Firmware Update from 01.00.02.00 to 01.07.00.00

IoT Modules MC/EM Series
21

I have some additional information regarding a suitable chassis/adapter for firmware update:
The signal line for Dynamic Power Control (DPR), located on pin 25, must not be attached to GND, when doing a firmware update (or when issuing the AT!BOOTHOLD) command. Otherwise the EM7565 comes up in normal mode, instead of the download mode.
In the chassis I mentioned above the DPR signal was set to GND via jumper (default from stock). In contrast, the M.2 to MiniPCIe adapter leaves this pin floating.
Removing the jumper connection did the trick for that chassis and the included module comes up with PID 9090 instead of 9091 after issuing AT!BOOTHOLD.

Maybe the information about this behaviour might be included into the manuals and release notes, as I didn’t find anything about it in those documents.

Regards
Robert

1 Like
22

Hi Robert,
first of all, thank you very much for the effort and the detailed instructions!
Did you use the generic-version of the 01.05.01.00 firmware? If so, could you maybe tell me the MD5 hash of the .exe-file?
Regards
Jens

23

Hi Jens,

yes, I used the generic version. The file is named 9999999_9907259_SWI9X50C_01.05.01.00_00_GENERIC_001.028_000.exe and its MD5 hash is EA117CD92526345B8DD7EE1B43B5C9B4

Regards
Robert

24

Perfect, thank you very much!

25

Hi Robert.

Thanks for the info about DPR signal (pin 25). We have been trying to put the EM7565 in Download Mode (PID 9090) without success for quite some time.
If it helps, in our case the DPR pin was connected to 1.8V. That does not work either. DPR must be floating.

I agree this info could be added somewhere in manual and release note.

Regards,
Livio.

26

I am stuck at Qdownloader here as well. If I understand correctly, I just need to try and update to an intermediate firmware build and then try the most recent build twice?

Also, where do I get a hold of an intermediate build?

Thank you for all your great posts folks.

27

Direct from Sierra Wireless:
https://source.sierrawireless.com/resources/airprime/minicard/75xx/fw/9999999_9907259_swi9x50c_01,-d-,05,-d-,01,-d-,00_00_generic_001,-d-,028_000/

4 Likes
28

Thanks internet friend!

29

Hi, mlv

Please help!

Please give me a link for loading the firmware: SWI9X50C_01.02.01.xx, Issue 7.
My modem EM7565 was stuck in Qdloader mode.
There are no access in the teams.

========================================================================
$ sudo systemctl disable ModemManager
$ sudo systemctl stop ModemManager

$ lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 138a:00ab Validity Sensors, Inc.
Bus 001 Device 020: ID 1199:9090 Sierra Wireless, Inc. QUSB__BULK
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 0408:5373 Quanta Computer, Inc. HP HD Camera
Bus 001 Device 006: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ sudo qmi-firmware-update -v -b -s 1:20

[19 окт 2022, 21:30:53] [Debug] [bus 001, dev 020] sysfs path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-5
[19 окт 2022, 21:30:53] [Debug] [qfu-udev] peer port for ‘/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5’ found: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-0:1.0/usb2-port2
[19 окт 2022, 21:30:53] [Debug] [qfu-utils] couldn’t ping ModemManager: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name “org.freedesktop.ModemManager1” does not exist
[19 окт 2022, 21:30:53] [Debug] [qfu,device-selection] single cdc-wdm device requested in sysfs path ‘/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5’
[19 окт 2022, 21:30:53] [Debug] [qfu,device-selection] couldn’t find any device to use
[19 окт 2022, 21:30:53] [Debug] [qfu,device-selection] multiple tty devices requested in sysfs path ‘/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5’
[19 окт 2022, 21:30:53] [Debug] [qfu,device-selection] device found: /dev/ttyUSB0
[19 окт 2022, 21:30:53] [Debug] [qfu-at-device,ttyUSB0] opening TTY
[19 окт 2022, 21:30:53] [Debug] [qfu-at-device,ttyUSB0] setting up serial port…
[19 окт 2022, 21:30:53] [Debug] [qfu-at-device,ttyUSB0] >> AT!BOOTHOLD
[19 окт 2022, 21:30:53] [Debug] [qfu-at-device,ttyUSB0] <<
[19 окт 2022, 21:30:53] [Debug] [qfu-reseter] error: unknown error
[19 окт 2022, 21:30:53] [Debug] [qfu-at-device,ttyUSB0] >> AT!BOOTHOLD
[19 окт 2022, 21:30:53] [Debug] [qfu-at-device,ttyUSB0] <<
[19 окт 2022, 21:30:53] [Debug] [qfu-reseter] error: unknown error
[19 окт 2022, 21:30:53] [Debug] [qfu-at-device,ttyUSB0] >> AT!BOOTHOLD
[19 окт 2022, 21:30:53] [Debug] [qfu-at-device,ttyUSB0] <<
[19 окт 2022, 21:30:53] [Debug] [qfu-reseter] error: unknown error
error: reseter operation finished: couldn’t run reset operation

$ sudo qmi-firmware-update -p -s 1:20 -U
SWI9X50C_01.05.01.00.cwe
SWI9X50C_01.05.01.00_GENERIC_001.028_000.nvu

downloading cwe image: SWI9X50C_01.05.01.00.cwe (80,2 МБ)…
finalizing download… (may take several minutes, be patient)
successfully downloaded in 125,97s (636,8 кБ/s)
downloading cwe image: SWI9X50C_01.05.01.00_GENERIC_001.028_000.nvu (3,9 кБ)…
finalizing download… (may take several minutes, be patient)
successfully downloaded in 0,05s (80,7 кБ/s)
rebooting in normal mode…
firmware update operation finished successfully

$ lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 138a:00ab Validity Sensors, Inc.
Bus 001 Device 022: ID 1199:9090 Sierra Wireless, Inc. QUSB__BULK
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 0408:5373 Quanta Computer, Inc. HP HD Camera
Bus 001 Device 006: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

30

Good afternoon!
Please help me.

The modem is still in QDL mode.
Tests were carried out on adapters:
M.2 → USB2.0
M.2 → USB3.0
M.2 → mini PCI-E → USB2.0
M.2 → mini PCI-E → USB3.0

Firmware
SWI9X50C_01.05.01.00
SWI9X50C_01.14.13.00

Ubuntu 22.04.1

dmitry@hp-ubDmitry:~$ lsusb
Bus 001 Device 042: ID 1199:9090 Sierra Wireless, Inc. QUSB__BULK

dmitry@hp-ubDmitry:~$ lsusb -t
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 4: Dev 42, If 0, Class=Vendor Specific Class, Driver=qcserial, 480M

MBPL_SDK_R28_ENG5-fwdwl

dmitry@hp-ubDmitry:~$ sudo ./Modem/MBPL_SDK_R28_ENG5-fwdwl/bin/fwdwl-litehostx86_64 -c QMI -m 4 -d /dev/ttyUSB0 -f
./Modem/SWI9X50C_01.14.13.00/

Application version: 1.0.2207.1
INFO: QDL Port: /dev/ttyUSB0
INFO: Device Path:
INFO: FW Path: ./Modem/SWI9X50C_01.14.13.00/
Target image Info:
Carrier :GENERIC
FW Version :01.14.13.00
Model ID :SWI9X50C
Package ID :000
PRI Version:002.048
SKU :9999999
Modem is in QDL mode. Continuing FW download
Waiting for modem to come up in BOOT and HOLD mode …
BOOT and HOLD Mode. Downloading firmware …
Downloading: ./Modem/SWI9X50C_01.14.13.00//SWI9X50C_01.14.13.00_GENERIC_002.048_000.nvu
FW download failed: eSDP_FWDWL_ERR_FIREHOSE_DEV_REPORT_ERR(121)
Exiting Application!!!

fwdwl.log
…
[2526][7]Current mode: -1, previous max_reads_allowed: 298
[2526][7]Read payload [291]
[2526][7]Complete target 1: <?xml version="1.0" encoding="UTF-8" ?>
[2526][7]Current mode: 11, previous max_reads_allowed: 297
[2526][7]Device error code received, exiting application.

lite-fwSLQS04.00.27

dmitry@hp-ubDmitry:~$ sudo ./Modem/SLQS04.00.27/SampleApps/lite-fw-download/bin/fwdwl-litehostx86_64
-d /dev/ttyUSB0
-m 4
-f ./Modem/SWI9X50C_01.14.13.00/

Modem Manager rules Tested
litefw version :lite-fwSLQS04.00.27
INFO: QDL Port : /dev/ttyUSB0
INFO: Device Path: /dev/qcqmi0
INFO: FW Path : ./Modem/SWI9X50C_01.14.13.00/
Package Info:
Carrier :GENERIC
FW Version :01.14.13.00
Model ID :SWI9X50C
Package ID :000
PRI Version:002.048
SKU :9999999
Part Number:9907259
file_type : 6
Modem is QDL mode. Skipping FW preference setting
Waiting for modem to come up in BOOT and HOLD mode …
BOOT and HOLD Mode. Downloading firmware …
litefw_DownloadFW failed: 100
Exiting Application!!!

qmi-firmware-update

dmitry@hp-ubDmitry:~$ sudo qmi-firmware-update -p -d 1199:9090 -U
./Modem/SWI9X50C_01.14.13.00/SWI9X50C_01.14.13.00.cwe
./Modem/SWI9X50C_01.14.13.00/SWI9X50C_01.14.13.00_GENERIC_002.048_000.nvu
–ignore-mm-runtime-check

downloading cwe image: SWI9X50C_01.14.13.00.cwe (80,2 МБ)…
finalizing download… (may take several minutes, be patient)
successfully downloaded in 14,73s (5,4 МБ/s)
downloading cwe image: SWI9X50C_01.14.13.00_GENERIC_002.048_000.nvu (31,3 кБ)…
finalizing download… (may take several minutes, be patient)
error: error downloading image: couldn’t teardown download: unexpected firehose response received: value=NAK, rawmode=false

Windows 10

FDT version: 1.0.1902.1
Awaiting suitable port or adapter …
Switching to streaming mode …
Downloading images …
Writing image |
Flashing image /
Awaiting adapter …
Enabling selective suspend …
Firmware download failed.
Primary error code: 14 - No MBN adapter available.
Secondary error code: 0 - Not applicable.
Device error code: 0x0 - Unknown device error code.

Preexisting images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:
Final images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:

OEM PRI:

IMEI:

Total time elapsed: 257703 ms.

Images downloaded:
Image ID: ??
Build ID: 01.14.13.00?
write time: 15797 ms
additional flash time: 172 ms

Time to reset to application mode: -1 ms.

Press Enter to continue … qmi-firmware-update

unpacked into a folder
run with admin rights
Sierra Wireless EM7565 in QDLoader -- Restoring the Modem COM Port - WIRELESS JOINT

…
SWI9X50C_01.14.13.00_GENERIC_002.048_000.nvu
SWI9X50C_01.14.13.00.cwe
GobiApi.dll
fdt2.exe (run with admin rights)
combo_script.txt