Fwupdate download fail

IoT Modules
1

I have some issue with fwupdate download <image.cwe> on some device. I am using wp76xx series module.

I already see:

but their issue looks different.

I have 3 devices. All devices on R13.3 Legato 19.02. I have custom system image file generate from systoimg and I can flash this image to 2 devices using fwupdate download <image.cwe>.But 1 device cannot flash. When I run update command, I see:

Connecting to service ...
Download started ...
Error in download

Then in legato logs:

Jan 1 11:01:53 swi-mdm9x28-wp user.info Legato: INFO | fwupdateDaemon[959]/le_pa_fwupdate T=main | pa_fwupdate_qmi.c pa_fwupdate_OpenSwifota() 2158 | Open SWIFOTA partition
Jan 1 11:01:53 swi-mdm9x28-wp user.err Legato: =ERR= | fwupdateDaemon[959]/swiQmi T=main | swiQmi.c swiQmi_CheckResponse() 795 | Sending QMI_SWI_M2M_FDT_OPEN_REQ_V01 failed: rc=0 (), resp.result=1.[0x01], resp.error=2.[0x02]
Jan 1 11:01:53 swi-mdm9x28-wp user.err Legato: =ERR= | fwupdateDaemon[959]/le_pa_fwupdate T=main | pa_fwupdate_qmi.c pa_fwupdate_OpenSwifota() 2169 | Failed to open SWIFOTA partition
Jan 1 11:01:53 swi-mdm9x28-wp user.info Legato: INFO | fwupdateDaemon[959]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteDwlStatus() 1716 | FW update download status stored.
Jan 1 11:01:53 swi-mdm9x28-wp user.crit Legato: CRT | fwupdateDaemon[959]/le_pa_fwupdate_singlesys T=main | partition.c partition_WriteSwifotaPartition() 1396 | Closing and releasing MTD due to forceClose
Jan 1 11:01:53 swi-mdm9x28-wp user.crit Legato: CRT | fwupdateDaemon[959]/le_pa_fwupdate_singlesys T=main | partition.c partition_CloseSwifotaPartition() 1155 | Closing and releasing MTD due to forceClose
Jan 1 11:01:53 swi-mdm9x28-wp user.info Legato: INFO | supervisor[865]/supervisor T=main | proc.c proc_SigChildHandler() 2051 | Process ‘fwupdate@0’ (PID: 1861) has exited with exit code 1.

My partition looks okay. Can someone advice?

2

how about downloading official image (e.g. R13.3.1) to this problematic module?

https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-release-13,-d-,1,-d-,1/#sthash.mu1ldr0f.IqB1Slsf.dpbs

What is the return of the following on this problematic module?

ATI3
ATI8
AT!ENTERCND="A710"
AT!IMPREF?
AT!PCINFO?
AT!bsinfo
3

I want to try without flashing official image again incase this problem happen again.

GOOD DEVICE


ATI3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7609
Revision: SWI9X07Y_02.28.03.05 000000 jenkins 2019/07/08 11:04:16
IMEI: <IMEI>
IMEI SV:  6
FSN: <FSN>
+GCAP: +CGSM

ATI8
Legato Ver: 19.02.0_57b5bfeacf0621b21422fdf5d5fd9bc6
Yocto Ver:  SWI9X07Y_02.28.04.01 2021-09-08_15:45:55
OS Ver: Linux version 3.18.131 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 PREEMPT Wed Sep 8 15:29:33 UTC 2021
LK Ver: SWI9X07Y_02.28.04.01
RootFS Ver: SWI9X07Y_02.28.04.01 2021-09-08_15:45:55
UserFS Ver: unknown
MCU Ver: 002.011

AT!ENTERCND="A710"

AT!IMPREF?
!IMPREF: 
 preferred fw version:    02.28.03.05
 preferred carrier name:  TELSTRA
 preferred config name:   TELSTRA_001.058_000
 preferred subpri index:  000
 current fw version:      02.28.03.05
 current carrier name:    TELSTRA
 current config name:     TELSTRA_001.058_000
 current subpri index:    000

AT!PCINFO?
State: Online
LPM voters - Temp:0, Volt:0, User:0, W_DISABLE:0, IMSWITCH:0, BIOS:0, LWM2M:0, OMADM:0, FOTA:0
LPM persistence - None

AT!BSINFO
Product: WP7609
Revision: 40
Main:  MDM9207 (000)
Radio: WTR2965 
Power: PMD9607 (002)
Flash: H27S4G8F2EKPB4      512MB x8 (173/0/0) (2048 blocks of 64 pages/block 4096B page size)

BAD DEVICE

ATI3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7609
Revision: SWI9X07Y_02.28.03.05 000000 jenkins 2019/07/08 11:04:16
IMEI: <IMEI>
IMEI SV:  6
FSN: <FSN>
+GCAP: +CGSM

ATI8
Legato Ver: 19.02.0_029915f8bbdfc6b6f6b921965c2e35a9
Yocto Ver:  SWI9X07Y_02.28.04.01 2021-09-08_15:45:55
OS Ver: Linux version 3.18.131 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 PREEMPT Wed Sep 8 15:29:33 UTC 2021
LK Ver: SWI9X07Y_02.28.04.01
RootFS Ver: SWI9X07Y_02.28.04.01 2021-09-08_15:45:55
UserFS Ver: unknown
MCU Ver: 002.011

AT!ENTERCND="A710"
AT!IMPREF?
!IMPREF: 
 preferred fw version:    02.28.03.05
 preferred carrier name:  TELSTRA
 preferred config name:   TELSTRA_001.058_000
 preferred subpri index:  000
 current fw version:      02.28.03.05
 current carrier name:    TELSTRA
 current config name:     TELSTRA_001.058_000
 current subpri index:    000

AT!PCINFO?
State: Online
LPM voters - Temp:0, Volt:0, User:0, W_DISABLE:0, IMSWITCH:0, BIOS:0, LWM2M:0, OMADM:0, FOTA:0
LPM persistence - None

AT!BSINFO
Product: WP7609
Revision: 40
Main:  MDM9207 (000)
Radio: WTR2965 
Power: PMD9607 (002)
Flash: H27S4G8F2EKPB4      512MB x8 (173/0/0) (2048 blocks of 64 pages/block 4096B page size)

Interesting because both say same things except Legato version.

Can this be the reason?

< Legato Ver: 19.02.0_57b5bfeacf0621b21422fdf5d5fd9bc6
> Legato Ver: 19.02.0_029915f8bbdfc6b6f6b921965c2e35a9

If this is the reason, how can I make legato same version? Leaf package on leaf only show 19.02.0

4

i have updated the official WP76xx_Release13.3.1_TELSTRA.exe to my module, and the legato version is as follows:


ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7608
Revision: SWI9X07Y_02.28.03.05 000000 jenkins 2019/07/08 11:04:16
IMEI: 352913090512345
IMEI SV:  6
FSN: XG207430012345
+GCAP: +CGSM

OK
ati8
Legato Ver: 19.02.0_4cb954265427b8c2c668a010ff5be274
Yocto Ver:  SWI9X07Y_02.28.04.01 2021-09-08_15:45:55
OS Ver: Linux version 3.18.131 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 PREEMPT Wed Sep 8 15:29:33 UTC 2021
LK Ver: SWI9X07Y_02.28.04.01
RootFS Ver: SWI9X07Y_02.28.04.01 2021-09-08_15:45:55
UserFS Ver: unknown
MCU Ver: unknown

OK

I believe legato image is updated in your module as it is different from the official one

5

Do you think legato version is the reason my fwupdate fails?

I think if I flash official R13.3 .cwe again, my system will be deleted like new - is this true? I want to keep the data and configuration of my current device

6

can you backup your data and confirm with current device first?

7

I realise that there is difference when updating device with fwupdate download <FIRMWARE>.cwe vs update <FIRMWARE>.wpxxxx.update

If update <FIRMWARE>.wpxxxx.update , I cannot flash using fwupdate download <FIRMWARE>.cwe

I can fwupdate download <FIRMWARE>.cwe, then update <FIRMWARE>.wpxxxx.update, but when I do, I cannot fwupdate download <FIRMWARE>.cwe anymore.

Why is this? Can I make it so I can fwupdate download <FIRMWARE>.cwe again?

8

what is your “.wpxxxx.update” doing ?

you can upgrade to FW official R16 and then back to official R13.3.1, and then you should be able to do fwupdate download <FIRMWARE>.cwe again

9

<FIRMWARE>.wpxxxx.update is build by mksys command

Same code as <FIRMWARE>.cwebut I use systoimgto build this image

Is there no way to fwupdate download <FIRMWARE>.cwe again on my device? I want to know if I can without flash FW again

10

you can try to clean the userapp partition by the “flash_eraseall /dev/mtdxx” command and see if you can download the .cwe again afterwards: