after AT!RMARESET=1
the at+cfun=1 command returns
+CME ERROR: operation not supported
what can i do ?
after AT!RMARESET=1
the at+cfun=1 command returns
+CME ERROR: operation not supported
what can i do ?
Hi @frini, some factor is preventing the module from going online. Could you check AT!PCINFO? response, to determine what vote is holding the device in LPM? Potential reasons include voltage or temperature out of range, modem software mismatched with configuration, and hardware switch (W_DISABLE).
Thanks,
Ryan
Hi Ryan,
Thanks for your help.
the AT!PCIFNO returns the following:
State: Low Power Mode
LPM voters - Temp:0, Volt:0, User:0, W_DISABLE:0, IMSWITCH:1, BIOS:0, LWM2M:0, OMADM:0, FOTA:0
LPM persistence - None
OK
what does it mean ?
I checked in the forum for similar answers and i also checked AT!IMPREF?
!IMPREF:
preferred fw version: 00.00.00.00
preferred carrier name: NONE
preferred config name: NONE_000.000_000
current fw version: 02.16.06.00
current carrier name: GENERIC
current config name: GENERIC_001.013_000
fw version mismatch
carrier name mismatch
config name mismatch
OK
and also at!image?1
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
FW 1 GOOD 127 0 0 001.028_001 02.16.06.00_GENERIC
FW 2 EMPTY 0 0 0
FW 3 GOOD 127 0 0 001.026_000 02.16.06.00_ATT
Max FW images: 3
Active FW image is at slot 255
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID
Max PRI images: 50
OK
It seem to have a missmatch. but AT!IMPREF=“GENERIC” results in error (after typing the password)
can the parameter be updated from the linux shell (ssh)?
Thanks @frini. For image preference, could you take a look at this thread?:
The one-click tools for Windows, distributed by Sierra, should set the preference. If re-applying the modem firmware image doesn’t help, could you provide a few more details?
ATI ->I’m just interested in the FW version, from this response
AT!PRIID?
AT!CUSTOM?
Thanks,
Ryan
The windows tool doesn’t work (it did before the problem occurred) . it writes:
Primary error code: 51 - Failed to switch device to BOOT&HOLD mode.
Secondary error code: 201 - Failed to switch device to QDL mode.
Device error code: 0x0 - Unknown device error code.
ati:
Revision: SWI9X06Y_02.16.06.00 7605a6 jenkins 2018/06/20 17:56:12
AT!PRIID?
PRI Part Number: 5501024
Revision: 000.005
Customer: DevKit
Carrier PRI: None
OK
AT!CUSTOM?
!CUSTOM:
GPSENABLE 0x01
GPSLPM 0x01
IPV6ENABLE 0x01
UIM2ENABLE 0x01
SIMLPM 0x01
USBSERIALENABLE 0x01
SINGLEAPNSWITCH 0x01
TXONINDICATION 0x01
HSICENABLE 0x01
BOOTQUIETDISABLE 0x01
SCRUBEN 0x01
EXTGPSLNAEN 0x01
OK
I was on the way to install the SDK and try swiflash but i have restart the PC and change something in the boot of the PC and unforchantly it is a remote PC and i will have access to it only next week.
So, until than only at commands can be used…
Success!!
I managed to manually install the FW again by cmd:
C:\Users\xxx\AppData\Local\Temp\RarSFX0>fdt2 -f WP77xx_Release9.1_RC5_GENERIC.spk
FDT version: 1.0.1806.0
Awaiting suitable port or adapter …
Switching to boot & hold mode …
Disabling selective suspend …
Awaiting DM port …
Switching to boot & hold mode …
Disabling selective suspend …
Awaiting port removal …
Awaiting download port …
Switching to streaming mode …
Downloading images …
Writing image -
Flashing image /
the device seems to work now. I am still not able to attach to the NW but its a progress.
Thanks a lot for your help