Download on BGS5 | Thales IoT Developer Community
May 2, 2016 - 8:40am, 5923 views
I am sucessfully downloading software (JAR/JAD) into the flash using AT^SJDL=1 commands.
But, if am using `AT^SJAM=0,"a:/A9Sw/theSoftware.jad",""` after 20seconds a ^SYSLOADING is responding, in stead of OK. The software is installed and starting, but I was wondering if this normal?
So you get "^SYSLOADING" while installing the application but the application is installed after that even though there's no OK reply and it is possible to run it then? Is it reproducible? Normally you should get OK reply or ERROR and ^SYSLOADING is only thrown on system start. And you should generally wait for SYSSTART before issuing commands to the module.
What interface are you using? You could redirect system out to ASC0 and check if there's anything unusual. Could you also paste AT^SCFG? output?
I am using a Java class with import gnu.io.SerialPort; from the RXTX library 1.7
Here the response of AT^SCFG?
Yes , it's reproducible. I now noticed that stopping a midlet with (AT^SJAM=2) also results in ^SYSLOADING directly after W [2016-05-02T11:13:09Z] DestroyApp called is written to SYSTEM.OUT.
Update, I narrowed down the "problem" a bit.
your module has disabled the loading of the JRC or just the JRC has been deleted of the FFS.
chekc with at^sjam=5 if the JRC is running.
the quickly way to solve the situation is to reflash the firmware in the module
Somewhere over the rainbow!!! Looking for the Oz Land!!!
How can I reflash the firmware when I can't access USB port for the module?
You can do it on serial interface.
The JRC is a factory MIDlet that implements some of the module's functionality and it starts automatically when the global autostart for applications is enabled. So you should not set AT^SCFG="Userware/Autostart","","0". When system starts it displays ^SYSLOADING and when JRC is started the ^SYSSTART is also displayed. The option "Userware/Autostart/Delay" also influences JRC.
Thanks. Having JRC enabled seems to solve the problem.
I now have a smaller problem left, with downloading a 550kB JAR on the unit using AT^SJDL1. In ~30% of the cases the JDL **** does not return a checksum but a timeout. I am using the default 115200 baut rate ****. Can anybody give me a hint on this?
Can you write some more details? What terminal program is used? Which interface are you using: USB or UART? Is it always the same file with the same size? Is it possible that the file is used by another application at that time or there is not enough space in the module's file system?