I’m a few weeks into using this modem and just upgraded the firmware to the latest generic SWIX55C_03.09.11.00/030.044_000
The SIM is connecting but some checks show missing values, and nothing in PRI image slots:
AT!ENTERCND="A710"
OK
AT!PRIID?
PRI Part Number: Unknown
Revision: Unknown
Customer: Unknown
Carrier PRI: None
OK
AT!IMPREF?
!IMPREF:
preferred image setting does not exist
current fw version: 03.09.11.00
current carrier name:
current config name:
current subpri index: 000
fw version mismatch
carrier name mismatch
config name mismatch
OK
AT!IMAGE?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 127 0 0 ?_? 03.04.03.00_?
FW 2 GOOD 127 0 0 ?_? 03.09.11.00_?
FW 3 EMPTY 0 0 0
Max FW images: 3
Active FW image is at slot 255
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
Max PRI images: 50
OK
AT!SKU?
!SKU: Unset
OK
Not exactly sure what went wrong or how to populate that info.
If I try set the image like AT!IMAGE="GENERIC" it also fails, not surprisingly.
The older firmware version had the same issues…
Also if you want to use the teraterm script (its just a text file) to get the status of the unit (use the script or send the commands manually). EM91 status.ttl (1.5 KB)
Was able to complete the linux steps using the examples you provided -
fw + pri IMAGEs, IMPREF populated (no -w or -n switches previously, or have USB drivers installed while issuing fwdwl cmd)
PRIID still reported unknown w/ SIM connected, set manually (can I just set the values using filename as in the output?)
SKU Still missing…
But it seems like all the FW upgrades were successful this time:
Welcome to minicom 2.8
OPTIONS: I18n
Port /dev/ttyUSB0, 20:23:39
Press CTRL-A Z for help on special keys
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: EM9191
Revision: SWIX55C_03.09.11.00 7bf975 jenkins 2022/06/10 20:36:01
IMEI: 355866235646598
IMEI SV: 22
FSN: 8W1157036304A1
+GCAP: +CGSM
OK
at!entercnd="A710"
OK
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 127 0 0 ?_? 03.04.03.00_?
FW 2 EMPTY 0 0 0
FW 3 EMPTY 0 0 0
Max FW images: 3
Active FW image is at slot 255
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
Max PRI images: 50
OK
# exit minicom
$ sudo ./fwdwl-litehostx86_64 -p /dev/cdc-wdm2 -t 1 -f ./em9/SWIX55C_03.09.06.00-001_TMO_030.035_000 -w SWIX55C_03.09.06.00-001.cwe -n SWIX55C_03.09.06.00-001_TMO_030.035_000.nvu
Application version: 1.0.2204.2
INFO: QDL Port :
INFO: Device Path: /dev/cdc-wdm2
INFO: FW Path : ./em9/SWIX55C_03.09.06.00-001_TMO_030.035_000
Target image Info:
Carrier :TMO
FW Version :03.09.06.00
Model ID :SWIX55C
Package ID :000
PRI Version:030.035
SKU :9999999
Switching device into download mode ...
Modem Needs FW
Modem Needs PRI
Waiting for modem to disconnect from the host ...
Modem disconnected from host.
Waiting for modem to come up in BOOT and HOLD mode ...
QDL port found: /dev/ttyUSB0
BOOT and HOLD Mode. Downloading firmware ...
Downloading: ./em9/SWIX55C_03.09.06.00-001_TMO_030.035_000/SWIX55C_03.09.06.00-001.cwe
Downloading: ./em9/SWIX55C_03.09.06.00-001_TMO_030.035_000/SWIX55C_03.09.06.00-001_TMO_030.035_000.nvu
FW download succeeded.
Waiting for modem to come up in ONLINE mode ...
Modem is now in ONLINE mode ...
FW update status: Successful
FW info from modem:
Model ID : EM9191
FW Version : SWIX55C_03.09.06.00
Carrier Name : TMO
Carrier PRI Revision: 030.035_000
Firmware Download Process completed
Exiting Application!!!
$ sudo ./fwdwl-litehostx86_64 -p /dev/cdc-wdm2 -t 1 -f ./em9/SWIX55C_03.09.11.00-001_GENERIC_030.044_000 -w SWIX55C_03.09.11.00-001.cwe -n SWIX55C_03.09.11.00-001_GENERIC_030.044_000.nvu
Application version: 1.0.2204.2
INFO: QDL Port :
INFO: Device Path: /dev/cdc-wdm2
INFO: FW Path : ./em9/SWIX55C_03.09.11.00-001_GENERIC_030.044_000
Target image Info:
Carrier :GENERIC
FW Version :03.09.11.00
Model ID :SWIX55C
Package ID :000
PRI Version:030.044
SKU :9999999
Switching device into download mode ...
Modem Needs FW
Modem Needs PRI
Waiting for modem to disconnect from the host ...
Modem disconnected from host.
Waiting for modem to come up in BOOT and HOLD mode ...
QDL port found: /dev/ttyUSB0
BOOT and HOLD Mode. Downloading firmware ...
Downloading: ./em9/SWIX55C_03.09.11.00-001_GENERIC_030.044_000/SWIX55C_03.09.11.00-001.cwe
Downloading: ./em9/SWIX55C_03.09.11.00-001_GENERIC_030.044_000/SWIX55C_03.09.11.00-001_GENERIC_030.044_000.nvu
FW download succeeded.
Waiting for modem to come up in ONLINE mode ...
Modem is now in ONLINE mode ...
FW update status: Successful
FW info from modem:
Model ID : EM9191
FW Version : SWIX55C_03.09.11.00
Carrier Name : GENERIC
Carrier PRI Revision: 030.044_000
Firmware Download Process completed
Exiting Application!!!
Welcome to minicom 2.8
OPTIONS: I18n
Port /dev/ttyUSB0, 20:35:09
Press CTRL-A Z for help on special keys
at!entercnd="A710"
OK
at!impref?
!IMPREF:
preferred fw version: 03.09.11.00
preferred carrier name: GENERIC
preferred config name: GENERIC_030.044_000
preferred subpri index: 000
current fw version: 03.09.11.00
current carrier name: GENERIC
current config name: GENERIC_030.044_000
current subpri index: 000
OK
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 127 0 0 ?_? 03.04.03.00_?
FW 2 GOOD 128 0 0 ?_? 03.09.06.00_?
FW 3 GOOD 129 0 0 ?_? 03.09.11.00_?
Max FW images: 3
Active FW image is at slot 3
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 030.044_000 03.09.11.00_GENERIC
PRI FF GOOD 0 0 0 030.035_000 03.09.06.00_TMO
Max PRI images: 50
OK
# installed em9191 back in router
# ROOter at-cmd terminal:
at!entercnd="A710"
OK
at!priid?
PRI Part Number: Unknown
Revision: Unknown
Customer: Unknown
Carrier PRI: 9999999_9909621_SWIX55C_03.09.11.00_01_GENERIC_030.044_000
Carrier PRI: 9999999_9910308_SWIX55C_03.09.06.00_01_TMO_030.035_000
OK
at!priid="9909621","030.044","GENERIC"
OK
at!sku?
!SKU: Unset
OK
I will add here for other bone heads like me.
Make sure you stop the ModemManager process on your Linux computer. I ran an update on one modem. Walked away. Came back. Had to reboot the computer for an unrelated reason. Went back to updating a modem and kept getting FIREHOSE errors. Spent WAY longer than needed to figure out it was the ModemManager process jacking it up.
Do you happen to know the EXACT proper syntax for the fdt2.exe tool on Windows10 to add an updated fw image and the associated PRI images, WITHOUT overwriting the last fw image in slot 1 and subsequently orphaning the PRI associated with that last fw image?
I keep running the fdt2.exe tool and successfully flashing firmware images to the EM9191, but they keep writing themselves in the fw slot # 1, instead of in slots 2 or 3. I can’t figure out why. Works fine when I do as you posted an example of in Linux using fwdwl-lite. Not when using fdt2.exe in Windows10. I really need the Win10 way to work properly.
Here is an example of the commands I run, again in Windows 10 “command line” ran inside the folder with the images:
Before anyone says anything: I use -force to make sure it runs the whole flash process while I’m troubleshooting, regardless of whether the image I’m flashing is there already or not. I’ve run it without and it does the same thing. Not related to the issue as far as I can tell.