MC7430 firmware update

greetings, I am looking for help updating the firmware on hundreds of MC7430 modems we have. I would like to confirm the process as the windows update tool we have just downloaded and run has bricked our first device and I do not want to repeat the process.

The current version on our devices is
SWI9X30C_02.20.03.00 r6691 CARMD-EV-FRMWR2 2016/06/30 10:54:05

and I want to update to the latest version compatible with the new Zealand telco. I assume the correct firmware to upgrade to is ( Telstra SWI9X30C_02.33.03.00)
but I would like to confirm this please?

which tool has bricked the module?
Is it the exe of " Telstra SWI9X30C_02.33.03.00"?

Yes, our software dev has downloaded the .exe of Telstra SWI9X30C_02.33.03.00 and this is his exact response to his attempt.

"The update tool said the update was successful (see attached log) but the modem is dead. It resets every couple of seconds and nothing is showing up in device manager. "

no problem is found on my side:

ati3
Manufacturer: Sierra Wireless, Incorporated
Model: MC7430
Revision: SWI9X30C_02.20.03.01 r6748 CARMD-EV-FRMWR2 2016/08/12 01:47:36
MEID: 35907406012345
IMEI: 359074060123452
IMEI SV:  7
FSN: LU626300112345
+GCAP: +CGSM


OK

at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
FW   1    GOOD   135 0 0      ?_?         02.38.00.00_?
FW   2    GOOD   136 0 0      ?_?         02.20.03.01_?
FW   3    GOOD   131 0 0      ?_?         02.24.03.00_?
FW   4    GOOD   129 0 0      ?_?         02.24.05.06_?
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      000.010_000 02.14.03.00_DOCOMO
PRI  FF   GOOD   0   0 0      002.082_000 02.38.00.00_GENERIC
PRI  FF   GOOD   0   0 0      002.019_002 02.20.03.01_TELSTRA
Max PRI images: 50


OK
*****************After running 9999999_9904890_SWI9X30C_02.20.03.01_00_TELSTRA_002.019_002.exe*****************



ati3
Manufacturer: Sierra Wireless, Incorporated
Model: MC7430
Revision: SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30
MEID: 35907406012345
IMEI: 359074060123452
IMEI SV: 20
FSN: LU626300112345
+GCAP: +CGSM


OK
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
FW   1    GOOD   135 0 0      ?_?         02.38.00.00_?
FW   2    GOOD   136 0 0      ?_?         02.33.03.00_?
FW   3    GOOD   131 0 0      ?_?         02.24.03.00_?
FW   4    GOOD   129 0 0      ?_?         02.24.05.06_?
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      000.010_000 02.14.03.00_DOCOMO
PRI  FF   GOOD   0   0 0      002.082_000 02.38.00.00_GENERIC
PRI  FF   GOOD   0   0 0      002.067_001 02.33.03.00_TELSTRA
Max PRI images: 50


OK

Greetings and thanks for your help :slight_smile:

can you please confirm the correct procedure to perform the update? I will take a modem and use a USB to PCImini adaptor and see if I can perform the update using my windows 11 PC.

do i need to use the AT command !BOOTHOLD before performing the .exe update for example?

i put the module in dev kit and just double click the exe in windows 11…

is there a way to do it without the devkit?

dev kit is just an example, other use might use their custom board.
Have you verified before whether FW upgrade is possible in your board?

No i have not verified. how do we do that?

normally user will run the exe to verify, same as what you have done before
no idea why your board is not able to upgrade FW …

this is similar to the adaptor i have that allows me to connect the MC7430 to my wondows s11 PC
https://www.aliexpress.com/item/1005004656051012.html?spm=a2g0o.detail.0.0.4ab86gE96gE98t&gps-id=pcDetailTopMoreOtherSeller&scm=1007.40050.281175.0&scm_id=1007.40050.281175.0&scm-url=1007.40050.281175.0&pvid=e1226e01-0e23-4b6b-b93c-e3ee0f7065bb&_t=gps-id:pcDetailTopMoreOtherSeller,scm-url:1007.40050.281175.0,pvid:e1226e01-0e23-4b6b-b93c-e3ee0f7065bb,tpp_buckets:668%232846%238109%231935&pdp_npi=4%40dis!NZD!16.14!7.75!!!9.62!!%402101ef7016915498308773786e810c!12000029999746279!rec!NZ!1612001130!

what else should I do because we cannot continue to brick the devices… how can we recover devices that have been bricked?

so nothing is seen in the device manager for the bricked device?
Have you tried to connect the bricked device to linux PC and check dmesg?

no not yet but i will ask my colleague to try

Said colleague here. I have a log of the update process:

https://pastebin.com/BSssUQBY

I didn’t execute the 9999999_9904609_SWI9X30C_02.38.00.00_00_GENERIC_002.082_000.exe directly but extracted the fdt2.exe and called it with the arguments from combo_script.txt with the additional logging enabled.

After the update the modem seems to be in what looks like a boot loop. Avery couple of seconds the status LEDs on my development board turn off for a second and then back on. In device manager nothing is showing up.

Have you tried to connect the bricked device to linux PC and check dmesg

I can try that tomorrow when I have access to the modem again.

Try keeping it boot loop overnight and see if if it can recover

False alarm, the problem wasn’t the modem but the dev-board I was using. It has power issues and worked by chance when I did the update but afterwards crapped out. On a different board the modem booted fine and the update was applied.

Good afternoon. I have a similar problem. After trying to update with an .exe file, the modem has no information about the current firmware version and two unidentified Qualcomm™ Snapdragon™ X7 LTE DW5819 devices appeared in the Win 10 Device Manager. The modem sees the SIM card, but does not connect to the network. Please help.


Do you have modem port in device manager?

If you are talking about Com, then no. Only Com from the motherboard.