I am troubleshooting a WP7702 running Legato 21.05.0_2dabb8d054d3c0c9b5655d2326b279a1.
The issue appeared while I was trying to use /dev/ttyHS0 from a Linux application and changing the UART mapping with MAPUART/uartMode. I cannot confirm that the mapping change caused the failure, but the device now exhibits the following behavior:
The internal AT interface at /dev/smd8 is unusable. Opening it with microcom times out:
microcom: can't open '/dev/smd8': Connection timed out
uartMode get 1, uartMode get 2, and uartMode set 1 atCmds fail with:
diag: Unable to get remote processor info. Continuing with just the local processor
Internal error check logs for details.
Logs show repeated QMI initialization/service failures and timeouts.
With Legato running, the device reboots approximately every two to three minutes. The logs show a mandatory watchdog failure involving cellNetService, followed by a supervisor-triggered reboot. Stopping Legato prevents the observed reboot loop.
RAM usage immediately before a reboot did not indicate memory exhaustion.
Recovery attempts
Flashed WP77xx_Release15.1_VERIZON.spk. The problem persisted.
Tried swiflash -r and downloading reset.cwe directly with Windows FDT 2.1.2509.0. The reset image was rejected:
Primary error code: 77 - Failed in streaming download stage.
Secondary error code: 68 - Received incorrect response.
Device error code: 0x97 - Not allowed.
The device console reported:
not allowed to write UAPP partition
Following the workaround discussed in the WP77xx Release 12 forum thread, attempted a direct USER1 erase with:
/usr/sbin/flash_erase /dev/mtd16 0 0
I verified the partition beforehand:
mtd16: 08300000 00040000 "userapp"
Legato and psmd were stopped, although /etc and /data overlays remained mounted because normal unmount attempts returned “Device or resource busy.”
After reboot, I observed reset-related behavior, including Dropbear regenerating a host key, but the original instability persisted. I do not yet have independent confirmation that all intended user state was cleared.
Questions
What is the supported replacement for swiflash -r on WP77xx firmware that rejects reset.cwe? Is there an updated reset image or documented recovery procedure?
Another thread suggests using an unsandboxed Legato app to clear userapp. What exact operations should that app perform, and how should it safely handle the active USER1 mounts? Is there a reference implementation?
Where is persistent configuration changed by AT!MAPUART stored? Does it survive both a firmware reflash and USER1 erase?
Can UART mapping or the relevant modem configuration be restored through USB/download mode when AT commands and uartMode are unavailable, without erasing calibration data or device identity?
What diagnostics would help distinguish a persistent configuration problem from a modem firmware/startup failure?
A supported, documented recovery path is important here: reflashing the firmware has not restored a usable baseline, and the existing reset mechanism is explicitly rejected by the bootloader.
the method of reset.cwe has security hole. This method cannot be used anymore since R12.
you can try with system() api to call those commands in an unsandboxed legato application.
this should be stored inside the NV storgae of modem firmware as this is part of the modem AT function. You can try with a OK module and see if upgrading firmware will reset the AT!MAPAURT parameter.
normally you will not have any method to erase calibration data and device identity.
you can see here on how to ensure the legato supervisor loads the legato image from the legato RO partition
BTW, does the latest firmware solve the reset problem caused by legato image?
I’ll have follow-up questions, but I need an explicit answer to this one because it has serious production implications:
Does Sierra/Semtech currently provide a supported tool or procedure to return a WP7702 to its factory-shipped software and configuration state, while preserving calibration data and device identity—even when AT commands are unresponsive?
Does Sierra currently provide a supported tool or procedure to return a WP7702 to its factory-shipped software and configuration state, while preserving calibration data and device identity—even when AT commands are unresponsive?
Please answer the original question, before any other questions are asked.
Do you mean the usb AT port is not responding?
AT commands sent through the Host USB modem endpoint,(IE: COM8 for windows or /dev/tty something for Linux), receive no response.
The internal AT interface, /dev/smd8, times out when opened.
Legato AT command APIs fail
There is no way to send AT commands
How can you see the device log if the usb is not working?
There is normally two minutes after boot before the Legato initiate a reboot. In that time I can interact with the console. The logs show modem/QMI communication failures followed by a mandatory watchdog failure involving cellNetService. The Legato watchdog exits, and the supervisor initiates a reboot. Stopping Legato prevents the repeated reboots, but AT and modem communication remain unresponsive (both before and after the legato stop command).
I have bricked a second device. All I need to do is run:
```
root@p0xx-119-nosn:~# uartMode set 1 app
diag: Unable to get remote processor info. Continuing with just the local processor
UART1 will be set to ‘app’ after the next reboot.
root@p0xx-119-nosn:~# reboot
```
After that AT commands don’t work and the device will only stay powered on for 5 minutes before rebooting (see original symptoms).
```
root@p0xx-119-nosn:~# microcom /dev/smd8
root@p0xx-119-nosn:~#
root@p0xx-119-nosn:~# uartMode set 1 atCmds
diag: Unable to get remote processor info. Continuing with just the local processor
Internal error check logs for details.
```
the logs are just filled with QMI/At commands errors and eventually the watchdog errors.
At a bare minimum, I need a way to undo uartMode set 1 app. Flashing the device does not fix this problem.
I wonder if you use at!mapuart instead of uartMode command, will it still have problem?
BTW, I don’t quite see problem with “uartMode set 1 app”, after reboot, it can show the following:
root@fx30:~# legato version
21.05.0.54b96444_0a6e18078edde5151619cb964564694d
root@fx30:~# uartMode get 1
diag: Unable to get remote processor info. Continuing with just the local processor
UART1 is available for use by Linux applications.
root@fx30:~# microcom /dev/smd8
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7702
Revision: SWI9X06Y_02.36.08.09 c094f4 jenkins 2022/06/24 03:14:28
IMEI: 352653090612435
IMEI SV: 8
FSN: VU213431212345
+GCAP: +CGSM
OK