Autostart locked up Concept Board - solved | Thales IoT Developer Community
June 17, 2015 - 11:19pm, 2257 views
I set my Midlet to Autostart, and then could no longer use the USB serial ports which are set up by the IMP Dbg system. I don't really understand the IMP Dbg very well anyway. So there was no way to send AT commands, there was no port that could work for sending AT commands. So the board just ran my program forever, even when turning it off and on again. Looked like it was a brick.
For the next person: the solution was to move the USB cable to the ASC0 port since that port appears to have a remaining AT Command capability. So simply send the AT^SCFG to turn off autostart, restart the board, and all is well again.
Roland
Roland
Hello Roland,
If the Java MIDlet is running you are still able to issue AT commands on USB or serial interfaces (if the java application is not using the ports).
If you configure the System out for the application to some port, this port is reserved only for application out, so on this particular port only you can't issue AT commands (regardless if the application is running or not).
Another thing is that if you have the open USB connection to the module on PC while the module restarts you can loose the possibility to communicate via USB until you close the USB connection on PC and restart the module. This doesn't affect serial connections (ASC0, ASC1). That's probably why you were able to connect via ASC0 and switch off autostart.
Please remember to activate the global autostart setting again (after uninstallation of your application and/or installation without autostart parameters in the JAD file), because without that the factory JRC MIDlet will also not start automatically (and this JRC application implements some of the module's features).
Best regards,
Bartłomiej