ELS61-E R2 - FFS failure | Telit Cinterion IoT Developer Community
April 20, 2023 - 12:21pm, 143 views
Hello,
We already have several cases, where ELS61 R2 are not working.
An attempt to reinstall the firmware failed. els61-e_rev02.000_arn01.000.05 as well 06 and 07 (gwinswup.exe) they are not of any help.
gwinswup log:
[2023-04-20 09:33:46]
[2023-04-20 09:33:49]OpenAttachedFile: No. 13 file not exist
[2023-04-20 09:33:49]Disabling userware autostart...
[2023-04-20 09:33:49]Checking module Character Set ('GSM' or 'UCS2') ...
[2023-04-20 09:34:07]Restoring module state...
[2023-04-20 09:34:15]Initializing firmware update...
[2023-04-20 09:34:18]Waiting for re-enumerated USB port...
[2023-04-20 09:35:51]Warning: Timeout waiting for 1st ACK before swup start!
[2023-04-20 09:35:51]Erasing flash memory (this can take a couple of minutes without visible progress)...
[2023-04-20 09:36:06]ERROR: Unexpected or fatal response (0x0d) to block 0!
[2023-04-20 09:36:06]ERROR: Firmware update failed!
[2023-04-20 09:36:06]Parsing configuration file...
[2023-04-20 09:36:06]Restoring module state...
AT^SJAM=4 response is empty (OK)
Neither our nor the JRC MIDlet is apparently installed / available.
Does anyone have similar experiences or a solution? Thanks.
at^scfg?
at^scfg?
^SCFG: "MEopMode/Comp1",""
^SCFG: "Gpio/port/MCLK","GPIO4"
^SCFG: "Serial/Ifc","0"
^SCFG: "RemoteWakeUp/Event/USB","none"
^SCFG: "RemoteWakeUp/Ports","current"
^SCFG: "RemoteWakeUp/Ports","powerup"
^SCFG: "Audio/Loop","0"
^SCFG: "Call/ECC","0"
^SCFG: "Call/Speech/Codec","0"
^SCFG: "Gpio/mode/ASC1","std"
^SCFG: "Gpio/mode/DAI","gpio"
^SCFG: "Gpio/mode/DCD0","gpio"
^SCFG: "Gpio/mode/DSR0","gpio"
^SCFG: "Gpio/mode/DTR0","gpio"
^SCFG: "Gpio/mode/FSR","gpio"
^SCFG: "Gpio/mode/PULSE","gpio"
^SCFG: "Gpio/mode/PWM","gpio"
^SCFG: "Gpio/mode/RING0","gpio"
^SCFG: "Gpio/mode/SPI","rsv"
^SCFG: "Gpio/mode/SYNC","std"
^SCFG: "Gpio/mode/MCLK","gpio"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","ELS61-E R2"
^SCFG: "MEopMode/SoR","off"
^SCFG: "MEopMode/CregRoam","0"
^SCFG: "MeOpMode/SRPOM","0"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEShutdown/sVsup/threshold","0","0"
^SCFG: "Radio/Band/2G","0x00000014"
^SCFG: "Radio/Band/3G","0x00000081"
^SCFG: "Radio/Band/4G","0x08080085"
^SCFG: "Radio/Mtpl/2G","0"
^SCFG: "Radio/Mtpl/3G","0"
^SCFG: "Radio/Mtpl/4G","0"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "Serial/Interface/Allocation","1","1"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","005B","Cinterion Wireless Modules","ELSx",""
^SCFG: "Tcp/IRT","3"
^SCFG: "Tcp/MR","10"
^SCFG: "Tcp/OT","6000"
^SCFG: "Tcp/WithURCs","on"
^SCFG: "Tcp/TLS/Version","MIN","***"
^SCFG: "Trace/Syslog/OTAP","0"
^SCFG: "Urc/Ringline","local"
^SCFG: "Urc/Ringline/ActiveTime","2"
^SCFG: "Userware/Autostart","0"
^SCFG: "Userware/Autostart/Delay","0"
^SCFG: "Userware/DebugInterface","0.0.0.0","0.0.0.0","0"
^SCFG: "Userware/DebugMode","off"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","null",,,,"off"
^SCFG: "Userware/Watchdog","1"
^SCFG: "MEopMode/ExpectDTR","current"
^SCFG: "MEopMode/ExpectDTR","powerup"
OK
Hello,
Could you write what are the symptoms of the problem?
Is the module still responsive after that failed firmware update?
Is it possible to install the missing MIDlets?
BR,
Bartłomiej
Hello,
We have a custom java software running on the module. Our software restarts the module using the at-command "at+cfun=1,1". At some modules the JRC doesn't exist anymore on the file system after restarting and so we get ^SYSINFO=200. About 10% of the ELS61 loosing the JRC Midlet suite get stuck in a boot loop whit ^SYSINFO=202, because of the mssing JRC.
We already implemented a 15s startup delay in our custom java software to give the module time to initialize.
Do you have any idea why this is happening?
Thank you!
BR,
Philipp
We also have the same java application running on the EHS5 and there we don't have this problem. Only happening on the ELS61-E-R2
Hello,
at+cfun=1,1 is considered to be a safe way of module reboot. So it should not cause any risks.
So, maybe please take a closer look at what your app is doing at the moment of sending this command.
If the app is properly written, the standard system system shutdown procedure should also call destroyApp() in your app. Please also check what is done in this method.
Also make sure that 'Oracle-MIDlet-Autostart:' in your app is set to a value greater than 1?
^SYSINFO: 200 could be thrown if there is no JRC as it means that it was not attempted to be started.
^SYSINFO: 202 means that JRC start was tried eight times, but failed and the module was restarted with ^SYSINFO: 201 URC.
Is it possible to list the installed applications and if JRC is not on the list is it possible to install it?
Best regards,
Bartłomiej