EHS-5: Can't upload jar after upgrade | Telit Cinterion IoT Developer Community
April 11, 2018 - 10:35am, 4686 views
Hi!
I've updated my module from 0051 to 0055, exact versions are:
ati1 Cinterion EHS5-E REVISION 03.001 A-REVISION 00.000.55
After this update I can no longer upload any file with .jad or .jar extension (note: there are no files with this name on a:/):
at^sfsa=open,a:/test.jad,8 ^SFSA: 13 ERROR
at^sfsa=open,a:/test.jar,8 ^SFSA: 13 ERROR at^sfsa=open,a:/test.txt,8 ^SFSA: 0,0 OK
Interstingly, there was no problem installing jar over the network using OTAP command.
What am I doing wrong? Is there any configuration to tweak?
Hello,
Please check AT^SCFG? output. Maybe autostart is disabled and JRC is not running. Some AT commands are implemented in JRC.
Regards,
Bartłomiej
Nope, that's not the case:
Also, that would mean all AT^SFSA commands fail - see above, I can upload .txt file, but not .jad/.jar, which is hilarious.
Regards,
Przemysław
OK, you are right - I have also tried this with the similar result. Was it working differently with the previous firmware versions?
You can use AT^SJDL command instead - this is working.
Regards,
Bartłomiej
Well, our automation scripts currently use AT^SFSA to upload the file and install it with AT^SJAM=0,... .
We can switch to AT^SJDL, but this means extra unexpected work on our side :-/
I'm sorry for this. I have checked that this behavior has already been identified but it is not going to be changed in the near future. There is AT^SJDL command that can deal with jar and jad files.
Regards,
Bartłomiej
The problem doesn't stop here, I tried AT^SJDL just to get the following:
AT^SJDL=1,409,"a:/test.jad"
CONNECT
.. here I upload the data and get:
+CME ERROR: memory failure
What's "memory failure", anyway? Filesystem **********?
Regards,
Przemysław
Hello,
Please remove "a:/" from the path and leave the file name only. Then try again. There should be no error.
Regards,
Bartłomiej
Indeed, that worked. I wish the error message was less misleading :)
Thank you!
If anyone else hits this - minor hint: you can still specify the path, so e.g. AT^SJDL=1,<n>,"somedir/file.txt" works.
Great!
BR
I just received the following information from Aplicom, any comment on that?
Pages