PLS62T - Can't communicate over USB or ASC0 | Thales IoT Developer Community
December 22, 2021 - 7:28pm, 554 views
I'm trying to troubleshoot a device that had some conflicting userware installed. I was struggling against both midlets to stop/uninstall them over ASC0 (being too stupid/lazy at the time to find a USB cable), and in the process I foolishly managed to:
1. Disable Userware/Autostart (and maybe set Userware/Autostart/Delay to a very large value)
2. Potentially mess up Userware/Stdout (not sure if I had last set it to ASC0 or NULL)
At this point, all I see on ASC0 is "^SYSLOADING" and then "SYSTEM.OUT STARTED", and it won't respond to AT commands. I also cannot get USB to respond to any commands. I've made sure that USB is configured in device manager with a 115200 baud and Hardware flow control.
I can get both ASC0 and USB working on a different PLS62T module without a problem, so it seems like the issue is related to the current configuration on the module. I'm just not sure how I can resolve this if I can't send it any AT commands.
Do you have any recommendations for troubleshooting this? I'm ultimately just trying to do a factory reset, so it's not a problem at all if that's a requirement.
Hello,
In case of USB the baudrate setting is not relevant. After plugging in USB cable you should see more than one virtual interface in the system. Did you try more than one? Not all will reply to AT commands. Please see "Serial/Interface/Allocation" setting in the AT commands specification. I believe that you should be able to communicate on USB.
If autostart is disabled the JRC MIDlet is also not started and the module throws ^SYSINFO: 200. So please activate it later.
Regards,
Bartłomiej