failure to run JAD/JAR file (ERROR: Incorrect parameters) | Telit Cinterion IoT Developer Community
February 27, 2017 - 11:04pm, 6618 views
While debugging/building I tried to use the Eclipse/Gemalto
tools to load a JAR/JAD file to an EHS6 and run/remotely-
debug it. The modules failes to load from the remote
debugger:
Waiting for debug device registration of "IMP_NG_EHS5_REMOTE"...
Passing control to external device emulator...
Installing suite from: http://192.168.244.2:50647/Gem.jad
*** Error ***
Failed to execute MIDlet suite
End of debug session. Emulator is closed!
and if I try to load it manually, I get the following
error:
at^sjam=5
^SJAM: "a:/JRC-1.56.49.jad","Java Remote Control MIDlet Suite","Cinterion","1.56.49",1
OK
at^sjam=4
^SJAM: "a:/HelloWorld.jad","HelloWorld MIDlet Suite","Gemalto M2M GmbH","1.0.0",0,3305,0
^SJAM: "a:/JRC-1.56.49.jad","Java Remote Control MIDlet Suite","Cinterion","1.56.49",1,788015,0
OK
at+cmee=2
OK
at^sjam=0,"a:/Gem.jad",
+CME ERROR: Incorrect parameters
at^sjam=4
^SJAM: "a:/JRC-1.56.49.jad","Java Remote Control MIDlet Suite","Cinterion","1.56.49",1,788015,0
OK
The rub is if I copy the JAR/JAD files to another ****m (an EHS5)
the application loads and runs without error.
Any suggestions as to how to trouble shoot it problem?
(I was trying to reflash the EHS6 to perhaps *****
whatever's set wrong, but the installer fails as it's
trying to ***** the flash.
More data:
ati1
Cinterion
EHS6
REVISION 03.001
A-REVISION 00.000.49
OK
at^scfg?
^SCFG: "Audio/Loop","0"
^SCFG: "Call/ECC","0"
^SCFG: "Call/Speech/Codec","0"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Gpio/****/ASC1","rsv"
^SCFG: "Gpio/****/DAI","gpio"
^SCFG: "Gpio/****/DCD0","gpio"
^SCFG: "Gpio/****/DSR0","rsv"
^SCFG: "Gpio/****/DTR0","gpio"
^SCFG: "Gpio/****/FSR","gpio"
^SCFG: "Gpio/****/HSIC","rsv"
^SCFG: "Gpio/****/PULSE","gpio"
^SCFG: "Gpio/****/PWM","gpio"
^SCFG: "Gpio/****/RING0","gpio"
^SCFG: "Gpio/****/SPI","std"
^SCFG: "Gpio/****/SYNC","gpio"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","EHS6"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEShutdown/sVsup/threshold","0","0"
^SCFG: "MEopMode/CFUN","0","1"
^SCFG: "MEopMode/Comp1",""
^SCFG: "MEopMode/ExpectDTR","current"
^SCFG: "MEopMode/ExpectDTR","powerup"
^SCFG: "MEopMode/SoR","off"
^SCFG: "Radio/Band","511"
^SCFG: "Radio/Mtpl","0"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "Serial/Interface/Allocation","0","0"
^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","192.168.244.1","192.168.244.2","0"
^SCFG: "Userware/DebugMode","on"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","usb3",,,,"off"
^SCFG: "Userware/Watchdog","1"
OK
I'd start from what I've written in the previous post. And the next question would be - has it happened again after you have fixed it. If so I'd ask how frequently does it happen. Generally such scenario is possible but it is rather not likely to happen. And maybe it will never happen again in your case. Only if it does you should wonder why. At this point it is hard to say what went wrong. The error message should point your attention first to the contents of the jad file and manifest file inside the jar.
The character set is default and it should not cause any problems.
Regards,
Bartłomiej
The problem turns out to be alpha-numeric characters in the MIDlet
version string: 0.0.1 is "valid", but 0.0.1a is not (and causes the
"incorrect parameters" load error.
Hello,
So it's solved. Great!
For those who may read this thread - the version numbering convention is described in the IMP-NG API as follows:
Version Numbering
Version numbers have the format Major.Minor[.Micro] (X.X[.X]), where the .Micro portion MAY be omitted. (If the .Micro portion is not omitted, then it defaults to zero). In addition, each portion of the version number is allowed a maximum of two decimal digits (i.e., 0-99). Version numbers are described in the the Java(TM) Product Versioning Specification http://java.sun.com/products/jdk/1.2/docs/guide/versioning/spec/Versioni....
For example, 1.0.0 can be used to specify the first version of a MIDlet suite. For each portion of the version number, leading zeros are not significant. For example, 08 is equivalent to 8. Also, 1.0 is equivalent to 1.0.0. However, 1.1 is equivalent to 1.1.0, and not 1.0.1.
A missing MIDlet-Version tag is assumed to be 0.0.0, which means that any non-zero version number is considered as a newer version of the MIDlet suite.
Regards,
Bartłomiej