Connect shield stopped working after using the gwinswup | Telit Cinterion IoT Developer Community
October 13, 2017 - 12:19pm, 2899 views
I am working with the Connect shield that has Els61 chip on board. Everything worked fine for 10 days. I could debug a running software from the NetBeans and I didn't have any major problems except that occasionally I had to restart the device.
But today something strange happened. The AT command at^sjam=4 stopped working. I couldn't get neighter OK nor ERROR. at^sjam=5 worked but I couldn't see my .jad file running. Also, I couldn't run the software from the NetBeans anymore.
I found on your forum this thread: https://iot-developer.thalesgroup.com/threads/atsjam-does-not-give-response
As Bartłomiej recommended, I tried to run gWinSwup (els61-us_e_gwinswup_rev01.000_arn0001400) with "Recovery file system" option. After several "module update failed" messages, the new fw started to transware to the device. But in the and, after 6-7 minutes, again "module update failed" message occured. And after that my module is completelly dead. I can not see it any more from Tera Term, my Windows is not recognizing any device on the USB.
Is there any solution for this problem? How to 'see' the modem again on my Windows?
Was the described AT^SJAM behavior observed even after rebooting the module? How about other functionality, FFS access with MES - have you checked it?
For firmware update with gWinSwup you should be using USB ****m or ASC0 interface.
If the firmware update failed after the old firmware was deleted the module may not have the valid firmware but still there should be a bootloader. In such case it should start in a firmware upload **** and should wait for firmware upload on ASC0 for 10 seconds after start and then on USB. So you should reboot the module and start gWinSwup, choose the appropriate port, check "No Firmware in Module" and start.
If you will not be able to install the firmware with gWinSwup the only thing you can dso is to report the broken module to your supplier or local Gemalto office.
Thank you for your respoonse.
Yes, the described behavior occured even after the reboot. I didn't chacked the FFS access with MES and now I have no access to the module.
I tried with the instructions you gave me. So, I've rebooted the module, started gWinSwup, choosed the port and checked the 'No firmware in Module'. But after I click on the Start, the messages are: first, 'Initializing Firmware update' and after that 'Module update failed'. Even my module is on the COM port 4, I've tried with all COM ports. It is the same on every port.
Do you recommend anything else?
Have you also tried on module's ASC0 interface, have you connected all RS232 lines? On this serial interface it should be possible only for 10 seconds after booting the module.
After 10 seconds the module should enumerate on some USB and you could try on USB then. I'll send you one document so that you can make sure that you did all properly.
If all that have failed you will not be able to do anything more - it is also possible that the module is damaged. So in that case you need to contact your local Gemalto technical sales.
write me an PM with you email adress. I will send you an instruction how to recover from that ****.
Currently I am preparing this instruction for the community. I will send you the draft version.