Firmware not downloading on EM9293

IoT Modules
1

Need some help downloading firmware for my EM9293. I’ve tried power cycling the device and also running AT!BOOTHOLD but that didn’t make the firmware download successful.

sudo ./bin/fw-download-toolrpi -f \~/Downloads/SWIX65C_02.17.08.00_ROGERS_030.033_001 -w SWIX65C_02.17.08.00.cwe -n SWIX65C_02.17.08.00_ROGERS_030.033_001.nvu -d /dev/ttyUSB1 -F -c MBIM
Application version: 1.0.2412.2
INFO: QDL Port: /dev/ttyUSB1
INFO: Device Path:
INFO: Device Port: 0-0
INFO: FW Path: ~/Downloads/SWIX65C_02.17.08.00_ROGERS_030.033_001
Target image Info:
Carrier    :ROGERS
FW Version :02.17.08.00
Model ID   :SWIX65C
Package ID :001
PRI Version:030.033
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 …
FW download failed: eSDP_FWDWL_ERR_SAHARA_UNRESPONSIVE(122)
Device not responsive in download mode.  Please power cycle device.
2

I have some experience with this. I do not recognize from memory the fw download tool version. I will check but I have some questions for you,

what version of MBPL drivers are installed?

3

It should be the latest drivers since I downloaded them from the website a few days ago.

4

Have you tried to download the firmware in normal way?
you should not download firmware in boot and hold mode.

5

Yes, I’ve tried it the normal way.

6

then is it working fine in normal way?

7

Nope, I get stuck in BOOT and HOLD Mode. Downloading firmware... and then it says:

FW download failed: eSDP_FWDWL_ERR_SAHARA_UNRESPONSIVE(122) Device not responsive in download mode. Please power cycle device.

8

then you can take a OK module and type AT!BOOTHOLD and see if you can bring the module back to normal mode.
If yes, then that means your command line is correct but just your current module is faulty.

9

I ran AT!BOOTHOLD and the USB connection got disabled, so I replugged into my raspPi. Checked the status using AT!GSTATUS and it’s still in LOW POWER MODE.

10

there is no relationship between AT!BOOTHOLD and low power mode.
If you wanna see why it is kept in low power mode, you need to check AT!PCINFO?

11

Indeed, I have a FW mismatch which is what is keeping at Low Power Mode. Any steps to download my firmware properly?

AT!PCINFO?
State: Low Power Mode
LPM voters - Temp:0, Volt:0, User:0, W_DISABLE:0, IMSWITCH:1, BIOS:0, LWM2M:0, OMADM:0, FOTA0
LPM persistence - None

at!impref?
!IMPREF: 
 preferred fw version:    02.17.08.00
 preferred carrier name:  ROGERS
 preferred config name:   ROGERS_030.033_001
 preferred subpri index:  000
 current fw version:      02.15.01.00
 current carrier name:    GENERIC
 current config name:     GENERIC_030.054_001
 current subpri index:    000

 fw version mismatch
 carrier name mismatch
 config name mismatch
12

how did you download the firmware in normal mode?

13

The “GENERIC” firmware was already loaded in before. But for the ROGERS firmware, I used the fw-download tool while in normal mode but it got stuck as I’ve shown and automatically switched to LOW POWER MODE.

So, I guess it was unable to download it properly and hence, the fw mismatch.

14

do you mean you can download GENERIC firmware but not for Rogers firmware for normal mode?
Then how about firmware like AT&T or TMO or Verizon?

15

Well, I’ve also tried the newer GENERIC firmware downloads from the website and still ran into the same issue. So I don’t think it’s the carrier.

16

then probably you did not download any firmware successfully…

17

Yes, I think so too. Is there any way to fix this FW mismatch? I just want to go back to ONLINE mode at least. I’ve tried deleting the current FW images but still no luck.

18

@blackbow7 did you have an idea of any solution to the FW mismatch, or just how to download FW successfully in general?

19

i don’t see problem to download firmware:

20

You can fix the IMPREF mismatch with this AT command, AT!IMPREF=”GENERIC”

Then power off and on the module.

That should bring the module back to normal.