EHS-5: bricked after aborted firmware upgrade | Telit Cinterion IoT Developer Community
April 11, 2018 - 11:18am, 2427 views
I have one EHS-5-based device bricked after gWinSwup cancelled by accident.
I've tried to use "No Firmware in Module" checkbox, and it appears to work, but it fails everytime after flashing some blocks (over 200). Is there any other way to reflash the failing device?
BTW, does it mean, that flashing with AT^SFDL can also make a device unbootable, if device is powered off during the operation? I assume there is only a single firmware image in Flash...
Below is the relevant log part:
[2018-04-09 13:25:55]Initializing firmware update... [2018-04-09 13:26:12]Erasing flash memory (this can take a couple of minutes without visible progress)... [2018-04-09 13:28:47]Transferring firmware in progress... [2018-04-09 13:30:10]ERROR: Timeout waiting for response after block no. 215! [2018-04-09 13:30:10]ERROR: Firmware update failed! [2018-04-09 13:30:10]Parsing configuration file... [2018-04-09 13:30:10]Restoring module state... [2018-04-09 13:30:10]Module update failed
Generally the firmware update procedure is implemented in a way that it should be possible to repeat the procedure in case of a failure caused by switching off the module or cutting off the power during the update. In the beginning of the process the old firmware is deleted. So if it is disturbed after or during that step there is no firmware on the module but still there is a bootloader and module is ready for firmware download after each boot.
So in case of gWinSwup tool you should check "No Firmware in Module".
In case of AT^SFDL=2 the firmware is loaded from the internal flash file system (it should be copied there before the process can be started). If the power is cut off and restored the process is started again automatically.
In case of your problem please make sure that you are using the modem USB interface or ASC0 and the correct firmware version is loaded. Can you write what firmware version was previously installed and what is loaded now? Maybe you could also try to load the same as was before.
If this will not work on any interface there is probably not much you can do more. I think that you should then contact your local Gemalto office and report a broken module.
Well, I have to use serial port, as Aplicom was kind enough not to provide USB access in their TRIX A9 modules :)
Previously it was firmware version 0051. I do not have USF file for that release.
Probably they didn't need USB for their functionality. AREV 51 is quite fresh and close to 55. Normally there should be no problem to flash from 51 to 55. I can send you 51 but there may be no difference. You could try with other baudrate also. I'll also send you an application note document about updating firmware. Maybe this will help.
I tried flashing with 0051, but the result is the same, more or less.
The update starts so I suppose that you have applied the following instructions from the document:
- Open gWinSwup and restart the module.
- After booting the module you have ***. 10s to check the option “No Firmware in Module“ and click the START button.
- If the download does not start within 10s the module switches from ASC0 to USB.
Maybe you are using some USB-RS232 converter which is causing problems. You could also try to trace the serial communication.
But if it's not a USB converter issue and as regardless of the firmware version the download always stops at more or less the same point with information that there was a timeout waiting for response I think that you may assume that the module is damaged and report it to your local Gemalto office.