Flashed latest generic fw on MC7455 now "config name mismatch"

[ciarlill]

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.

Some details:

Code: Select all

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

I tried the following (from this doc: https://docs.google.com/document/d/1IO- ... Ac2JWB3Mk8)

Code: Select all

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 the firmware. Still in the same situation. So everything looks good except that damn config name and I can't change it! Any ideas?

[ciarlill]

Tried running the updated flashing script from this thread: https://wirelessjoint.com/viewtopic.php?f=17 ... ELP#p10286 on an ubuntu live USB. Flashed just fine... same result.

[BillA]

Tried running the updated flashing script from this thread: https://wirelessjoint.com/viewtopic.php?f=17 ... ELP#p10286 on an ubuntu live USB. Flashed just fine... same result.

After flashing it, try running these commands (one of the reset commands will fails which is fine):

AT!ENTERCND="A710"
AT!RMARESET=OEM
AT!RMARESET=1
AT!RESET

Wait a minute then:
AT!ENTERCND="A710"
AT!IMPREF="GENERIC"
AT!RESET

[ciarlill]

After flashing it, try running these commands (one of the reset commands will fails which is fine):

AT!ENTERCND="A710"
AT!RMARESET=OEM
AT!RMARESET=1
AT!RESET

Wait a minute then:
AT!ENTERCND="A710"
AT!IMPREF="GENERIC"
AT!RESET

No dice. I tried running through everything twice.

Here is AT!IMAGE?

Code: Select all

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

I _think_ this looks right... but still the same IMPREF:

Code: Select all

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

WTF is _002.026 even coming from!

[BillA]

I _think_ this looks right... but still the same IMPREF:

Code: Select all

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

WTF is _002.026 even coming from!

The second one looks better, I would try reflashing it again and run the reset commands again.
The older version string might be for informational purposes only, I wouldn't worry about it as long as the modem is working fine.

[ciarlill]

The second one looks better, I would try reflashing it again and run the reset commands again.
The older version string might be for informational purposes only, I wouldn't worry about it as long as the modem is working fine.

I've run the reset and flashing process twice now, still get stuck with that same "current config name". The frustrating thing is I cannot even find a firmware with matching PRI to try to flash to get out of this now. Still reading through this thread looking for ideas to try: https://forum.sierrawireless.com/t/firm ... 0/12829/14

[BillA]

I've run the reset and flashing process twice now, still get stuck with that same "current config name". The frustrating thing is I cannot even find a firmware with matching PRI to try to flash to get out of this now. Still reading through this thread looking for ideas to try: https://forum.sierrawireless.com/t/firm ... 0/12829/14

It may be a shot in the dark, but try switching to one of the other images then back to generic using the AT!IMPREF="<name>" command, maybe it's just stuck. Besides, if the modem is functioning on generic, I wouldn't worry about the version string too much.

[ciarlill]

It may be a shot in the dark, but try switching to one of the other images then back to generic using the AT!IMPREF="<name>" command, maybe it's just stuck. Besides, if the modem is functioning on generic, I wouldn't worry about the version string too much.

Yeah I will try flashing some other images to maybe get it unstuck. However the version string appears to be important in this case and the "config name mismatch" is causing the modem to be stuck in low power mode. But maybe that is a red herring and the real cause is something else?

Code: Select all

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

[BillA]

Yeah I will try flashing some other images to maybe get it unstuck. However the version string appears to be important in this case and the "config name mismatch" is causing the modem to be stuck in low power mode. But maybe that is a red herring and the real cause is something else?

Code: Select all

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

I meant reflashing it with the same firmware after the reset command then reset it again.
From what I've read, it could be an engineering sample, and/or locked hardware for a laptop.
Check out this page full of great info, you could even contact Daniele Wood.
https://github.com/danielewood/sierra-wireless-modems

[ciarlill]

I meant reflashing it with the same firmware after the reset command then reset it again.
From what I've read, it could be an engineering sample, and/or locked hardware for a laptop.
Check out this page full of great info, you could even contact Daniele Wood.
https://github.com/danielewood/sierra-wireless-modems

Yeah I have come to the conclusion I have one of the dreaded engineering samples, even though it doesn't exactly match the pics. I'll try reaching out to Daniele Wood and see if he has any ideas. Thanks again!