ELS61-E keeps on restarting | Telit Cinterion IoT Developer Community
March 2, 2022 - 8:50am, 893 views
I have a DSB75 board and an ELS61-E REL.1 evaluation module.
The module is continuously restarting (every 2-3 seconds) and I have no way to stop it (USB is not enumerating, and ASC0-ASC1 ports seems to be unusable, so I cannot send any AT command).
Is there any way to recover it?
Best regards,
Marco
Hello,
Do you see any output on ASC0 or ASC1? Hwo did you lead to this situation? Is there any Java MIDlet running in autostart mode? Is SIM inserted?
Best regards,
Bartłomiej
Hello,
I've uploaded a MIDlet, it is running in autostart mode, I think the problem is that it is crashing so the module is restarting.
On ASC0 or ASC1 what I see is some spurious characters every time the module restarts, I've tried with different baudrates and with or without RTS/CTS h/w control, but no significant strings there.
No SIM inserted.
Best regards,
Marco
Hello,
MIDlet application crash can happen during the development. That's why it is good to configure some delay for autostart with AT^SCFG command during the development phase.
Because when the user app is crashing on start and if this crash is causing the module reboot the only solution is to disable the autostart with an AT command. The best interface for that is ASC0 because it is active in every configuration and USB enumeration takes some time. So the command should be sent just after module start. Usually it is possible even with the standard delay 0, but it can take a while to succseed.
But if you don't even see SYSLOADING URC, it doesn't look good. Is your app using the serial interface? Or maybe system out is redirected to it?
BR,
Bartłomiej
Hello,
yes, the application is using it. But also before the application was loaded, the ASC0 wasn't showing anything. The system out wasn't redirected (set to null).
BR
Marco
By default AT commands are not possible on ASC1 (if you haven't changed AT^SCFG="Serial/Interface/Allocation",). So there is only ASC0. If the crash happens before the app opens ASC0 or it is not one of the first things done by the app there could be a chance. It is also possible that the serial interfaces are disabled by AT^SOPW command. If not maybe it's a matter of baudrate setting.
Please prepare the command and try to paste it and send when the module boots. If this fails you can't do anything more.
BR,
Bartłomiej