WP7607 lite-fw-download failed

IoT Modules WP Series
1

I am using fw-download from the lite-sdk to update the firmware, the command is as follows:

./fwdwl-litearm64linaro -t 1 -f /home/root -l log.txt

The printing information during the update is as follows:

Application version: 1.0.2303.0
INFO: QDL Port:
INFO: Device Path: /dev/cdc-wdm0
INFO: FW Path: Images
Target image Info:
Carrier    :SIERRA
FW Version :02.37.06.05
Model ID   :SWI9X07Y
Package ID :000
PRI Version:001.072
SKU        :9999999
Switching device into download mode ...
Modem Needs FW
Modem Needs PRI
Waiting for modem to disconnect from the host ...
[ 1601.582824] usb 2-1: USB disconnect, device number 2
[ 1601.588524] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 1601.596764] option 2-1:1.0: device disconnected
[ 1601.601925] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 1601.610094] option 2-1:1.2: device disconnected
[ 1601.616908] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[ 1601.625075] option 2-1:1.3: device disconnected
[ 1601.629880] qmi_wwan 2-1:1.8 wwan0: unregister 'qmi_wwan' usb-ci_hdrc.1-1, WWAN/QMI device
Modem disconnected from host.
[ 1601.672312] cdc_ether 2-1:1.19 usb0: unregister 'cdc_ether' usb-ci_hdrc.1-1, CDC Ethernet Device
Waiting for modem to come up in BOOT and HOLD mode ...
[ 1614.186053] usb 2-1: new high-speed USB device number 3 using ci_hdrc
[ 1614.348401] option 2-1:1.0: GSM modem (1-port) converter detected
[ 1614.354922] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
QDL port found: /dev/ttyUSB0
BOOT and HOLD Mode. Downloading firmware ...
Downloading: Images/WP76xx_Release16.3_SIERRA.spk
FW download failed: eSDP_FWDWL_ERR_FIREHOSE_STATE_ERR(120)

The content of the log is as follows:

[07:34:09.401][7]Received ACK/RAWMODE_TRUE for Program command.  Advance to payload transfer stage.
[07:34:09.401][7]Current mode: 7, previous max_reads_allowed: 29
[07:34:09.401][7]Write: Images/WP76xx_Release16.3_SIERRA.spk

[07:34:09.401][7]Actual read block size used: 0 bytes
[07:34:09.401][7]Write Start
[07:34:37.520][7]Total bytes sent: 69671245 bytes
[07:34:37.537][7]Firmware Write Completed, max_reads_allowed reset to 300
[07:34:38.038][7]read timeout
[07:34:38.038][7]Current mode: 7, previous max_reads_allowed: 299
[07:34:38.038][7]prev_mode (7) same as current mode, skip processing.
[07:34:38.539][7]read timeout
2

In addition, after the error occurred, I tried to power cycle the module, but since then, the module has been unable to connect to the internet.
The ModemManager log is as follows:

Jun 28 07:53:32 enpalplayground ModemManager[1020]: [modem0] simple connect started...
Jun 28 07:53:32 enpalplayground ModemManager[1020]: [modem0] simple connect state (4/8): wait to get fully enabled
Jun 28 07:53:33 enpalplayground ModemManager[1020]: [modem0] couldn't enable interface: 'Invalid transition'
Jun 28 07:53:33 enpalplayground ModemManager[1020]: [modem0] state changed (enabling -> disabled)
Jun 28 07:53:33 enpalplayground ModemManager[1020]: [modem0] simple connect started...
Jun 28 07:53:33 enpalplayground ModemManager[1020]: [modem0] simple connect state (3/8): enable
Jun 28 07:53:33 enpalplayground ModemManager[1020]: [modem0] state changed (disabled -> enabling)
Jun 28 07:53:33 enpalplayground ModemManager[1020]: [modem0] simple connect started...
Jun 28 07:53:33 enpalplayground ModemManager[1020]: [modem0] simple connect state (4/8): wait to get fully enabled
Jun 28 07:53:33 enpalplayground ModemManager[1020]: [modem0] couldn't enable interface: 'Invalid transition'
3

how about adding “-m 4”?

how about using swiflash?
https://source.sierrawireless.com/resources/airprime/software/swiflash/#sthash.F6ugVWGl.dpbs

One more thing is that i don’t see you install the MBPL USB driver.

4

Thanks for your reply.I have resolved the problem.
The reason why it failed to upgrade the module was that i was using a newer version of the firmware.
Atually,something had changed in that version,such as the partition.

5

I don’t quite think there is partition change in R16.3…
Which FW are you using now?

6

The following content is the log for the AT!impref? command:

 preferred fw version:    02.18.05.00
 preferred carrier name:  SIERRA
 preferred config name:   SIERRA_001.002_000
 current fw version:      02.18.05.00
 current carrier name:    SIERRA
 current config name:     SIERRA_001.002_000
7

that is quite an old firmware in R10, probably it does not even contain the new memory support…
https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-release-10,-d-,1,-d-,1,-d-,1/#sthash.M5vzD1mQ.pDVcvtqH.dpbs

8

yep,I tried to upgrade the module using R16.3 firmware,but i didn’t know that is was not supported from the old firmware.
luckly,i tried using R10 firmware to update it,and it succeeded.
If I want to upgrade it successfully, do I need to update it one by one with adjacent versions?

9

As i know, R16.3 should support the old firmware

I don’t know why your upgrade has problem, but of course you can try if R13and R16 are OK to your module