Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't restore EM7565 from QDLoader mode #125

Open
msdnna opened this issue May 27, 2022 · 3 comments
Open

Can't restore EM7565 from QDLoader mode #125

msdnna opened this issue May 27, 2022 · 3 comments
Labels
wontfix This will not be worked on

Comments

@msdnna
Copy link

msdnna commented May 27, 2022

Due to the initially incorrect firmware for the latest firmware (bypassing intermediate ones) using the qmi-firmware-update method, my EM7565 went into QDLoader mode and now cannot boot normally. I tried to act according to the instructions of @danielewood Sierra-Linux-QMI-SDK.md, but all to no avail - at first, the firmware via fwdwl-litehostx86_64 to the version SWI9X50C_01.05.01.00_00_GENERIC_001.028_000 went fine, stopping at the message "Waiting for modem to come up in ONLINE mode ...", while the modem was loaded into QDL again, and now the firmware is completely terminated with the message "litefw_DownloadFW failed: 100". Multiple attempts were made to flash the version SWI9X50C_01.05.01.00_00_GENERIC_001.028_000, then to SWI9X50C_01.07.02.00_GENERIC_002.004_000, as well as the latest available with all intermediate versions found on the network:

  • SWI9X50C_01.05.01.00_00_GENERIC_001.028_000
  • SWI9X50C_01.07.02.00_00_GENERIC_002.004_001
  • SWI9X50C_01.08.04.00_00_GENERIC_002.012_000
  • SWI9X50C_01.09.04.00_00_GENERIC_002.019_000
  • SWI9X50C_01.11.00.00_00_GENERIC_002.023_000
  • SWI9X50C_01.14.02.00_00_GENERIC_002.035_000
  • SWI9X50C_01.14.02.00_00_GENERIC_002.035_003

All to no avail, the behavior of the modem does not change. All the instructions I found on the net do not work.
There is an assumption that the modem has finally become corrupted, but I would like to believe that it can be restored.

dmesg output:
[170555.087573] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
[170555.087659] usb 1-1: USB disconnect, device number 48
[170555.087733] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[170555.087743] qcserial 1-1:1.0: device disconnected
[170556.192998] usb 1-1: new high-speed USB device number 49 using xhci_hcd
[170556.321590] usb 1-1: New USB device found, idVendor=1199, idProduct=9090, bcdDevice= 0.00
[170556.321594] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[170556.321595] usb 1-1: Product: QUSB__BULK
[170556.321596] usb 1-1: Manufacturer: Sierra Wireless, Incorporated
[170556.321597] usb 1-1: SerialNumber: UF72338581040421
[170556.323774] qcserial 1-1:1.0: Qualcomm USB modem converter detected
[170556.323881] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
[170599.828919] usb 1-1: USB disconnect, device number 49
[170599.829106] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[170599.829156] qcserial 1-1:1.0: device disconnected
[170651.334305] usb 1-1: new high-speed USB device number 50 using xhci_hcd
[170651.465611] usb 1-1: New USB device found, idVendor=1199, idProduct=9090, bcdDevice= 0.00
[170651.465615] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[170651.465616] usb 1-1: Product: Sierra Wireless EM7565
[170651.465617] usb 1-1: Manufacturer: Sierra Wireless, Incorporated
[170651.465618] usb 1-1: SerialNumber: UF72338581040421
[170651.467390] qcserial 1-1:1.0: Qualcomm USB modem converter detected
[170651.467574] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
[170651.467634] usb 1-1: USB disconnect, device number 50
[170651.467774] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[170651.467786] qcserial 1-1:1.0: device disconnected
[170794.425608] usb 1-1: new high-speed USB device number 51 using xhci_hcd
[170794.557281] usb 1-1: New USB device found, idVendor=1199, idProduct=9090, bcdDevice= 0.00
[170794.557285] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[170794.557286] usb 1-1: Product: QUSB_Fast_Enum.
[170794.557287] usb 1-1: Manufacturer: Sierra Wireless, Incorporated
[170794.557288] usb 1-1: SerialNumber: UF72338581040421
[170794.559095] qcserial 1-1:1.0: Qualcomm USB modem converter detected
[170794.559214] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
[170794.559287] usb 1-1: USB disconnect, device number 51
[170794.559390] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[170794.559400] qcserial 1-1:1.0: device disconnected
[170795.663773] usb 1-1: new high-speed USB device number 52 using xhci_hcd
[170795.794380] usb 1-1: New USB device found, idVendor=1199, idProduct=9090, bcdDevice= 0.00
[170795.794384] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[170795.794386] usb 1-1: Product: QUSB__BULK
[170795.794387] usb 1-1: Manufacturer: Sierra Wireless, Incorporated
[170795.794388] usb 1-1: SerialNumber: UF72338581040421
[170795.796319] qcserial 1-1:1.0: Qualcomm USB modem converter detected
[170795.796407] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0

@msdnna msdnna added the wontfix This will not be worked on label May 27, 2022
@kkonradpl
Copy link

kkonradpl commented Jun 6, 2022

I have the same problem with EM7565 (Lenovo 1199/90C3) from China, originally with SWI9X50C_00.03.02.00 firmware.
I changed the VID & PID to 1199/9091 and tried to update the FW to a recent one which resulted in a bootloop and fallback to bootloader.

After many hours of fiddling with different FWs, at some point EM7565 restored… the stock SWI9X50C_00.03.02.00 version (!) on its own. Then I tried to follow the instructions from this repository (update to SWI9X50C_01.05.01.00_00 as immediate step), but again with no luck – the bootloader shows up and nothing more.

I can still update the FW using both qmi-firmware-update (no errors) and fwdwl-litehostx86_64 (CWE seems to be fine, but NVU fails with NAK message). After that, it simply bootloops a few times and falls back to bootloader.

@gsmantenna
Copy link

I have same issue with @kkonradpl ,I have 2 old em7565 fw SWI9X50C_00.03.02.00 and SWI9X50C_00.06.02.00 ,both fail upgrade at CWE
upgradde log:
364][7]**************************************************
[364][7]Copyright: © 2015-2020 Sierra Wireless, Inc. all rights reserved
[364][7]lite-fw is only permitted to use on Sierra Wireless Modem
[364][7]lite-fw version lite-fwSLQS04.00.27
[364][7]**************************************************
[364][7]litefw_getFileType: eFW_TYPE_CWE
[364][7]QDL Port :/dev/cdc-wdm3
[364][7]OpenSendTTYFD9x07 error from TCSANOW

[369][7]Need PRI
[369][7]litefw_getFileType: eFW_TYPE_CWE
[369][7]File Type :2
[369][7]sectorsize:4096, number of chunk data:19584
[369][7]File Total Size : number of chunk data 19584(cwe:80212820 + nvu:0)
[374][7]read timeout
[374][7]payload [0]

[374][7]sahara message might be missed.
[374][7]Lite9x07Download and 2464
[374][7]Tx:�

[374][7]e9x07SendSaharaRsp Rsp
[374][7]payload [16]

[374][7]Tx:�

[374][7]e9x07SendSaharaRsp Rsp
[374][7]payload [16]

[379][7]read timeout
[379][7]payload [0]

[384][7]read timeout
[384][7]payload [0]

[384][7]fail switch to Firehose mode

@OzzyFox
Copy link

OzzyFox commented Feb 27, 2023

I have EM7565 that stuck in QDLoader port (1199:9090)
Tried to flash it:

ubuntu-mate@ubuntu-mate:~$ ./fwdwl-litehostx86_64 -d /dev/$devpath --modelfamily 4 --logfile "fwdwl-lite-$devpath.log" -e 1 --fwpath "./swi_fw0105/"
litefw version :lite-fwSLQS04.00.15 
INFO: QDL Port  : /dev/
INFO: Device Path: /dev/qcqmi0
INFO: FW  Path  : ./swi_fw0105/
Package Info:
Carrier    :GENERIC
FW Version :01.05.01.00
Model ID   :SWI9X50C
Package ID :000
PRI Version:001.028
SKU        :9999999
GetDeviceMode: ERROR! Unknown modem state
Modem not in correct state
Exiting Application!!!

Tied to flash it with all FW in Windows - no luck
Tried to flash with FDT tool - same
Any suggestions? Thanks for answer!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants