5 thoughts on “Modem crash when deleting or uploading script sometimes”
I’m trying to upload a bunch of Python scripts to a GL865-DUAL but every now and then I run into issues when either deleting the old .pyo file or uploading the new .py file.
From my application:
[DBG] GL865: Uploading CUHandler.py (2357 bytes)
[DBG] AT#DSCRIPT="CUHandler.pyo"
OK
[DBG] AT#WSCRIPT="CUHandler.py",2357
[ERR] GL865: Timeout waiting for script upload prompt.
From the modem:
SYSendMsg – queue error – err code -46
13 200
AT QUEUE FULL
Prim 13 Mess 0 Task_Id BA
Prim 78 Mess 19C85E Task_Id BA
Prim 78 Mess 19C88E Task_Id BA
Prim 13 Mess 0 Task_Id BA
Prim 27 Mess 19CF8E Task_Id BA
Prim 179 Mess 19C08E Task_Id BA
Prim 154 Mess 19C67E Task_Id BA
Prim 78 Mess 19C6EE Task_Id BA
Prim 106 Mess 19D4AE Task_Id BA
Prim 179 Mess 19D56E Task_Id BA
Prim 200 Mess 19DFAE Task_Id BA
Prim 154 Mess 19E42E Task_Id BA
Prim 279 Mess 815F0 Task_Id BA
Prim 13 Mess 0 Task_Id BA
Prim 1157 Mess 81E10 Task_Id RR
Prim 1299 Mess 80E10 Task_Id BA
Prim 13 Mess 0 Task_Id BA
Prim 279 Mess 812D0 Task_Id BA
Prim 13 Mess 0 Task_Id BA
Prim 13 Mess 0 Task_Id BA
Last FN 2538042
Protocols Version: 5.05.000
System Version: 10.00.154.2-B000
*** SYExit(10) [ Message fail ] called from B85FEC (task BA) PSW 0042
Anything I can do to prevent this? Should I take some additional steps before uploading?
Hi,
do you send the AT#WSCRIPT immediatelly after the AT#DSCRIPT OK response or there is a 2-3 second pause in between?
I’m asking this because even if #DSCRIPT returns the OK, the delete operation is done in background and it can interfere with #WSCRIPT.
Aha, I did not know that. I was not waiting before writing so that could very well be it. However, now I can’t upload the script at all:
[DBG] AT#DSCRIPT="CUHandler.pyo"
+CME ERROR
[DBG] AT#DSCRIPT="CUHandler.py"
+CME ERROR
[DBG] AT#WSCRIPT="CUHandler.py",2357
+CME ERROR
I’ll try to switch units to verify that I haven’t broken the old one.
Hi
just +CME ERROR without any other cause?
Can you set AT+CMEE=2 and check again the error response?
AT#RSCRIPT and AT#LSCRIPT are also failing?
Otherwise try AT+CMAR=00000000 to format the NVM and start from a clean situation.
It was just giving error with no more information. I just switched back to the broken unit and for some reason it seems to be working now (of course). I will keep an eye out and try your suggestions if it happens again.
We use cookies to enhance your browsing experience and help us improve our websites. To improve our website, we carefully select third parties that use cookies to allow us to serve specific content and achieve the purposes set out in our cookie policy. For more information on how to make adjustments through your browser to the cookies being used on your device, please click Find Out More link. By closing this banner or continuing to browse our website, you agree to our use of such cookies. FIND OUT MORE
Hi,
do you send the AT#WSCRIPT immediatelly after the AT#DSCRIPT OK response or there is a 2-3 second pause in between?
I’m asking this because even if #DSCRIPT returns the OK, the delete operation is done in background and it can interfere with #WSCRIPT.
Aha, I did not know that. I was not waiting before writing so that could very well be it. However, now I can’t upload the script at all:
I’ll try to switch units to verify that I haven’t broken the old one.
Hi
just +CME ERROR without any other cause?
Can you set AT+CMEE=2 and check again the error response?
AT#RSCRIPT and AT#LSCRIPT are also failing?
Otherwise try AT+CMAR=00000000 to format the NVM and start from a clean situation.
It was just giving error with no more information. I just switched back to the broken unit and for some reason it seems to be working now (of course). I will keep an eye out and try your suggestions if it happens again.
Thanks!