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?
- AT!BOOTHOLD
- ./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
Hello jyijyi
In my case I am getting download error 100
fwdwl-lite -m 4 -t 1 -f /fw/ -c QMI -d /dev/ttyUSB0 -p /dev/cdc-wdm0
please find attached log fileProcessing: fwdwl.log…
Processing: fwdwl_log…
fwdwl_log.txt (31.1 KB)
I am trying to upgrade the firmware of RC7620 module, and it exits with error 100.
Where as when same process is followed with EM7421 module, it works smoothly and firmware is upgraded.
Any particular reason behind this?
where are all the error codes listed?
Did you enter at!boothold ?
Have you tried swiflash?
https://source.sierrawireless.com/resources/airprime/software/swiflash/