Fwupdate / swiflash doesn't seems to be working

Hi @jyijyi ,

I have come across 2 No’s of wp7608 modules where in fwupdate / swiflash doesn’t seems to be updating the firmware . strangely reset.cwe doesnt work with fwupdate but works with dev studio’s recovery wizard .

attached are the logs from the device for your reference .

Below are command responses

root@swi-mdm9x28-wp:~# cat /etc/legato/version
Build created at 2018-09-20_16:17:38

Yocto build version: SWI9X07Y_02.18.06.00

Build host: jenkins
Versions:

  • firmware: SWI9X07Y_02.18.06.00
  • poky: yocto-2.2.3-57-ge6aadcc2
  • meta-openembedded: b40116c
  • meta-swi: 5fd8531
  • meta-swi-extras: 0e6dd5d
  • linux-quic-quic: 3.18.44
    root@swi-mdm9x28-wp:~# fwupdate query
    Connecting to service …
    Firmware Version: SWI9X07Y_02.18.05.00 000000 jenkins 2018/07/19 17:40:21
    Bootloader Version: SWI9X07Y_02.18.05.00 000000 jenkins 2018/07/19 17:40:21
    Linux Version: 3.18.44 #2 PREEMPT Thu Sep 20 16:20:02 UTC 2018
    root@swi-mdm9x28-wp:~# df -h
    Filesystem Size Used Available Use% Mounted on
    devtmpfs 256.0K 8.0K 248.0K 3% /dev
    /dev/mapper/rt 16.3M 16.3M 0 100% /
    mdev 256.0K 8.0K 248.0K 3% /dev
    tmpfs 76.3M 0 76.3M 0% /dev/shm
    tmpfs 76.3M 0 76.3M 0% /run
    tmpfs 76.3M 44.0K 76.2M 0% /var
    tmpfs 76.3M 32.0K 76.2M 0% /tmp
    mdev 256.0K 8.0K 248.0K 3% /dev
    tmpfs 76.3M 0 76.3M 0% /dev/shm
    tmpfs 76.3M 0 76.3M 0% /run
    tmpfs 76.3M 44.0K 76.2M 0% /var
    tmpfs 76.3M 32.0K 76.2M 0% /tmp
    /dev/ubi3_0 104.5M 60.1M 39.8M 60% /mnt/flash
    /dev/ubiblock2_0 3.8M 3.8M 0 100% /mnt/legato
    /dev/ubi4_0 8.7M 76.0K 8.1M 1% /mnt/userrw
    overlay 104.5M 60.1M 39.8M 60% /etc
    overlay 104.5M 60.1M 39.8M 60% /data
    overlay 104.5M 60.1M 39.8M 60% /lib/firmware
    /dev/ubi3_0 104.5M 60.1M 39.8M 60% /home
    /dev/ubiblock1_0 24.8M 24.8M 0 100% /firmware
    /dev/ubi3_0 104.5M 60.1M 39.8M 60% /legato
    tmpfs 76.3M 32.0K 76.2M 0% /etc/ld.so.conf
    tmpfs 76.3M 32.0K 76.2M 0% /etc/ld.so.cache
    tmpfs 76.3M 32.0K 76.2M 0% /etc/hosts
    cgroupsRoot 77.6M 0 77.6M 0% /sys/fs/cgroup
    /dev/ubi3_0 104.5M 60.1M 39.8M 60% /legato/systems/current
    root@swi-mdm9x28-wp:~# cm info all
    Device: WP7608
    IMEI: 352913090156819
    IMEISV: 5
    FSN: XG909500511310
    Firmware Version: SWI9X07Y_02.18.05.00 000000 jenkins 2018/07/19 17:40:21
    Bootloader Version: SWI9X07Y_02.18.05.00 000000 jenkins 2018/07/19 17:40:21
    MCU Version: 002.009
    PRI Part Number (PN): 9908665
    PRI Revision: 001.001
    Carrier PRI Name: GENERIC
    Carrier PRI Revision: 002.041_002
    SKU: 1104194
    Last Reset Cause: Reset, User Requested
    Resets Count: Expected: 3 Unexpected: 0

==================== AT LOGS ========================
at!oemauth?

!OEMAUTH: Disabled
OEM cert hash: Not provisioned

OK
ati3

Manufacturer: Sierra Wireless, Incorporated
Model: WP7608
Revision: SWI9X07Y_02.18.05.00 000000 jenkins 2018/07/19 17:40:21
IMEI: 352913090156819
IMEI SV: 5
FSN: XG909500511310
+GCAP: +CGSM

OK
at!impref?

!IMPREF:
preferred fw version: 02.18.05.00
preferred carrier name: GENERIC
preferred config name: GENERIC_002.041_002
current fw version: 02.18.05.00
current carrier name: GENERIC
current config name: GENERIC_002.041_002

OK

=================== logread during FWUPDATE===========================

Jan 6 00:38:38 | fwupdateDaemon[877]/le_pa_fwupdate T=main | pa_fwupdate_qmi.c pa_fwupdate_Download() 1242 | Download completed
Jan 6 00:38:38 | fwupdateDaemon[877]/le_pa_fwupdate T=main | pa_fwupdate_qmi.c pa_fwupdate_Download() 1285 | Download Complete
Jan 6 00:38:38 | fwupdateDaemon[877]/le_pa_fwupdate T=main | pa_fwupdate_qmi.c pa_fwupdate_Install() 1763 | Install command successful. System resetting.
Jan 6 00:38:38 | fwupdateDaemon[877]/fwupdateDaemon T=main | fwupdateServer.c le_fwupdate_InstallAndMarkGood() 408 | !!! Error LE_OK

====================================================================
Please let me know the possible reason for the same .

BOOT_DMESG_DEV2.txt (64.5 KB)
CONSOLE-My new device-20210525-145820_DEV2.txt (15.8 KB)
BOOT_LOGREAD_DEV2.txt (333.1 KB)

how about the one click exe on Windows platform?

@jyijyi
I tried flashing using the one click tool as well as the recovery wizard but only reset.cwe seems to be working with recovery wizard .

same custom image was flashed on thousands of wp7608 modules .

i could see below line in logread

Jan 1 00:39:28 swi-mdm9x28-wp user.err kernel: [ 7.397042] UBIFS error (pid: 477): cannot open “ubi0:usrfs”, error -19

File : BOOT_LOGREAD_DEV2.txt

Can you erase the user app partition by swiflash

Did not test it . but as of now reset.cwe works with recovery wizard in dev studio but same when tried with custom yocto cwe /spk or legato cwe doesnt seems to be working . ( There is an option in recovery wizard to flash custom images as well )
What do you suspect here ?

Just see if it helps to revert back to default state

Ok let me check and get back to you . meanwhile the issue is similar to what has been discussed here but in my case the image size is correct

Hi @jyijyi ,

Just a quick question . How will the module behave if the fw file was partially copied and attempts were made to update it ?

I believe it will not update, i tried to update with some txt file, it would abort

I have around 3-4 modules where in i am unable to update any firmware . I was suspecting if attempts of updating partial files could have caused this or the modules are in this state from factory ?

have you tried to erase user app partition and see if it helps?

I tried erasing it with recovery wizard though the recovery is successful but any other firmware flashed later are not installed .

Below are the steps I followed
Step 1) Factory reset using recovery wizard in devstudio (Windows OS)
=> This was successful as i saw the files being deleted
Step 2) Flashed custom Yocto image which was not installed even though there was reboot . (command used : fwupdate download Yocto_file )

do you have the UART console log for step 2?

No I just have the logread , dmesg logs I believe it will have the details required . If not i will try to capture those logs

You can also capture the uart console log for more hints