BGS5T JRC crashes after OTAP | Telit Cinterion IoT Developer Community
October 25, 2019 - 3:23pm, 2379 views
Hello,
I updated my program with OTAP and after that it become unresponsive. Today I went to the field to check what is happening and I found that that JRC won't run anyomre. I deleted my own MIDlet but JRC still crashes. Error output is this:
java.lang.NoClassDefFoundError: com/cinterion/jrc/JRC_LogManager
- cM.a(), bci=0
- com.cinterion.jrc.JRC_Midlet.<init>(), bci=12
- java.lang.Class.newInstance(), bci=0
- com.sun.midp.main.CldcMIDletLoader.newInstance(), bci=69
- com.sun.midp.midlet.MIDletStateHandler.createMIDlet(), bci=63
- com.sun.midp.midlet.MIDletStateHandler.createAndRegisterMIDlet(), bci=17
- com.sun.midp.midlet.MIDletStateHandler.startSuite(), bci=24
- com.sun.midp.main.AbstractMIDletSuiteLoader.startSuite(), bci=38
- com.sun.midp.main.CldcMIDletSuiteLoader.startSuite(), bci=5
- com.sun.midp.main.AbstractMIDletSuiteLoader.runMIDletSuite(), bci=134
- com.sun.midp.main.AppIsolateMIDletSuiteLoader.main(), bci=26
MIDlet:com.cinterion.jrc.JRC_Midlet abnormal exit
MIDlet:com.cinterion.jrc.JRC_Midlet abnormal exit
Could JRC be damaged somehow in the proces of OTAP or what is the problem?
Best regards,
Jure
Hello Jure,
Did you only update your MIDlet or JRC also?
If JRC was updatead and is crashing after that there might be some incompatibility - you might have installe JRC for a different firmware version or module.
If only the MIDlet was updated and there is java.lang.NoClassDefFoundError it could mean that the midlet was built incorrectly, with libraries for some other or older module etc.
If JRC was OK before and you have uninstalled the faulty application, JRC should not be crashing.
Please check ATI1 reply and JRC version with at^sjam=4 command.
Best regards,
Bartłomiej
Hello Bartlomiej,
only our MIDlet was updated. I allready deleted the MIDlet but JRC still crashes.
This are AT replys:
Regards,
Jure
Hello Jure,
Please check ATI1 reply for the full firware version so that we could check if the JRC version matches the firmware verion. SYSINFO: 200 means that JRC was not tried to start (no autostart, no midlet at all, whatever). Please aslo check AT^SCFG? output if autostart is active.
Do you see this exception every time after start or just SYSINFO messsage?
Best regards,
Bartłomiej
Hello Bartlomiej,
ATI1 and scfg?:
USB COM PORT:
TTL ASC1 debugging:
Regards,
Jure
Hello Jure,
You have the correct JRC version for your firmware.
It really looks like there's no other MIDlet installed and JRC crashes just after start due to the lack of JRC_LogManager dclass. So SYSSTART URC is not even displayed and there's ^SYSINFO: 200 as if JRC was not even attemted to be started. It looks strange. I'd recommend to reinstall JRC and firmware if this does not help. Please let me know if you need firmware.
Regards,
Bartłomiej
Hello Bartlomiej,
I reinstaled JRC and now it looks OK. Do you maybe know what could cause this problem?
Regards,
Jure
Hello,
It's good that you got it working again.
So it seems that JRC installation got somehow corrupted. I can't explain this - the only thing I can think of is that maybe the module was being powered off incorrectly - I mean by cutting off the power instead of software initiated power-off which is always a recommended way. There is a very small risk that some operation may not be finsihed properly in such a case which may result in some problems.
Regards,
Bartłomiej