Exception when trying to execute AT^SJAM=4 | Telit Cinterion IoT Developer Community
July 23, 2021 - 1:31pm, 4838 views
Hi,
after i deleted a Midlet with OTAP START:delete messages, the module is in a very weird state.
Whenever i try to call AT^SJAM=4 nothing happens but on the SYSTEM.OUT i get the following exception:
java.lang.NullPointerException: 0
- com.cinterion.ams.AmsNativeCommand.execute(), bci=562
- com.cinterion.ams.AmsNativeExtension$NativeCommandListenerThread.run(), bci=9
Is it possible that this comes from using OTAP delete command?
(I never had to use this before..)
ati1
Cinterion
ELS61-E R2
REVISION 02.000
A-REVISION 01.000.02
Best Regards,
Andy
Hello and happy new year,
Yes, there is a long delay after "Erasing flash memory". 5 minutes exactly and then the error. No progress in the update state bar.
Best regards,
Daniel
Happy New year,
It seems that there might a communication problem if the deletion process is not even started. Please make sure that you use the correct interface and the module replies to AT commands on that interface. Please try USB modem interface (check in Device Manager if the drivers are installed) and in case of problems try ASC0 (will take much more time than USB). If for any reason you are unsuccessful please also try the manual way.
Regards,
Bartłomiej
Hello,
The swup.log is:
[2022-01-04 12:54:30]
[2022-01-04 12:54:32]OpenAttachedFile: No. 13 file not exist
[2022-01-04 12:54:32]Disabling userware autostart...
[2022-01-04 12:54:32]Checking module Character Set ('GSM' or 'UCS2') ...
[2022-01-04 12:54:50]Restoring module state...
[2022-01-04 12:54:59]Initializing firmware update...
[2022-01-04 12:55:01]Waiting for re-enumerated USB port...
[2022-01-04 12:55:27]Warning: Timeout waiting for 1st ACK before swup start!
[2022-01-04 12:55:27]Erasing flash memory (this can take a couple of minutes without visible progress)...
[2022-01-04 13:00:27]ERROR: Timeout waiting for response after block no. 0!
[2022-01-04 13:00:27]ERROR: Firmware update failed!
[2022-01-04 13:00:27]Parsing configuration file...
[2022-01-04 13:00:27]Restoring module state...
[2022-01-04 13:00:27]Module update failed
I tried with gWinSwup with all ports and I tried the manual way, but not works.
Regards
And what is the result if you try the manual way, i.e. load the usf file to the module and send AT^SFDL=2 command (please do it on ASC0 interface to make sure that you get all the aoutput)?
Appears written: ^SYSINFO: 200 and then the Cinterion reboots. And the response of at^scfg is:
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/****/ASC1","std"
^SCFG: "Gpio/****/DAI","gpio"
^SCFG: "Gpio/****/DCD0","std"
^SCFG: "Gpio/****/DSR0","std"
^SCFG: "Gpio/****/DTR0","std"
^SCFG: "Gpio/****/FSR","gpio"
^SCFG: "Gpio/****/PULSE","gpio"
^SCFG: "Gpio/****/PWM","gpio"
^SCFG: "Gpio/****/RING0","gpio"
^SCFG: "Gpio/****/SPI","rsv"
^SCFG: "Gpio/****/SYNC","gpio"
^SCFG: "Gpio/****/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","100"
^SCFG: "Userware/DebugInterface","0.0.0.0","0.0.0.0","0"
^SCFG: "Userware/DebugMode","on"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","asc0",,,,"off"
^SCFG: "Userware/Watchdog","1"
^SCFG: "MEopMode/ExpectDTR","current"
^SCFG: "MEopMode/ExpectDTR","powerup"
I don´t know what are the two last lines
^SYSINFO: 200 is because JRC MIDlet is not started. And it's not because "Userware/Autostart" is set to "0". Please set to 1. Please check if JRC is installed with AT^SJAM=4. To update JRC manually load new JRC (jar and jad) to the module's A drive and install as any other MIDlet with AT^SJAM (if it's running you need to stop it first).
My previous question was about what the module outputs if you upload the firmware file (usf) to the A drive and execute AT^SFDL=2 on serial interface.
Hello,
if I put at^sjaM=4, the console crashes and I can´t see the response.
I put "Userware/Autostart" to 1.
I have stopped the JRC and installed it again manually
And when I enter "at^sfdl=2", the module reboots and does nothing else. The at^scfg after reboot is:
^SJAM: "a:/JRC-1.62.01.jad","Java Remote Control MIDlet Suite","Cinterion","1.62.01",1,1
at^sjaM=5 works, but at^sjam=4 blocks the console
Regards
When I put "at^sfdl=2" the console puts "OK" and then the module reboots but nothing happens. If I put "at^sjam=4", the console crashes
Regards
Did you upload the firmware file with usf extension to the module before sending the command? If you send the command on ASC0 interface you have a chance to see the bootloader output to make sure that the firmware is updated. If it is and SJAM=4 still fails it seems that you have to use gWinSwup with the flag to recover file system. This is the only chance to fix the problem. If it fails as before you will not fix it. You may contact your supplier or local Thales office with it.
Regards,
Bartłomiej