How to update the RC7620 firmware with "qmi-update-firmware"

Can you check dmesg?

After at!boothold, you should see qcserial driver enumerate one usb port such as /dev/ttyUSB0

here is the information added in dmesg after the AT!BOOTHOLD command
ttyUSB0 is not visible in the folder /dev. why ?

usb 1-1.1: USB disconnect, device number 3
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 device
usbcore: deregistering interface driver qmi_wwan
usb 1-1.1: new high-speed USB device number 4 using ci_hdrc
usb 1-1.1: New USB device found, idVendor=1199, idProduct=68c0
usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.1: Product: Sierra Wireless RC7620-1
usb 1-1.1: Manufacturer: Sierra Wireless, Incorporated
usb 1-1.1: SerialNumber: 7T0265850513B011
qcserial 1-1.1:1.0: Qualcomm USB modem converter detected
usb 1-1.1: Qualcomm USB modem converter now attached to ttyUSB0
usbcore: registered new interface driver qmi_wwan
random: crng init done

Didn’t here show ttyusb0 is created?

qcserial 1-1.1:1.0: Qualcomm USB modem converter detected
usb 1-1.1: Qualcomm USB modem converter now attached to ttyUSB0

Btw, do you need to use sudo to run the program?

Yes, but where ?
in the folder “/dev” nothing.

Not use sudo.
everything is managed at “root” level.

How did you enter at!boothold then?
You should use /dev/ttyUSB2, right?

Yes, I use /dev/ttyUSB2 to enter AT!BOOTHOLD.
When the modem start up, ttyUSB0,ttyUSB1 and ttyUSB2 are available.
But, after AT!BOOTHOLD nothing more

Strange, dmesg shows it is created …

How about directly running the app without sending at!boothold?

Ok, Here is the result

# ./fwdwl-litearm -m 4 -d /dev/ttyUSB0 -p /dev/cdc-wdm0 -t 1 -f

/usr/wit/applic/update/
Application version: 1.0.2105.3
modinfo: module ‘/lib/modules/4.14.231-1.1.0/cdc_mbim’ not found
INFO: QDL Port : /dev/ttyUSB0
INFO: Device Path: /dev/cdc-wdm0
INFO: FW Path : /usr/wit/applic/update/
Target image Info:
Carrier :SIERRA
FW Version :00.08.07.00
Model ID :SWI9X07H
Package ID :000
PRI Version:000.057
SKU :9999999
sh: udevadm: not found
Exiting Application!!!

I don’t use udev on my embedded target.
I use mdev

Can you install it???

it is very complicated.
I have to get the sources, compile them for my target and do the installation manually.
I think the problem comes from a bad usb enumeration when the modem goes into BOOTHOLD mode.
I’ll look into this.

I think, I understand the problem.
I have an asynchronism with “mdev” and the /dev/ttyUSB0 is destroyed just after being initialized.

The last test.
INFO: QDL Port : /dev/ttyUSB0
INFO: Device Path: /dev/cdc-wdm0
INFO: FW Path : /usr/wit/applic/update/
Target image Info:
Carrier :SIERRA
FW Version :00.08.07.00
Model ID :SWI9X07H
Package ID :000
PRI Version:000.057
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: /usr/wit/applic/update//RC76xx_Release8_SIERRA_R2C_7620.spk
/
FW download succeeded.
Waiting for modem to come up in ONLINE mode …
Modem is now in ONLINE mode …

Many thanks for your important help.
sorry if my English is not perfect. it is not my native language.
Now I just have to automate it.

so do you use the following?

  1. AT!BOOTHOLD
  2. ./fwdwl-litearm -m 4 -d /dev/ttyUSB0 -p /dev/cdc-wdm0 -t 1 -f /usr/wit/applic/update/

Yes, this is exactly the commands used

Hello jyijyi,

I can’t find the information to know when the “fwdwl-litearm” operation is successfully completed.
it’s for the automatic update

Do you have an idea?

I have attached the log of the update.
fwdwl.zip (2.1 KB)

Thank you for your help
See you soon
JFT

from your previous log, I can see the following:

*FW download succeeded.*
*Waiting for modem to come up in ONLINE mode …*
*Modem is now in ONLINE mode …*

Hello jyijyi,

these messages are not systematic.
In the log file attached to the exchange previously, (fwdwl.zip) these messages are not present and the update is still correct.

Is there any other information provided by “fwdwl-litearm” that can be used automatically ?

Thank you for your help
See you soon
JFT

you can check the source code in the MBPL
\MBPL_SDK_R20_ENG4-lite.bin\SampleApps\lite-fw-download\src