After power problem, new ID USB on 05C6:9008. Why?

IoT Modules
1

Hello,
Due to power supply problems, an RC7620-1 modem no longer appears as a USB device. To be able to reload its firmware, I set the Boot Pin to 0.
But the modem now has the USB ID 05C6:9008 which is different from the usual 1199:68C0.
With the fwdwl-litearm tool I can’t download it.
Here is the result of the log.

IMPORTANT: The drivers are in the kernel

[04:25:15.249][1]System date/time: 01/01/2018 4:25:15
[04:25:15.250][1]1.0.2303.0
[04:25:15.272][1]Kernel: Linux REDY 4.14.281-1.1.0 #1 PREEMPT Wed Jun 8 10:32:05 CEST 2022 armv7l GNU/Linux

[04:25:15.273][1]File not found: /sys/module/qcserial/version

[04:25:15.273][1]Unable to get qcserial driver’s version from file ‘/sys/module/qcserial/version’ trying using modinfo

[04:25:15.286][1]Unable to log qcserial version info. Drivers from MBPL R17 or newer are required.
[04:25:15.287][1]File not found: /sys/module/usb_wwan/version

[04:25:15.287][1]Unable to get usb_wwan driver’s version from file ‘/sys/module/usb_wwan/version’ trying using modinfo

[04:25:15.300][1]Unable to log usb_wwan version info. Drivers from MBPL R17 or newer are required.
[04:25:15.301][1]File not found: /sys/module/cdc_mbim/version

[04:25:15.301][1]Unable to get cdc_mbim driver’s version from file ‘/sys/module/cdc_mbim/version’ trying using modinfo

[04:25:15.314][1]Unable to log cdc_mbim version info. Drivers from MBPL R17 or newer are required.
[04:25:15.314][1]File not found: /sys/module/qmi_wwan/version

[04:25:15.314][1]Unable to get qmi_wwan driver’s version from file ‘/sys/module/qmi_wwan/version’ trying using modinfo

[04:25:15.327][1]Unable to log qmi_wwan version info. Drivers from MBPL R17 or newer are required.
[04:25:15.328][1]File not found: /sys/module/mhictrl/version

[04:25:15.328][1]Unable to get mhictrl driver’s version from file ‘/sys/module/mhictrl/version’ trying using modinfo

[04:25:15.341][1]Unable to log mhictrl version info. Drivers from MBPL R17 or newer are required.
[04:25:15.341][1]File not found: /sys/module/mhinet/version

[04:25:15.342][1]Unable to get mhinet driver’s version from file ‘/sys/module/mhinet/version’ trying using modinfo

[04:25:15.354][1]Unable to log mhinet version info. Drivers from MBPL R17 or newer are required.
[04:25:15.355][1]File not found: /sys/module/mhitty/version

[04:25:15.355][1]Unable to get mhitty driver’s version from file ‘/sys/module/mhitty/version’ trying using modinfo

[04:25:15.368][1]Unable to log mhitty version info. Drivers from MBPL R17 or newer are required.
[04:25:15.369][1]/usr/sbin/fwdwl-litearm
[04:25:15.369][1]-c
[04:25:15.369][1]QMI
[04:25:15.369][1]-d
[04:25:15.369][1]/dev/ttyUSB0
[04:25:15.369][1]-p
[04:25:15.369][1]/dev/cdc-wdm0
[04:25:15.369][1]-m4
[04:25:15.369][1]-f
[04:25:15.369][1]/var/
[04:25:15.369][1]-l
[04:25:15.369][1]testsr.log
[04:25:15.437][7]User specified read block size: 0 bytes
[04:25:15.438][7]**************************************************
[04:25:15.438][7]Copyright: © 2015-2017 Sierra Wireless, Inc. all rights reserved
[04:25:15.438][7]lite-fw is only permitted to be used with Sierra Wireless Modems
[04:25:15.438][7]lite-fw version lite-fwMBPL_SDK_R32_ENG2
[04:25:15.438][7]**************************************************
[04:25:15.438][6]Device is in BOOT&HOLD mode.
[04:25:15.439][6]Images list:
[04:25:15.439][6]Image[0]: /var//RC76xx_Release9.6.1_GENERIC_7620.spk
[04:25:15.462][7]find_dev_ss_loc: Do not found any USB devices with VID(0x1199)
[04:25:15.462][3]disable_ss: Failed to find device SS path. SS stays unchanged.
[04:25:15.462][6]litefw_download: Adjust download_type from 0 to REG_DWLD as device is already in B&H mode.
[04:25:15.462][7]Waiting for modem to come up in B&H mode …
[04:25:16.465][7]Modem is in B&H mode. Downloading firmware …
[04:25:16.498][7]find_dev_ss_loc: Do not found any USB devices with VID(0x1199)
[04:25:16.499][3]disable_ss: Failed to find device SS path. SS stays unchanged.
[04:25:16.499][7]QDL Port :/dev/ttyUSB0
[04:25:22.000][7]read timeout
[04:25:22.000][7]Read payload [0]
[04:25:22.000][1]Read 0 bytes
*[04:25:22.001][1]<- *
[04:25:22.001][7]Sahara HELLO message might be missed. Resending Sahara HELLO response.
[04:25:22.001][7]Current mode: 0, previous max_reads_allowed: 29
[04:25:22.001][1]Send 48 bytes
[04:25:22.001][1]-> 02 00 00 00 30 00 00 00 02 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00 01 00 00 00 02 00 00 00 …0…
[04:25:22.002][1]-> 03 00 00 00 04 00 00 00 05 00 00 00 06 00 00 00 …
[04:25:22.002][7]Sahara Hello Rsp sent successfully, max_reads_allowed reset to 30
[04:25:22.503][7]read timeout
[04:25:22.503][7]Read payload [0]
[04:25:22.503][1]Read 0 bytes
*[04:25:22.503][1]<- *
[04:25:22.503][3]Device not responsive to SAHARA HELLO RESPONSE, need a power cycle.

Do you have any idea how to recover the modem?
Thanks for your help

2

VID/PID “05c6:9008” is the Qualcomm VID/PID.
There is some boot up problem and makes to such enumeration.

Currently i don’t see any method to recover this.

3

Thank you for your reply, even if it’s not satisfactory.

So you’re saying that I can throw my modem in the bin?

That’s not a tenable situation at a time when everything has to be recycled.
I’m still convinced that there’s a way of recovering this modem.
I’m waiting for you to be more specific, even if it must be complicated.

Thank you for your help.

4

Have you contacted distributor?
Have you tried fdt tool in windows?

5

Hello,
No, I haven’t contacted the distributor yet. But what could they do for us?
can you tell me more about the windows fdt tool?

6

you contact distributor with business case, then you should get the official support to have deeper investigation for you.

fdt tool:
https://source.sierrawireless.com/resources/airprime/software/fdt/