OK
AT!IMPREF?
!IMPREF:
preferred fw version: 02.33.03.00
preferred carrier name: VERIZON
preferred config name: VERIZON_002.079_001
preferred subpri index: 000
current fw version: 02.33.03.00
current carrier name: GENERIC
current config name: GENERIC_002.026_000
current subpri index: 000
carrier name mismatch
config name mismatch
OK
AT!IMAGE?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 1 0 0 ?? 02.24.05.06?
FW 2 GOOD 2 0 0 ?? 02.33.03.00?
FW 3 EMPTY 0 0 0
FW 4 EMPTY 0 0 0
Max FW images: 4
Active FW image is at slot 2
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 002.026_000 02.24.05.06_GENERIC
PRI FF GOOD 0 0 0 002.079_001 02.33.03.00_VERIZON
Max PRI images: 50
OK
AT!PRIID?
PRI Part Number: 9907763
Revision: 001.001
Customer: Generic-M2M
If i change AT!IMPREF=“GENERIC” it works fine using an AT&T M2M SIM card on m2m.com.attz however when I change to AT!IMPREF=“VERIZON” it updates the preferred and the current fw version however current carrier name and current config name does not change and the card goes into low power mode.
After updating the card with the latest generic, this is what I get
pi@raspberrypi:~/firmware/generic $ sudo qmi-firmware-update --update --cdc-wdm /dev/cdc-wdm0 SWI9X30C_02.33.03.00_GENERIC_002.072_000.nvu SWI9X30C_02.33.03.00.cwe
loading device information before the update...
setting firmware preference:
firmware version: '02.33.03.00'
config version: '002.072_000'
carrier: 'GENERIC'
rebooting in download mode...
download mode detected
downloading cwe image: SWI9X30C_02.33.03.00.cwe (64.4 MB)...
finalizing download... (may take more than one minute, be patient)
successfully downloaded in 56.09s (1.1 MB/s)
downloading cwe image: SWI9X30C_02.33.03.00_GENERIC_002.072_000.nvu (3.3 kB)...
finalizing download... (may take more than one minute, be patient)
successfully downloaded in 0.05s (63.5 kB/s)
rebooting in normal mode...
normal mode detected
------------------------------------------------------------------------
NOTE: in order to validate which is the firmware running in the
module, the program will wait for a complete boot; this process
may take some time and several retries.
------------------------------------------------------------------------
waiting some time for the device to boot...
loading device information after the update (1/12)...
------------------------------------------------------------------------
original firmware revision was:
SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30
original running firmware details:
Model: MC7455
Boot version: SWI9X30C_02.33.03.00
AMSS version: SWI9X30C_02.33.03.00
SKU ID: 1103789
Carrier ID: 0
Config version: 002.026_000
original firmware preference details:
image 'modem': unique id '002.079_001', build id '02.33.03.00_VERIZON'
image 'pri': unique id '002.079_001', build id '02.33.03.00_VERIZON'
new firmware revision is:
SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30
new running firmware details:
Model: MC7455
Boot version: SWI9X30C_02.33.03.00
AMSS version: SWI9X30C_02.33.03.00
SKU ID: 1103789
Carrier ID: 0
Config version: 002.026_000
new firmware preference details:
image 'modem': unique id '002.072_000', build id '02.33.03.00_GENERIC'
image 'pri': unique id '002.072_000', build id '02.33.03.00_GENERIC'
NOTE: this device supports stored image management
with qmicli operations:
--dms-list-stored-images
--dms-select-stored-image
--dms-delete-stored-image
NOTE: this device supports firmware preference management
with qmicli operations:
--dms-get-firmware-preference
--dms-set-firmware-preference
------------------------------------------------------------------------
firmware update operation finished successfully
The current version will not change.
logging into the modem and showing the impref;
AT!IMPREF?
!IMPREF:
preferred fw version: 02.33.03.00
preferred carrier name: GENERIC
preferred config name: GENERIC_002.072_000
preferred subpri index: 000
current fw version: 02.33.03.00
current carrier name: GENERIC
current config name: GENERIC_002.026_000
current subpri index: 000
config name mismatch
OK
Hi Matthew,
What is the output of “AT!IMAGE?” command?
I’m not sure what is the root cause, but you can set the image manually to fix the mismatch
AT!IMPREF =“fw version”[,[“carrier name”,]“config name”]
Hi Matthew,
As I mentioned above, UNLOCK command is required for setting firmware with IMPREF command
Example:
at!impref="02.28.03.03","GENERIC","GENERIC_002.068_000"
ERROR
AT!ENTERCND="A710"
OK
at!impref="02.28.03.03","GENERIC","GENERIC_002.068_000"
ERROR
at!unlock="A710"
OK
at!impref="02.28.03.03","GENERIC","GENERIC_002.068_000"
OK
Even after doing that the following command throws an error;
AT!UNLOCK
ERROR
AT!UNLOCK="a710"
ERROR
AT!IMAGE?="
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 8 0 0 ?_? 02.24.05.06_?
FW 2 GOOD 9 0 0 ?_? 02.33.03.00_?
FW 3 GOOD 7 0 0 ?_? 02.32.11.00_?
FW 4 EMPTY 0 0 0
Max FW images: 4
Active FW image is at slot 2
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 002.070_002 02.32.11.00_ATT
PRI FF GOOD 0 0 0 002.072_000 02.33.03.00_GENERIC
PRI FF GOOD 0 0 0 002.079_001 02.33.03.00_VERIZON
Max PRI images: 50
OK
AT!IMPREF?
!IMPREF:
preferred fw version: 02.33.03.00
preferred carrier name: GENERIC
preferred config name: GENERIC_002.072_000
preferred subpri index: 000
current fw version: 02.33.03.00
current carrier name: GENERIC
current config name: GENERIC_002.026_000
current subpri index: 000
config name mismatch
OK
AT!ENTERCND="A710"
OK
AT!IMPREF="02.33.03.00","GENERIC","GENERIC_002.072.000"
ERROR
Hi Matthew,
Oh, I’m sorry, It is my mistake, your device could not use UNLOCK command.
Could you please try to change to VERIZON image and then back to GENERIC?
Please help to try these commands, and send us the output:
AT!IMPREF=“VERIZON”
AT!RESET
AT!IMAGE?
AT!IMPREF?
AT!IMPREF=“GENERIC”
AT!RESET
AT!IMAGE?
AT!IMPREF?
Again none of these commands are making a difference. I cannot get the “Current Config Name:” name to change and as a result the card enters low power mode and will not activate.
I have noticed several other people are having the exact same issue on this forum.
I have requested a refund from the seller of this card as I’m unable to get this card to function.
In the mean time i’m going to try an older firmware to see if it changes.
When upgrading the firmware in these cards is there an upgrade path that must be followed?