WP7611 Does not see Verizon SIM Card

IoT Modules WP Series
1

Hello all,

I’ve got a WP7611 on a custom board running openwrt. Modemmanager detects AT&T SIM cards just fine, but with a Verizon SIM it will say broken/not found. Interestingly, the at+cpin? command will return +CPIN: READY.

This makes me think it may have to do with the firmware version on the modem; however, I have been unable to upgrade the modem because it seems the qmi-firmware-update program does not seem to support the sahara protocol. This thread discusses it some, but does not come to a conclusion that will work for me.

Since I could not update the firmware, I tried using the qmi-select-stored-image command to select the verizon modem and pri options that were already on the modem, but that did not solve the issue.

I can still issue AT commands and SSH into the modem, so I’m wondering if there is a possible path to upgrade the firmware through one of those options.

Any help would be greatly appreciated.

2

you can scp the FW to /tmp folder of the module and then use “fwupdate download /tmp/xxx.spk” to upgrade the FW.

3

Thanks for the advice!

Unfortunately, when I tried to do this the first time, it seemed to get stuck on the step where it says
installing & reboot ...
I left it going for about 3 hours, but I eventually rebooted my device. I then tried running the command again with the install argument (fwupdate install) to no avail. I also noticed that if I ssh in and run the reboot command, the shell stops responding, but hangs for several minutes before it appears to actually reboot.

Interestingly, I just tried again and it it gave me an error during the installing & reboot step and stopped responding over ssh.

root@swi-mdm9x28-wp:~# fwupdate download /tmp/WP76xx_Release16_VERIZON.spk 
Connecting to service ...
Download started ...
Download successful
Installing & Reboot ...
Error during installation: LE_FAULT

I managed to follow the log output by running the fwupdate program in the background with &.

Here is the logread output. 
.
.
.
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | partition.c partition_WriteSwifotaPartition() 1411 | Image type 23 len 65536
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteData() 655 | Type 23 len 65536 wr 65536
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteImageData() 1043 | chunk length: 65536
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteImageData() 1054 | Image data write: CRC in header: 0x7d737bed, calculated CRC 0xb257185e
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteImageData() 1071 | CurrentInImgOffset: 6488064CurrentImageSize: 6553600 wrLen: 65536
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | partition.c partition_WriteSwifotaPartition() 1411 | Image type 23 len 65536
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteData() 655 | Type 23 len 65536 wr 65536
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteImageData() 1043 | chunk length: 65536
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteImageData() 1054 | Image data write: CRC in header: 0x7d737bed, calculated CRC 0x7d737bed
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteImageData() 1071 | CurrentInImgOffset: 6553600CurrentImageSize: 6553600 wrLen: 65536
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteImageData() 1085 | Image data write end: CRC in header: 0x7d737bed, calculated CRC 0x7d737bed
Jan  6 00:03:58 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c pa_fwupdate_Download() 2261 | End of update: total read 69683259, full length expected 69683259
Download successful
Installing & Reboot ...
Jan  6 00:04:06 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | partition.c partition_ComputeDataCrc32SwifotaPartition() 1366 | Offset 190 size 69682859 CRC 34fba230
Jan  6 00:04:06 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c pa_fwupdate_Download() 2305 | End of download: globalCrc 34fba230 length 69682859
Jan  6 00:04:06 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c pa_fwupdate_Download() 2306 | Expected CRC 34fba230
Jan  6 00:04:06 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c pa_fwupdate_Download() 2315 | Closing swifota partiton
Jan  6 00:04:06 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | partition.c partition_CloseSwifotaPartition() 1188 | Update for partiton swifota done with return 0
Jan  6 00:04:06 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c BuildMetaData() 2057 | Image length: 69683259
Jan  6 00:04:06 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c BuildMetaData() 2059 | Logical block: 2, Physical block: 2
Jan  6 00:04:07 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteDwlStatus() 1742 | FW update download status stored.
Jan  6 00:04:07 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate T=main | pa_fwupdate_qmi.c pa_fwupdate_CloseSwifota() 2216 | Close SWIFOTA partition
Jan  6 00:04:07 swi-mdm9x28-wp user.info Legato:  INFO | powerManagerService[1179]/powerMgr T=main | le_pm.c OnClientDisconnect() 298 | Client pid 1131 disconnected.
Jan  6 00:04:07 swi-mdm9x28-wp user.warn Legato: -WRN- | powerManagerService[1179]/powerMgr T=main | le_pm.c OnClientDisconnect() 315 | Releasing wakeup source 'legato_FWUpdate_fwupdateDaemon' on behalf of fwupdateDaemon/1131.
Jan  6 00:04:07 swi-mdm9x28-wp user.info Legato:  INFO | powerManagerService[1179]/powerMgr T=main | le_pm.c OnClientDisconnect() 323 | Deleting wakeup source 'legato_FWUpdate_fwupdateDaemon' on behalf of pid 1131.
Jan  6 00:04:07 swi-mdm9x28-wp user.info Legato:  INFO | powerManagerService[1179]/powerMgr T=main | le_pm.c OnClientConnect() 270 | Connection from client fwupdateDaemon/1131
Jan  6 00:04:07 swi-mdm9x28-wp user.warn Legato: -WRN- | fwupdateDaemon[1131]/framework T=main | fdMonitor.c le_fdMonitor_Create() 449 | FD Monitor object name 'fwupdateDaemon.fwupdateDaemon.le_pm' truncated to 'fwupdateDaemon.fwupdateDaemon.l'.
Jan  6 00:04:07 swi-mdm9x28-wp user.info Legato:  INFO | powerManagerService[1179]/powerMgr T=main | le_pm.c le_pm_NewWakeupSource() 509 | Created new wakeup source 'legato_FWUpdate_fwupdateDaemon' for pid 1131.
Jan  6 00:04:07 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | partition.c partition_WriteMetaData() 2117 | MTD 6: Writing from CWE image 23
Jan  6 00:04:07 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_flash_mtd.c pa_flash_GetInfo() 231 | MTD 6 "swifota": size 4f40000 (nbBlk 317), writeSize 1000, eraseSize 40000
Jan  6 00:04:07 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | partition.c partition_WriteMetaData() 2170 | MTD 6: Writing meta data to peb 0
Jan  6 00:04:07 swi-mdm9x28-wp user.info Legato:  INFO | fwupdateDaemon[1131]/le_pa_fwupdate_singlesys T=main | pa_fwupdate_singlesys.c WriteDwlStatus() 1742 | FW update download status stored.
Error during installation: LE_FAULT
Jan  6 00:04:10 swi-mdm9x28-wp user.err Legato: =ERR= | fwupdateDaemon[1131]/fwupdateDaemon T=main | fwupdateServer.c le_fwupdate_InstallAndMarkGood() 492 |  !!! Error LE_FAULT
Jan  6 00:04:10 swi-mdm9x28-wp user.info Legato:  INFO | powerManagerService[1179]/powerMgr T=main | le_pm.c OnClientDisconnect() 298 | Client pid 1131 disconnected.
Jan  6 00:04:10 swi-mdm9x28-wp user.warn Legato: -WRN- | powerManagerService[1179]/powerMgr T=main | le_pm.c OnClientDisconnect() 315 | Releasing wakeup source 'legato_FWUpdate_fwupdateDaemon' on behalf of fwupdateDaemon/1131.
Jan  6 00:04:10 swi-mdm9x28-wp user.info Legato:  INFO | powerManagerService[1179]/powerMgr T=main | le_pm.c OnClientDisconnect() 323 | Deleting wakeup source 'legato_FWUpdate_fwupdateDaemon' on behalf of pid 1131.
Jan  6 00:04:10 swi-mdm9x28-wp user.info Legato:  INFO | supervisor[1031]/supervisor T=main | proc.c proc_SigChildHandler() 2079 | Process 'fwupdate@0' (PID: 2383) has exited with exit code 1.
Jan  6 00:04:12 swi-mdm9x28-wp user.warn Legato: -WRN- | supervisor[1031]/supervisor T=main | app.c app_SigChildHandler() 4066 | Process 'fwupdate@0' in app 'tools' faulted: Ignored.
Jan  6 00:04:12 swi-mdm9x28-wp user.info Legato:  INFO | supervisor[1031]/supervisor T=main | app.c app_StopComplete() 4753 | app 'tools' has stopped.
Jan  6 00:04:12 swi-mdm9x28-wp user.info Legato:  INFO | supervisor[1031]/supervisor T=main | apps.c DeactivateAppContainer() 374 | Application 'tools' has stopped.

Any ideas about this?

4

you seem use the old spk WP76xx_Release16_VERIZON.spk which is not for new memory, you can try new one “WP76xx_Release16.0.1_VERIZON.spk”

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

5

I did not realize i was not using the latest firmware, thanks.

Unfortunately, that did not fix the issue. The output is exactly the same.

6

Can you install legato application?
Can you just install the yocto or just the legato image?

7

I’m sorry, I’m not sure I understand.
Do you mean install onto the WP7611? I think legato is already installed on the modem. There is a legato folder in the base directory; however, if i run the app list command I do not see legato in the output.(I apologize, I don’t know a ton about this system)

As for my host board, maybe i could cross compile something.

Also it looks like a new release dropped yesterday. I’ll try looking at some of that documentation for help.

8

I mean try to download the components one by one
https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-release-16,-d-,1-components/

9

Well, i’ve tried installing the updated OS file linux-SWI9X07Y_02.37.10.02.cwe, but it does not appear to have fully worked?

It ran without error, but when it came back up, it seems to have lost one of the stored images and the new one does not appear the same as the others.

output from qmicli -d /dev/cdc-wdm0 -p /dev/cdc-wdm0 --dms-list-stored-images 
[/dev/cdc-wdm0] Device list of stored images retrieved:

	[0] Type:    'modem'
	    Maximum: '3'

		[modem0]
		Unique ID:     '00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00'
		Build ID:      ''
		Storage index: '0'
		Failure count: '0'

		[modem1]
		Unique ID:     '?_?'
		Build ID:      '02.37.00.00_?'
		Storage index: '2'
		Failure count: '0'

	[1] Type:    'pri'
	    Maximum: '50'

		[pri0]
		Unique ID:     '002.098_003'
		Build ID:      '02.37.00.00_ATT'

		[pri1]
		Unique ID:     '001.060_003'
		Build ID:      '02.37.03.00_SIERRA'

		>>>>>>>>>> [CURRENT] <<<<<<<<<<
		[pri2]
		Unique ID:     '002.104_001'
		Build ID:      '02.37.03.00_VERIZON'

As for installing the new legato image, I downloaded the file for “base legato system” and it came as a .tar.bz2. I passing it into the fwupdate and it did not work.

10

Fwupdate download .cwe or .spk file

11

I’ve tried doing fwupdate download with both linux-SWI9X07Y_02.37.10.02.cwe and WP76xx_Release16.0.1_VERIZON.spk. That is how I got the result in my previous message.

12

What is the ati3 and ati8 after you install the fw by fwupdate download?

13

I’m sorry, I’m not sure how to check those. Also, I’m still not sure if the firmware installed correctly.

14

You can ssh to the module and use “microcom /dev/ttyAT” to enter AT commands

15

Oh, I did not realize those were AT commands, my bad.


ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7611
Revision: SWI9X07Y_02.37.03.00 73df45 jenkins 2020/04/08 10:59:14
IMEI: 355882100198599
IMEI SV: 14
FSN: ZU151330110910
+GCAP: +CGSM

OK

ati8
Legato Ver: 19.11.2_4ad011d85a76309438be40fc19e7153a
Yocto Ver:  SWI9X07Y_02.37.10.02 2022-02-11_09:57:45
OS Ver: Linux version 3.18.140 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 PREEMPT Fri Feb 11 09:40:40 UTC 2022
LK Ver: SWI9X07Y_02.37.10.02
RootFS Ver: SWI9X07Y_02.37.10.02 2022-02-11_09:57:45
UserFS Ver: unknown
MCU Ver: unknown

OK
16

Then it seems to be installed, right?

17

Yeah, that looks like the modem has the updated firmware now. However, it is still not seeing my Verizon SIM card :frowning:

18

how about AT!IMPREF? and AT!UIMS?

19

Here is the output. It seems to know to try to use Verizon. Is it possible the problem is on the side of the modemmanager service?

!IMPREF: 
 preferred fw version:    02.37.03.00
 preferred carrier name:  VERIZON
 preferred config name:   VERIZON_002.104_001
 preferred subpri index:  000
 current fw version:      02.37.03.00
 current carrier name:    VERIZON
 current config name:     VERIZON_002.104_001
 current subpri index:    000

OK

!UIMS: 0

OK
20

what is the return of the followings?
AT+CMEE=1
AT+CPIN?
AT+CIMI
at+CCID?
AT!CUSTOM?