MC7455 lower power mode (config name mismatch) after latest FW

Title pretty much says it. I tried to flash the latest generic firmware onto my generic MC7455 and it all looked like it went fine. However, the modem now comes up stuck in “low power mode”. After some digging I believe this is due to a “config name mismatch”, but I cannot seem to fix it.

Details:
ATI
Manufacturer: Sierra Wireless, Incorporated
Model: MC7455
Revision: SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30
IMEI: REDACTED
IMEI SV: 20
FSN: REDACTED
+GCAP: +CGSM

at!priid?
PRI Part Number: 9907763
Revision: 002.072
Customer: GENERIC

Carrier PRI: None

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

at!gstatus?
!GSTATUS:
Current Time:  434              Temperature: 29
Reset Counter: 3                Mode:        LOW POWER MODE


OK

Tried the following with no luck:
AT!ENTERCND=“A710”
AT!USBPID=9071,9070
AT!USBVID=1199
AT!PRIID=“9907763”,“002.072”,“GENERIC”
AT!IMAGE=0
AT!RESET
(followed by re-flashing)

I am dead in the water. Any help is appreciated.

Hi @alex.ciarlillo

You can try to do these steps as below:
1.Clear all firmware entries and NVUs:
AT!ENTERCND=“A710”
AT!IMAGE=0
AT!RESET
2. Download the latest firmware (SWI9X30C_02.33.03.00 Generic) to the module
https://source.sierrawireless.com/resources/airprime/minicard/74xx/airprime-em_mc74xx-approved-fw-packages/#sthash.u3x3NZkA.dpbs
3. Set image management preferences
AT!ENTERCND=“A710”
AT!IMPREF=“GENERIC”
AT!RESET
4.Provide some information about your module using below commands
ATI3
AT!ENTERCND=“A710”
AT!HWID?
AT!IMPREF?
AT!IMAGE?
AT!PRIID?
AT!GSTATUS?
AT!SKU?

Hi @Donald

I have run those commands and tried re-flashing a few times now, along with trying AT!RMARESET before re-flashing.

Here is the output of the commands you asked for:

Send:ATI3

Recieve: ATI3
Recieve: Manufacturer: Sierra Wireless, Incorporated
Recieve: Model: MC7455
Recieve: Revision: SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30
Recieve: IMEI: REDACTED
Recieve: IMEI SV: 20
Recieve: FSN: REDACTED
Recieve: +GCAP: +CGSM
Recieve: OK

Send:AT!ENTERCND="A710"

Recieve: AT!ENTERCND="A710"
Recieve: OK

Send:AT!HWID?

Recieve: AT!HWID?
Recieve: Revision: 1.0
Recieve: OK

Send:AT!IMPREF?

Recieve: AT!IMPREF?
Recieve: !IMPREF: 
Recieve:  preferred fw version:    02.33.03.00
Recieve:  preferred carrier name:  GENERIC
Recieve:  preferred config name:   GENERIC_002.072_000
Recieve:  preferred subpri index:  000
Recieve:  current fw version:      02.33.03.00
Recieve:  current carrier name:    GENERIC
Recieve:  current config name:     GENERIC_002.026_000
Recieve:  current subpri index:    000
Recieve:  config name mismatch
Recieve: OK

Send:AT!IMAGE?

Recieve: AT!IMAGE?
Recieve: TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
Recieve: FW   1    GOOD   1   0 0      ?_?         02.33.03.00_?
Recieve: FW   2    EMPTY  0   0 0                  
Recieve: FW   3    EMPTY  0   0 0                  
Recieve: FW   4    EMPTY  0   0 0                  
Recieve: Max FW images: 4
Recieve: Active FW image is at slot 1
Recieve: TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
Recieve: PRI  FF   GOOD   0   0 0      002.072_000 02.33.03.00_GENERIC
Recieve: Max PRI images: 50
Recieve: OK

Send:AT!PRIID?

Recieve: AT!PRIID?
Recieve: PRI Part Number: 9904609
Recieve: Revision: 002.072
Recieve: Customer: Generic-Laptop
Recieve: Carrier PRI: None
Recieve: OK

Send:AT!SKU?

Recieve: AT!SKU?
Recieve: SKU: 1103789
Recieve: OK

Send:AT!GSTATUS?

Recieve: AT!GSTATUS?
Recieve: !GSTATUS: 
Recieve: Current Time:  96		Temperature: 27
Recieve: Reset Counter: 1		Mode:        LOW POWER MODE 
Recieve: OK

Send:AT!IMPREF?

Recieve: AT!IMPREF?
Recieve: !IMPREF: 
Recieve:  preferred fw version:    02.33.03.00
Recieve:  preferred carrier name:  GENERIC
Recieve:  preferred config name:   GENERIC_002.072_000
Recieve:  preferred subpri index:  000
Recieve:  current fw version:      02.33.03.00
Recieve:  current carrier name:    GENERIC
Recieve:  current config name:     GENERIC_002.026_000
Recieve:  current subpri index:    000
Recieve:  config name mismatch
Recieve: OK

Hi @alex.ciarlillo

This issue has not been reproduced with MC7455 firmware SWI9X30C_02.33.03.00 Generic on my side.

PRI file is not switched correctly after upgrading the firmware on your module.

You can try to do these steps as below:
AT!ENTERCND=“A710”
AT!IMPREF=“02.33.03.00"”“GENERIC”,“GENERIC_002.072_000”
AT!PRIID=“9904609”,“002.072”,“GENERIC”
AT!RESET
AT!IMPREF?
AT!IMAGE?
AT!PRIID?
AT!GSTATUS?

@Donald @alex.ciarlillo
I am experiencing the same problem. For some reason, the modem is selecting the generic PRI from original firmware:
Carrier PRI: 9999999_9904609_SWI9X30C_02.24.05.06_00_GENERIC_002.026_000

Even though I’ve run AT!IMAGE=0 and downloaded the latest Verizon firmware/PRI. The Verizon PRI is the only one listed by AT!IMAGE? and yet the modem chooses Generic 002.026.
I’ve set AT!PRIID="9904780","002.079","hi" and AT!RESET. Doesn’t matter. I still get:

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

I’d love to hear thoughts or ideas that anyone has on this.

@perrysteger

So if you include the response to at!image? then we can see everything that is on the unit.

I would try the below command
at!impref=“GENERIC”
at!reset

Regards

Matt

@mlw here’s my minicom session, right after AT!IMAGE=0 and download latest Verizon firmware:

at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
FW   1    GOOD   1   0 0      ?_?         02.33.03.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.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:  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

and here is the result of doing the same thing with latest Generic:

at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
FW   1    GOOD   1   0 0      ?_?         02.33.03.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.072_000 02.33.03.00_GENERIC
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

I have one MC7455 (SKU 1103789) Rev B and both of these work fine. But I have several Rev A modems, and none of these will successfully load the correct PRI unless I revert to the 02.24.05 firmware that they shipped with. Does not work with 02.30.03, 02.32.11 or latest 02.33.03.

In summary: MC7455 Rev B modems are upgradeable. MC7455 Rev A modems only work with 02.24.05 firmware. We have a ton of Rev A modems deployed, and I would like the option of upgrading their firmware, so I still need a fix for this!

A little more info here. I have tried to set PRIID and this does not appear to be working:

at!priid="9904780","002.079","hi-there"
OK
at!priid?
PRI Part Number: 9904780
Revision: 002.079
Customer: hi-there

Carrier PRI: None

I think that “Carrier PRI: None” means that it doesn’t like my PRI…

@perrysteger

So can you send the below commands to the unit as everything looks like it should work. We have only ever had a single hardware revision that has shipped from the factory. We may have substituted like for like components but there has never been a memory change or refresh of the design which would mean that it only worked up to version X of the firmware.

at!hwid?
at!pcinfo?

Also a picture of one of the ‘rev A’ units would be useful as I cannot see a rev on mine (and its pretty old) but this could have changed over time.

Regards

Matt

@mlw thanks so much for responding. Here’s a dump of a minicom session this morning. Just downloaded the latest Verizon firmware/PRI combo and:

I’m guessing the since AT!PRIID? returning “Carrier PRI: None” may be a symptom of the problem.

at!entercnd="A710"
OK
at!hwid?
Revision: 1.0

OK
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, FOTA:0
LPM persistence - None

OK
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 1 0 0 ?_? 02.33.03.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.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: 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!priid?
PRI Part Number: 9904780
Revision: 002.079
Customer: hi

Carrier PRI: None

OK

@perrysteger

So I have a HW 1.0 unit as well and have no issues so I do not think it is anything do with this.

In the unit above you have the preferred set to VERIZON and the current set to GENERIC which is where the mismatch comes in (which is surprising given you do not have the GENERIC PRI file loaded). If you send the below then I think it will work.

at!impref=“VERIZON”
at!reset

That should set the current, the preferred and what is on the unit to line up.

Regards

Matt

@mlw Oh, I wish it were that easy. Here you go:

at!impref="VERIZON"
OK
at!reset
OK
(wait for modem to reset...)
ate
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

Can I ship you one of these modems? I have several that behave identically. I don’t need it back – just want to figure out how to get the firmware upgraded…

@perrysteger

So last ditch attempt, try the below command, this sets it back to ground 0 as far as is possible (its not possible to completely make it factory fresh).

at!rmareset=0

Might need a reset afterwards might not.

Regards

Matt

@mlw I’m all for last ditch efforts! Here it is:

at!rmareset=0
ERROR
at!entercnd="A710"
OK
at!rmareset=0
ERROR
at!rmareset?
!RMARESET: 
3 Latest


OK

I could do at!rmareset=3 for you, but I’ve done that already…

TechShip tech support asked me to try AT!IMPREF="AUTO-SIM", so here that is:

at!impref="AUTO-SIM"
OK
ate
OK
at!impref?
!IMPREF: 
 preferred fw version:    00.00.00.00
 preferred carrier name:  AUTO-SIM
 preferred config name:   AUTO-SIM_000.000_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

 carrier name mismatch
 config name mismatch

OK

And just for completeness, here’s AT!RMARESET=3:

at!rmareset=3
!RMARESET: DEVICE REBOOT REQUIRED

Items Restored:  1730
Items Deleted:   0
Items Skipped:   7

OK
at!reset
OK
ate
OK
at!impref?
!IMPREF: 
 preferred fw version:    02.24.05.06
 preferred carrier name:  GENERIC
 preferred config name:   GENERIC_002.026_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

 fw version mismatch

OK

Thanks for sticking with me on this.

Have you tried on Linux? You can give it a try by using the modem on a Linux PC and setting AT!IMAGE=“carrier”, AT!RESET based on what AT!IMAGE? shows you have on the modem.

@ajoseph yep – tried AT!IMPREF=“VERIZON” and “GENERIC”. This modem still reaches for an older unlisted generic PRI and gets carrier mismatch or version mismatch.

Thanks for trying @perrysteger. Would you please reach out via your Sierra or distributor support channel. We’ll look deeper into this issue that you are facing via the support channel. Thanks.

@ajoseph Could you give me some help contacting someone directly at Sierra? Thanks.

I believe this proves there is something seriously wrong with that module. The “0 Factory” and “1 Provision” cannot be replaced according to the AT command manual, and I assume that means they cannot be deleted either.

FWIW, at!rmareset=0 is documented as “For information only, cannot be restored”, so you might want to try at!rmareset=1 instead. But that list of restore points does not look promising so I guess it won’t work either.

The “3 Latest” restore point is automatically backed up and restored on every firmware update, so manually restoring it is not expected to make much difference.

@dl5162 agree that there is something wrong with this modem, along with the five additional Rev A modems I have here on my desk, and maybe a hundred or so we have deployed in the field. My lone Rev B modem IS upgradable to the latest firmware. I was hopeful that I could find someone from Sierra who might take up this cause to figure out why some of their modems are not upgradable. The original message in this thread from @alex.ciarlillo documents identical symptoms.

Thanks for responding.