Swiflash PORT not found

21

The -c QMI seemed to work but it only did one not sure if it can do multiple modules ?

sudo ./fwdwl-litehostx86_64 -c QMI -m 4 -f ~/GHS_Qt/ -s ‘GHS_Full_firmware_001.spk’ -t 1 -d /dev/ttyUSB0 -d /dev/ttyUSB3
[sudo] password for mango:
Application version: 1.0.2303.0
INFO: QDL Port: /dev/ttyUSB3
INFO: Device Path:
INFO: FW Path: /home/mango/GHS_Qt/
Target image Info:
Carrier :ATT
FW Version :02.36.06.00
Model ID :SWI9X06Y
Package ID :005
PRI Version:001.067
SKU :9999999
Modem is already 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/mango/GHS_Qt//GHS_Full_firmware_001.spk
All image data was downloaded successfully.
Device is about to reset …
Waiting for modem to come up in ONLINE mode …
^C

And it had to be killed just sitting there and the module was up and running again?

22

how about opening another terminal for another download for another module?

I can do this with swiflash on two modules at the same time

23

I just tried the multi module

swiflash -m “wp77xx” -i /home/mango/GHS_Qt/GHS_Full_firmware_001.spk -p /dev/serial/by-id/usb-Sierra_Wireless__Incorporated_Sierra_Wireless_WP7702_AT32365056151007-if00-port0 -p /dev/serial/by-id/usb-Sierra_Wireless__Incorporated_Sierra_Wireless_WP7702_AT32365056071007-if00-port0
Detecting USB of the target
No device connected

and two seperate terminals with one device each but same result.

Detecting USB of the target
No device connected

24

no idea then, i don’t see problem here with separate terminals with swiflash
you might try another terminal for fwdwl application

25

I tried this from within a C program and it seem to be doing both of them in parallel,
but “Waiting for modem to come up in ONLINE mode …” never returns even though both are up and running?
Well it timed out 240 second!!!

system(“echo … | sudo -S /home/mango/MBPL/MBPL_SDK_R32_ENG2-fwdwl.bin/SampleApps/lite-fw-download/bin/fwdwl-litehostx86_64 -c QMI -m 4 -f ~/GHS_Qt/ -s ‘GHS_Full_firmware_001.spk’ -t 1 -d /dev/ttyUSB0 &”);
system(“echo … | sudo -S /home/mango/MBPL/MBPL_SDK_R32_ENG2-fwdwl.bin/SampleApps/lite-fw-download/bin/fwdwl-litehostx86_64 -c QMI -m 4 -f ~/GHS_Qt/ -s ‘GHS_Full_firmware_001.spk’ -t 1 -d /dev/ttyUSB1 &”);

[sudo] password for mango: Application version: 1.0.2303.0
Application version: 1.0.2303.0
Target image Info:
Carrier :ATT
FW Version :02.36.06.00
Model ID :SWI9X06Y
Package ID :005
PRI Version:001.067
SKU :9999999
Target image Info:
Carrier :ATT
FW Version :02.36.06.00
Model ID :SWI9X06Y
Package ID :005
PRI Version:001.067
SKU :9999999
Downloading: /home/mango/GHS_Qt//GHS_Full_firmware_001.spk
Downloading: /home/mango/GHS_Qt//GHS_Full_firmware_001.spk
All image data was downloaded successfully.
All image data was downloaded successfully.
Device is about to reset …
Waiting for modem to come up in ONLINE mode …
Device is about to reset …
Waiting for modem to come up in ONLINE mode …

Failed to detect modem ONLINE mode in 240 seconds. Application terminates.
INFO: QDL Port: /dev/ttyUSB1
INFO: Device Path:
INFO: FW Path: /home/mango/GHS_Qt/
Modem is already in QDL mode. Continuing FW download.
Waiting for modem to come up in BOOT and HOLD mode …
BOOT and HOLD Mode. Downloading firmware …
Failed to detect modem ONLINE mode in 240 seconds. Application terminates.
INFO: QDL Port: /dev/ttyUSB0
INFO: Device Path:
INFO: FW Path: /home/mango/GHS_Qt/
Modem is already in QDL mode. Continuing FW download.
Waiting for modem to come up in BOOT and HOLD mode …
BOOT and HOLD Mode. Downloading firmware …

26

have you just tried one module connected and see if there is any “Waiting for modem to come up in ONLINE mode …”?
does the firmware change inside the module after this operation?

You really need to do some debug or investigation on this (e.g. step-by-step testing instead of doing two modules at the same time to make sure your environment and parameter are good)

27

It does the same thing,

I found why it takes 240 seconds

-R --retry
(Command is optional, should only be used for troubleshooting)
Specifies number of device connection retries after a FW download is completed.
The retry interval is 5 seconds.
The default number of retries is 48.
Example: -R 3 (3 retries)

What is it waiting for?

I am pretty sure it is updating the firmware but i will make a test, is there a way to see it on the device like an last update time? I have been using the same image

28

Are you using a single command with multiple -p options ?

29

if you confirm the FW is updated, probably you can ignore the message “Waiting for modem to come up in ONLINE mode …”. I think this message is just to check if the module is back to normal mode instead of download mode.

Are you using a single command with multiple -p options ?

do you mean swiflash with multiple -p option?
seems it does not work…

30

Yes i meant swiflash with multiple -p, good you verified it was not working.
I tried the -R option for fwdwl but that does not change the timeout?
I might kill the app and check when the devices attach