I am using the latest Sierra SDK Sierra_04.00.02, and I am trying to update the firmware on EM7455 from 2.08.02 to 2.20.03, everything seems to go well (I get the success as result) but when I check the firmware in the modem, it is still the old 2.08.02.
I am running on iMX6 ARM platform, all related binaries seems to be working ok.
root@mserver115:/tmp# ls -la SWI*
-rw-r–r-- 1 root root 64381598 Oct 26 19:55 SWI9X30C_02.20.03.00.cwe
-rw-r–r-- 1 root root 3062 Oct 26 19:55 SWI9X30C_02.20.03.00_Generic_002.017_000.nvu
root@mserver115:/tmp# echo raw,‘AT!BOOTHOLD’ | nc localhost 8080
AT!BOOTHOLD
OK
root@mserver115:/tmp# ./slqssdk &
[1] 611
root@mserver115:/tmp# ./fwdldarm -s /tmp/ -d 9x30 -p /tmp/ -k
Detecting USB of the target
DONE
Communicating with the target
DONE
Downloading the firmware
.DONE
Rebooting the module
…DONE
Firmware Download SUCCESS
[1]+ Killed ./slqssdk
root@mserver115:/tmp# echo raw,‘ATI’ | nc localhost 8080
ATI
Manufacturer: Sierra Wireless, Incorporated
Model: EM7455
Revision: SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53
MEID: 35432407003201
IMEI: 354324070032012
IMEI SV: 4
FSN: LF548120770310
+GCAP: +CGSM
OK
root@mserver115:/tmp#
When I check the update status in the modem, it will also indicate that all is well.
Is there any reason you issue the boothold command? This should not be nesessary. Are there any other files (particularily CWE or NVU files) in the /tmp folder?
No, but I had problem for fwdldarm to find the device, and it did work after I did put it in BOOT HOLD, but maybe I was just lucky. I can try without it.
Yes, the files are in the same directory, everything happens in /tmp and all files are there as well.
Maybe ‘AT!IMAGE?’ and/or ‘AT!IMPREF?’ will explain the problem? I believe the normal EM/MC74xx firmware update procedure is to change IMPREF and then upload new PRI and MODEM images as required. That works for me at least.
Looks like that firmware was not flashed after downloading. I had EM7455 on Windows 10 Pro 64 bit environment and just recent updating with latest same firmware release where with a successful result. I believe “boot and hold” mode shall be taken care by that script itself.
Without the BOOTHOLD the fwdldarm cannot find the device. But it seems that now the update is failing on error.
root@mserver115:/tmp# ./fwdldarm -s ./slqssdk -d 9x30 -p /tmp/
Detecting USB of the target
No device connected
root@mserver115:/tmp# ./fwdldarm -s ./slqssdk -d 9x30 -p /tmp/
Detecting USB of the target
No device connected
root@mserver115:/tmp# ./fwdldarm -s ./slqssdk -d 9x30 -p /tmp/
Detecting USB of the target
No device connected
root@mserver115:/tmp# ./fwdldarm -s ./slqssdk -d 9x30 -p /tmp/
Detecting USB of the target
No device connected
root@mserver115:/tmp# echo raw,‘AT!BOOTHOLD’ | nc localhost 8080
AT!BOOTHOLD
OK
root@mserver115:/tmp# ./fwdldarm -s ./slqssdk -d 9x30 -p /tmp/
Detecting USB of the target
DONE
Communicating with the target
DONE
Downloading the firmware
…ERROR: Firmware Download failed. Callback status 59399DONE
ERROR: Firmware Download Failed
root@mserver115:/tmp#
And I guess it did not come that far, as I don’t see any signs here;
root@mserver115:/tmp# echo raw,‘AT!BCFWUPDATESTATUS’ | nc localhost 8080
AT!BCFWUPDATESTATUS
!BCFWUPDATESTATUS: SUCCESS
TYPE=SPKG,STATUS=PASS
OK
root@mserver115:/tmp# echo raw,‘at!image?’ | nc localhost 8080
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 1 0 0 ?? 02.08.02.00?
FW 2 EMPTY 0 0 0
FW 3 EMPTY 0 0 0
FW 4 EMPTY 0 0 0
Max FW images: 4
Active FW image is at slot 1
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 002.017_000 02.20.03.00_GENERIC
Max PRI images: 50
OK
root@mserver115:/tmp# echo raw,‘at!impref?’ | nc localhost 8080
at!impref?
!IMPREF:
preferred fw version: 02.08.02.00
preferred carrier name: GENERIC
preferred config name: GENERIC_002.007_000
current fw version: 02.08.02.00
current carrier name: GENERIC
current config name: GENERIC_002.007_000
OK
root@mserver115:/tmp#
I have the same trouble, and I have been resolved it not long ago.
I found a suggestion, and I tried to remove modemanager.
Finally the firmware upgrade was finished with QMI SDK.
Thank you for the reply, but I don’t have modem manager installed at all. I do have libqmi, but there is no active process running that would be related to the device.
However, after the first failure something must be wrong now, because now it fails with a callback status code.
./fwdldarm -s ./slqssdk -d 9x30 -p /tmp/
Detecting USB of the target
DONE
Communicating with the target
DONE
Downloading the firmware
…ERROR: Firmware Download failed. Callback status 59399DONE
ERROR: Firmware Download Failed