it is written in your Linux QMI SDK documentation :
** NOTE: This product is now EOL. Sierra Wireless recommends customers move to MBPL on supported modules.
the RC7620 modem is a very recent product. I don’t understand. 
don’t you have another solution for me ?
we have been delivered 150 RC7620 modems with non-working Beta firmware. 
For the update with AVMS website, it is too complicated to have to fill in 150 IMEI - Serial number - connected to the network…
As you tested that MBPL seems cannot work with RC module…
So using the old SDK should be the only way. (other than AVMS)
The old SDK is not the solution as I need to blacklist the qmi_wwam driver used by the modem in operation.
I don’t think it’s up to me to say whether MBPL doesn’t work with the RC7620.
It would be up to you to confirm this.
it seems to work except that the .spk file is the wrong format ! why ?
There is no image to be downloaded. Exit applications!Exiting Application!!!
file log:
[225][1]-f
[225][1]RC76xx_Release8_SIERRA_R2C_7620.spk
225][7]User specified read block size: 0 bytes
[225][7]**************************************************
[225][7]Copyright: © 2015-2017 Sierra Wireless, Inc. all rights reserved
[225][7]lite-fw is only permitted to be use with Sierra Wireless Modems
225][7]lite-fw version lite-fwMBPL_SDK_R20_ENG4
[225][7]**************************************************
[225][6]Images list empty, no image to download.
I believe you can use gobinet
Do you have a document that simply describes the procedure to follow ?
Can you try the MBPL R20 again?
owner@ubuntu:~/QMI/MBPL_SDK_R20_ENG4-lite.src/SampleApps/lite-fw-download$ sudo ./bin/fwdwl-litehostx86_64 -m 4 -d /dev/ttyUSB0 -p /dev/cdc-wdm0 -t 1 -f /home/owner/Desktop/RC7620_FW/
Application version: 1.0.2105.3
INFO: QDL Port : /dev/ttyUSB0
INFO: Device Path: /dev/cdc-wdm0
INFO: FW Path : /home/owner/Desktop/RC7620_FW/
Target image Info:
Carrier :GENERIC
FW Version :00.08.07.00
Model ID :SWI9X07H
Package ID :000
PRI Version:001.081
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: /home/owner/Desktop/RC7620_FW//RC76xx_Release8_GENERIC_GCF_7620.spk
/
We move on. Thank you for your help.
After “AT!BOOTHOLD” command, /dev/cdc-wdm0 and /dev/ttyUSBx (x=1,2,3) disappears and do not reappear.
Here is the result of the test: how to ensure that the QMI device path is correct ?
AT!BOOTHOLD
OK
FATAL: term closed
# ./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
Modem is disconnected or not in correct state. Please ensure QMI device path is
correct.
Exiting Application!!!
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.