Hi @jyijyi ,
I try it again. And I got the same result.
So is any suggestion ?
have you tried “WP76xx_Release16.1_TMO.exe”?
I don’t see problem
Hi @jyijyi ,
If I only update TMO it worked, but multi upgrade will be failed.
Can you try this?
fdt2.exe -d wpspk -mi -f WP76xx_Release16.0.1_ATT.spk WP76xx_Release16.1_TMO.spk
Please note that after the upgrade, AT!IMAGE should contain those FWs:
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 8 0 0 002.098_003 02.37.00.00_ATT
FW 2 GOOD 9 0 1 001.017_001 02.35.02.00_TMO
FW 3 GOOD 7 0 0 002.095_003 02.37.03.00_GENERIC
Max FW images: 3
Active FW image is at slot 2
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 002.098_003 02.37.00.00_ATT
PRI FF GOOD 0 0 0 002.095_003 02.37.03.00_GENERIC
PRI FF GOOD 0 0 0 001.017_001 02.35.02.00_TMO
Max PRI images: 50
OK
Hi @jyijyi ,
I follow your commnad: .\fdt2.exe -force -d wpspk -mi -f WP76xx_Release16.1_ATT.spk WP76xx_Release16.1_TMO.spk WP76xx_Release16.1_VERIZON.spk WP76xx_Release16.1_GENERIC.spk
add “-mi” and I got the result in at!image?
at!image?
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 127 0 0 002.126_000 02.37.03.05_ATT
FW 2 GOOD 6 0 0 001.017_001 02.35.02.00_TMO
FW 3 GOOD 5 0 0 002.107_003 02.37.06.00_VERIZON
Max FW images: 3
Active FW image is at slot 1
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 002.126_000 02.37.03.05_ATT
PRI FF GOOD 0 0 0 002.115_002 02.37.03.05_GENERIC
PRI FF GOOD 0 0 0 001.060_000 02.37.03.00_SIERRA
PRI FF GOOD 0 0 0 001.027_000 02.37.02.00_SPRINT
PRI FF GOOD 0 0 0 001.027_000 02.37.03.00_TMO
PRI FF GOOD 0 0 0 002.104_000 02.37.03.00_VERIZON
Max PRI images: 50
OK
The FW will be right but the PRI will be wrong in TMO.
And FDT will display error.
can you try two images (ATT and TMO)first?
Hi @jyijyi ,
I try download ATT and TMO,
.\fdt2.exe -force -d wpspk -mi -f WP76xx_Release16.1_ATT.spk WP76xx_Release16.1_TMO.spk
And got the result in at!image?
at!image?
at!image?
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 128 0 0 002.126_000 02.37.03.05_ATT
FW 2 GOOD 1 0 0 001.017_001 02.35.02.00_TMO
FW 3 GOOD 127 0 0 002.107_003 02.37.06.00_VERIZON
Max FW images: 3
Active FW image is at slot 1
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
PRI FF GOOD 0 0 0 002.126_000 02.37.03.05_ATT
Max PRI images: 50
OK
FW result is good but PRI result is wrong!!!
I found that you need to run the command twice, first one for FW slot, second one for PRI
- fdt2.exe -d wpspk -mi -f WP76xx_Release16.1_GENERIC.spk WP76xx_Release16.1_TMO.spk
- fdt2.exe -mi -f WP76xx_Release16.1_GENERIC.spk WP76xx_Release16.1_TMO.spk
Hi @jyijyi ,
why it needs execute twice command?
I don’t know, seems this is the workaround if you don’t want to download exe one by one.
It takes too long time, so i don’t want download one by one.
Does any possible to solve this problem ?
how about running twice the commands?
It is working fine for you?
Not sure if the Linux SDK can help you on this
Hi @jyijyi ,
I try 4 images , and run command twice it does not work.
there are only 3 FW slot
have you tried 3 images?
Hi @jyijyi ,
ATT and GENERIC is the same FW so I think is enough slot to save FW.
I tried with 3 images with following commands, it is working fine:
- fdt2.exe -d wpspk -mi -f WP76xx_Release16.1_GENERIC.spk WP76xx_Release16.1_TMO.spk WP76xx_Release16.1_VERIZON.spk
- fdt2.exe -mi -f WP76xx_Release16.1_TMO.spk WP76xx_Release16.1_VERIZON.spk
for 4 images, you can do the following:
- fdt2.exe -d wpspk -mi -f WP76xx_Release16.1_GENERIC.spk WP76xx_Release16.1_TMO.spk WP76xx_Release16.1_VERIZON.spk
- fdt2.exe -mi -f 9999999_9907256_SWI9X07Y_02.37.03.05_00_ATT_002.126_000.spk 9999999_9909268_SWI9X07Y_02.35.02.00_00_TMO_001.017_001.spk 9999999_9907255_SWI9X07Y_02.37.06.00_00_VERIZON_002.107_003.spk
The modem FW can be downloaded here:
https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-release-16,-d-,1-components/#sthash.mdciAUFJ.dpbs
Hi @jyijyi ,
what’s difference between 1 and 2 ?
step 1 is for FW, step 2 is for PRI
The second files does not include FW ?