# RC7620-1 not available after update with "qmi-update-firmware"

**URL:** <https://forum.sierrawireless.com/t/rc7620-1-not-available-after-update-with-qmi-update-firmware/30723>\
**Category:** RC76\
**Tags:** fw-upgrade\
**Created:** [September 27, 2023, 8:04am UTC](https://forum.sierrawireless.com/t/rc7620-1-not-available-after-update-with-qmi-update-firmware/30723 "2023-09-27T08:04:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![JFTWIT](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@JFTWIT](https://forum.sierrawireless.com/u/JFTWIT)\
**Post date:** [September 27, 2023, 8:04am UTC](https://forum.sierrawireless.com/t/rc7620-1-not-available-after-update-with-qmi-update-firmware/30723/1 "2023-09-27T08:04:18Z")

</div>

Hello,

after updating an RC7620-1 with the latest firmware, the modem loops on the USB connect/disconnect part. I think it keeps rebooting.  
What is the method for recovering the modem?

Thank you for your help.

usb 1-1.1: new high-speed USB device number 113 using ci\_hdrc  
usb 1-1.1: config 1 has an invalid interface number: 8 but max is 3  
usb 1-1.1: config 1 has no interface number 1  
usb 1-1.1: New USB device found, idVendor=1199, idProduct=68c0  
usb 1-1.1: New USB device strings: Mfr=3, Product=2, SerialNumber=4  
usb 1-1.1: Product: Sierra Wireless RC7620-1  
usb 1-1.1: Manufacturer: Sierra Wireless, Incorporated  
usb 1-1.1: SerialNumber: 7T2473515007A120  
qcserial 1-1.1:1.0: Qualcomm USB modem converter detected  
usb 1-1.1: Qualcomm USB modem converter now attached to ttyUSB0  
qcserial 1-1.1:1.2: Qualcomm USB modem converter detected  
usb 1-1.1: Qualcomm USB modem converter now attached to ttyUSB1  
qcserial 1-1.1:1.3: Qualcomm USB modem converter detected  
usb 1-1.1: Qualcomm USB modem converter now attached to ttyUSB2  
qmi\_wwan 1-1.1:1.8: cdc-wdm0: USB WDM device  
qmi\_wwan 1-1.1:1.8 wwan0: register ‘qmi\_wwan’ at usb-ci\_hdrc.1-1.1, WWAN/QMI dev  
ice, ee:0a:1e:50:28:98  
usb 1-1.1: USB disconnect, device number 113  
qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0  
qcserial 1-1.1:1.0: device disconnected  
qcserial ttyUSB1: Qualcomm USB modem converter now disconnected from ttyUSB1  
qcserial 1-1.1:1.2: device disconnected  
qcserial ttyUSB2: Qualcomm USB modem converter now disconnected from ttyUSB2  
qcserial 1-1.1:1.3: device disconnected  
qmi\_wwan 1-1.1:1.8 wwan0: unregister ‘qmi\_wwan’ usb-ci\_hdrc.1-1.1, WWAN/QMI devi  
ce

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [September 27, 2023, 8:13am UTC](https://forum.sierrawireless.com/t/rc7620-1-not-available-after-update-with-qmi-update-firmware/30723/2 "2023-09-27T08:13:58Z")

</div>

have you tried to trigger the TP1 (pin 47) to download mode and download some FW again?

 ![image](https://us1.discourse-cdn.com/flex025/uploads/sierrawireless/original/2X/1/19941947852c3f765e0f38c6a7b9bee76a7b0e24.png)

```auto
For example: 
jordan@jordan-X240:~/QMI/MBPL/MBPL_SDK_R28_ENG5-fwdwl.bin/SampleApps/lite-fw-download$ sudo ./bin/fwdwl-litehostx86_64 -c QMI -m 4 -d /dev/ttyUSB0 -f /home/jordan/Downloads/FW_EM74x1/SWI9X50C_01.14.03.00_GENERIC_002.036_010/

```

---

<div class="post-metadata">

**Author:** ![JFTWIT](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@JFTWIT](https://forum.sierrawireless.com/u/JFTWIT)\
**Post date:** [September 27, 2023, 9:24am UTC](https://forum.sierrawireless.com/t/rc7620-1-not-available-after-update-with-qmi-update-firmware/30723/3 "2023-09-27T09:24:40Z")

</div>

Thank you for your reply.  
I will check with the hardware people to order this pin and use “fwdwl-litearm” in your order as my target is ARM 32 Bits.  
But in your order I don’t see the name of the update file. It is the file “RC76xx\_Release9.6.1\_GENERIC\_7620.spk”.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [September 27, 2023, 9:39am UTC](https://forum.sierrawireless.com/t/rc7620-1-not-available-after-update-with-qmi-update-firmware/30723/4 "2023-09-27T09:39:53Z")

</div>

My example is just for EM module  
You can change the filename

---

<div class="post-metadata">

**Author:** ![JFTWIT](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@JFTWIT](https://forum.sierrawireless.com/u/JFTWIT)\
**Post date:** [September 27, 2023, 3:24pm UTC](https://forum.sierrawireless.com/t/rc7620-1-not-available-after-update-with-qmi-update-firmware/30723/5 "2023-09-27T15:24:48Z")

</div>

Here’s the result of the recommended manipulation: 😒

 ![image](https://us1.discourse-cdn.com/flex025/uploads/sierrawireless/original/2X/8/8c10a65dbec9db90d97a7ddc6bc5724ed5c24fad.png)

What does this error mean?  
How can I correct it?  
Thank you for your help.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [September 27, 2023, 3:29pm UTC](https://forum.sierrawireless.com/t/rc7620-1-not-available-after-update-with-qmi-update-firmware/30723/6 "2023-09-27T15:29:02Z")

</div>

does same procedure work in anther OK module?  
This is to ensure the recovery method is OK for all module triggering TP1 boot pin.

---

<div class="post-metadata">

**Author:** ![JFTWIT](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@JFTWIT](https://forum.sierrawireless.com/u/JFTWIT)\
**Post date:** [September 27, 2023, 3:53pm UTC](https://forum.sierrawireless.com/t/rc7620-1-not-available-after-update-with-qmi-update-firmware/30723/7 "2023-09-27T15:53:12Z")

</div>

I think I’ve figured out the problem thanks to the fwdwl.log file:  
the qmi\_wwan, qcserial and usb\_wwan drivers are built into the Linux kernel, whereas you need to use modules.  
I’m going to change that.
