Concept Board Jar Jad Sjam freeze | Telit Cinterion IoT Developer Community
June 7, 2016 - 4:34pm, 7532 views
Dears,
I try to install a jar/jad code on EHS6 modem.
Operations :
1) Placing jar & jad using a:/module tool with USB cable
2) Installation with at^sjam=0,"a:/app.jad",""
3) Waiting and checking installed app with at^sjam=4
Firstly, working on EHS6T, everything is ok !!
Using the same jar/jad file on concept board, 1) is ok. On step 2) the command terminal freeze and no "ok" message appears, no more AT response, ... 30seconds later, I manually reboot and check installed app with step 3) but I only see jrc app...
Last, for our application I realized a complete PCB. USB connection OK, PSU ok, modem startup OK (Vcore 1,8V ok).
Step 1) OK but again freezing on step 2).
I see on step 2) the consumption of the PCB goes from 0,4W to 0,6W during the 5 to 10 first seconds of freezing.
Maybe configuration problem (scfg ?) ?
Or an hardware limitation ?
Thanks for your help,
Hello,
This is quite mysterious. Can you think of any relation between the modules on the the concept board and your board?
Have you checked other MIDlet? It doesn't seem as configuration problem but you could compare AT^SCFG outputs. Please paste also ATI1 replies.
How about the power source - please check AT^SBV output. Is this MIDlet somehow special, extremely big etc.? Is there a free space on the file system?
BR,
Bartłomiej
Hello Bartłomiej,
Thanks for your answer.
It seems to work with HelloWorld.jar/jad.
My jadr is 440ko, jad 1,5k.
I'm going to investigate your suggestion and tell more.
Free space is much higher than my jar/jad.
I used a basic jad with my jar and the modem freeze again.
I seems to come from the jar. The same jar working on terminal EHS6T.
Investiations continue...
This is really strange. Please try to compare the firmware versions on the modules (ATI1). You might also compare AT^SCFG? outputs.
Here is the outputs on one "failing jar install"modem.
ATI1
Cinterion
EHS6
REVISION 02.000
A-REVISION 00.000.03
at^scfg?
^SCFG: "Call/ECC","0"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Gpio/mode/ASC1","std"
^SCFG: "Gpio/mode/DAI","gpio"
^SCFG: "Gpio/mode/DCD0","std"
^SCFG: "Gpio/mode/DSR0","std"
^SCFG: "Gpio/mode/DTR0","std"
^SCFG: "Gpio/mode/FSR","gpio"
^SCFG: "Gpio/mode/HSIC","rsv"
^SCFG: "Gpio/mode/PULSE","gpio"
^SCFG: "Gpio/mode/PWM","gpio"
^SCFG: "Gpio/mode/RING0","std"
^SCFG: "Gpio/mode/SPI","rsv"
^SCFG: "Gpio/mode/SYNC","std"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","EHS6"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEopMode/SoR","off"
^SCFG: "Radio/Band","511"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "Serial/Interface/Allocation","1","1"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","0058","Cinterion Wireless Modules","EHx",""
^SCFG: "Tcp/IRT","3"
^SCFG: "Tcp/MR","10"
^SCFG: "Tcp/OT","6000"
^SCFG: "Tcp/WithURCs","on"
^SCFG: "Trace/Syslog/Otap","0"
^SCFG: "URC/Ringline","local"
^SCFG: "URC/Ringline/ActiveTime","2"
^SCFG: "Userware/Autostart","1"
^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"
Difference config are highlight
On the "not failing" terminal EHS6T :
ati1
Cinterion
EHS6
REVISION 02.000
A-REVISION 00.000.03
OK
at^scfg?
^SCFG: "Call/ECC","0"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Gpio/mode/ASC1","std"
^SCFG: "Gpio/mode/DAI","gpio"
^SCFG: "Gpio/mode/DCD0","std"
^SCFG: "Gpio/mode/DSR0","std"
^SCFG: "Gpio/mode/DTR0","std"
^SCFG: "Gpio/mode/FSR","gpio"
^SCFG: "Gpio/mode/HSIC","rsv"
^SCFG: "Gpio/mode/PULSE","gpio"
^SCFG: "Gpio/mode/PWM","gpio"
^SCFG: "Gpio/mode/RING0","std"
^SCFG: "Gpio/mode/SPI","rsv"
^SCFG: "Gpio/mode/SYNC","std"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","EHS6"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEopMode/SoR","off"
^SCFG: "Radio/Band","511"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "Serial/Interface/Allocation","1","1"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","0058","Cinterion Wireless Modules","EHx",""
^SCFG: "Tcp/IRT","6"
^SCFG: "Tcp/MR","10"
^SCFG: "Tcp/OT","60"
^SCFG: "Tcp/WithURCs","on"
^SCFG: "Trace/Syslog/Otap","0"
^SCFG: "URC/Ringline","local"
^SCFG: "URC/Ringline/ActiveTime","2"
^SCFG: "Userware/Autostart","1"
^SCFG: "Userware/Autostart/Delay","300"
^SCFG: "Userware/DebugInterface","0.0.0.0","0.0.0.0","0"
^SCFG: "Userware/DebugMode","off"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","asc0",,,,"off"
^SCFG: "Userware/Watchdog","1"
Hello,
These differences should have nothing to do with MIDlet installation. The firmware is quite old but this also should not matter especially that there is the same version on all modules. But as it is an old version you should try to update. How about the power supply - have you checked this?
On the other hand you could also try to change anything in the MIDlet to change it's size a little bit and check if it changes anything. Are you sure that you have used the same jar and jad files on the first module or maybe it was some other build? Maybe rebuilding the MIDlet would help.
Is there anything else on the flash file system? Is it possible to load some files there and remove them? Have any other MIDlets been installed before? Does the module reply on other interfaces? How about if you hit "enter" while there is no answer?
Regards,
Bartłomiej
Hello Bartłomiej,
No other midlet installed than jrc.
AT^SBV give 3679.
I'm sure it's the same jad & jar.
We also imagined to work on jar size. We realized tests and there seems to be two combined problems...
Our original 450ko jar, without SIM card but with "MIDlet-Install-Notify: ..." on the jad, at^sjam 0 freeze.
Our original 450ko jar, without SIM card but without "MIDlet-Install-Notify: ..." on the jad, at^sjam 0 freeze.
BUT
A reduced 18ko jar, without SIM card but with "MIDlet-Install-Notify: ..." on the jad, at^sjam 0 freeze.
A reduced 18ko jar, without SIM card but without "MIDlet-Install-Notify: ..." on the jad, at^sjam 0 error.
I can imagine that without SIM card, Install notification couldn't successed => freeze. So it could explain a part of the problem.
Can you tell me what is doing the EHS6 with the jar when installing it with sjam 0 ?
Only copying ? Executing anything from the jar ? Checking things inside the jar ?
Wow, it seem to work with SIM card...
Hello,
So it's going more complicated. The behaviour connected with MIDlet-Install-Notify parameter is not what you could expect. There is another parameter that could be used for the notification: NotifyURL - the question would be if you don't have it in your jad file.
But as we have here some unexpected and so far unexplained behaviour which seem to have something to do with the software now I recommend updating the modules to the latest release 2 firmware (or updating to the release 3) before further analysis.
There is a great chance that the problem will not exist in the latest release.
During the installation the files are copied to the hidden space of the flash file system but there is also some verification of the parameters from jad file and manifest inside the jar file. It is also checked if the installed application is the update for the already installed. As you have already discovered the notification is also sent.
Regards,
Bartłomiej
Pages