Exception when trying to execute AT^SJAM=4 | Thales IoT Developer Community
July 23, 2021 - 1:31pm, 5815 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
Hi Andy,
In general it's possible to delete MIDlets via OTAP delete commands and you should not experience any issues due to this procedure. Is it possible that your device experienced a power cut during this OTAP procedure?
What kind of Java application did your remove - was it a custom Java application or the JRC MIDlet? Was the URL pointing to module's FFS or was it a network resource? Were there any additional MIDlets installed on your module before the OTAP delete was triggered?
BR,
Ida
Hello Ida,
Power cut could be possible but i don't know, because i've done the OTAP operation remote.
No, it was a midlet of our own which was installed on a:/.
Yes there was a second app from us installed on the module.
Best Regards,
Andy
Hi Andy,
I'm afraid we have no previous reports of any similar issues to the one you are experiencing and I also couldn't reproduce it on my setup with simple OTAP deletes procedures.
What I can recommend is to re-flash your module's firmware to restore it to proper configuration. I shared the update utility/file with you via email.
BR,
Ida
Hello,
I´ve the same problem for ELS61. at^sjam=5 works, but if i write at^sjam=4, the response is:
java.lang.NullPointerException
- java.lang.System.throwNullPointerException(), bci=4
- com.cinterion.ams.AmsNativeExtension$NativeCommandListenerThread.run(), bci=9
Can you help me, please?
Best regards
Daniel
Hello,
Did you do anything special before this happened? Did you notice any power outage during installation/uninstallation or is the power cut frequently during the operation?
The exception happens on reading the installed applications which should normally never happen. I think that it could potentially mean some problem with data integrity. So I would try the same as suggested by Ida - to perform firmware reinstallation with gWinSwup. If it doesn't help I'd also check "Recovery File System" flag before starting.
Best regards,
Bartłomiej
Hi ,
i´ve tried to reinstall the firmware with gWinSwup, but it doesn´t works.
The log of gWinSwup is:
[2021-12-20 11:28:37]
[2021-12-20 11:28:39]OpenAttachedFile: No. 13 file not exist
[2021-12-20 11:28:39]Disabling userware autostart...
[2021-12-20 11:28:39]Checking module Character Set ('GSM' or 'UCS2') ...
[2021-12-20 11:28:57]Restoring module state...
[2021-12-20 11:29:05]Initializing firmware update...
[2021-12-20 11:29:07]Waiting for re-enumerated USB port...
[2021-12-20 11:29:33]Warning: Timeout waiting for 1st ACK before swup start!
[2021-12-20 11:29:33]Erasing flash memory (this can take a couple of minutes without visible progress)...
[2021-12-20 11:34:33]ERROR: Timeout waiting for response after block no. 0!
[2021-12-20 11:34:33]ERROR: Firmware update failed!
[2021-12-20 11:34:33]Parsing configuration file...
[2021-12-20 11:34:33]Restoring module state...
[2021-12-20 11:34:33]Module update failed
I´ve check "Recovery File System" and i´ve tried to check the others too, but nothing works
Best regards,
Daniel
and 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/****/ASC1","std"
^SCFG: "Gpio/****/DAI","gpio"
^SCFG: "Gpio/****/DCD0","gpio"
^SCFG: "Gpio/****/DSR0","gpio"
^SCFG: "Gpio/****/DTR0","gpio"
^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","off"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","usb1",,,,"off"
^SCFG: "Userware/Watchdog","1"
^SCFG: "MEopMode/ExpectDTR","current"
^SCFG: "MEopMode/ExpectDTR","powerup"
Hello,
What firmware version were you trying to install on the module? Are you sure that it was the proper one? Which interface was used for the update?
Based on the log it seems that the old firmware was deleted and the new one not installed. In such case the module would boot in the firmware upload ****. In such a case you still have a chance to install the firmware. You need to check the flag "No Firmware in Module". For the first 10 seconds after booting the firmware upload is possible on ASC0 interface. If it will not start the USB should be enumerated and you should be able to start the update on USB. Please try.
Best regards,
Bartłomiej
Hello,
I don´t know the firmware version. My ATI1 is:
ati1
Cinterion
ELS61-E R2
REVISION 02.000
A-REVISION 01.000.02
I use "els61-e_rev02.000_arn01.000.06_gwinswup.exe" file to update
I can install the "JRC-1.62.08.jad" file with at commands if it can helps
Best regards,
Daniel
Hello,
The firmware version is correct.
So, as I understand the old firmware was not deleted and the module boots normally.
I thought it was because there is a long delay after "Erasing flash memory" and before the error.
Please make sure that you are using ASC0 or USB modem interface and that the module can reply to AT commands on that interface (for instance there is no system.out redirected) and try again. I believe that it should work.
It is also possible to upload usf file to the module's file system and use AT^SFDL=2 command to update the firmware from the local flash. JRC can be updated as a standard MIDlet.
But it would be better to use gWinSwup with the "Recovery File System" flag.
Regards,
Bartłomiej
Pages