PLS62W software update fails | Thales IoT Developer Community
June 27, 2022 - 2:19pm, 1880 views
Hello,
When trying to update the PLS62W software with gWinSwup, an error sometimes happens: the upgrade stops to Transferring MIDlet[JRC-xxx.jad] in progress… and cannot go further.
Does someone have a solution to this problem?
Thanks,
Hello,
Have you checked the log file that gWinSwup usually creates in the same folder? Maybe there's some more information. What interface is used - USB or RS232? Did you try to wait a little longer? How much time does it take?
BR,
Bartłomiej
Hi,
Many thanks for your prompt response. I am using the USB interface. Here is the message printed in the log file:
[2022-06-27 17:40:25]OpenAttachedFile: 13 fail
[2022-06-27 17:40:25]Disabling userware autostart...
[2022-06-27 17:40:25]Checking module Character Set ('GSM' or 'UCS2') ...
[2022-06-27 17:40:43]Restoring module state...
[2022-06-27 17:40:51]Initializing firmware update...
[2022-06-27 17:40:54]Waiting for re-enumerated USB port...
[2022-06-27 17:41:20]Warning: Timeout waiting for 1st ACK before swup start!
[2022-06-27 17:41:20]Erasing flash memory (this can take a couple of minutes without visible progress)...
[2022-06-27 17:41:20]Transferring firmware in progress...
[2022-06-27 17:41:36]Updating flash file system (this can take a couple of minutes without visible progress)...
[2022-06-27 17:41:51]Restoring module state...
[2022-06-27 17:41:51]Firmware update succeeded
[2022-06-27 17:41:51]Erasing old data...
[2022-06-27 17:41:54]Checking module Character Set ('GSM' or 'UCS2') ...
[2022-06-27 17:42:06]Restoring module state...
[2022-06-27 17:42:06]Parsing configuration file...
[2022-06-27 17:42:06]Warning: Cannot find property "MIDlet-2" anymore
[2022-06-27 17:42:06]Warning: Cannot find property "File-1" anymore
[2022-06-27 17:42:06]Opening \\.\COM25 in 115200 baudrate
[2022-06-27 17:42:18]Initializing MIDlet[JRC-1.62.04.jad] update...
[2022-06-27 17:42:18]Removing existing JRC-MIDlet...
[2022-06-27 17:42:18]Transferring MIDlet[JRC-1.62.04.jad] in progress...
[2022-06-27 17:42:19]Error: Failed to read checksum!
[2022-06-27 17:42:19]ERROR: MIDlet[JRC-1.62.04.jad] transfer fail
[2022-06-27 17:42:19]Deleting temporary MIDlet[JRC-1.62.04.jad] file
[2022-06-27 17:42:19]Deleting temporary MIDlet[JRC-1.62.04.jar] file
[2022-06-27 17:42:19]ERROR: update MIDlet[1] fail
[2022-06-27 17:42:19]Initializing MIDlet[JRC-1.62.04.jad] update...
[2022-06-27 17:42:19]Removing existing JRC-MIDlet...
[2022-06-27 17:42:19]Transferring MIDlet[JRC-1.62.04.jad] in progress...
[2022-06-27 17:42:35]Error: Failed to finish MIDlet update!
[2022-06-27 17:42:35]ERROR: MIDlet[JRC-1.62.04.jad] transfer fail
[2022-06-27 17:42:35]Deleting temporary MIDlet[JRC-1.62.04.jad] file
[2022-06-27 17:42:35]Deleting temporary MIDlet[JRC-1.62.04.jar] file
[2022-06-27 17:42:35]ERROR: update MIDlet[1] fail
Then, the following section keeps being printed endlessly:
[2022-06-27 17:42:19]Initializing MIDlet[JRC-1.62.04.jad] update...
[2022-06-27 17:42:19]Removing existing JRC-MIDlet...
[2022-06-27 17:42:19]Transferring MIDlet[JRC-1.62.04.jad] in progress...
[2022-06-27 17:42:35]Error: Failed to finish MIDlet update!
[2022-06-27 17:42:35]ERROR: MIDlet[JRC-1.62.04.jad] transfer fail
[2022-06-27 17:42:35]Deleting temporary MIDlet[JRC-1.62.04.jad] file
[2022-06-27 17:42:35]Deleting temporary MIDlet[JRC-1.62.04.jar] file
[2022-06-27 17:42:35]ERROR: update MIDlet[1] fail
I have waited for more than two hours without success.
Best regards
Looks strange. Maybe the update program is corrupted or there is not enough space on the module's file system or there's some other problem on uploading the JRC MIDlet. As it's USB I wouldn't suspect any data corruption on the interface. Does it happen with one module only?
Anyway you could try on another USB or cable or without USB hub on the way or on RS232. What FW version are you installing? It looks like usf is installed and there is only a problem with JRC. Do you have JRC MIDlet as separate files? You can then try to just upload it to the module and then install it manually as any other MIDlet with AT^SJAM command.
Regards,
Bartłomiej
Hi Bartłomiej,
This error occurs with about 25% of the modules we must update (we do not update them all). We are trying to install the FW version 02.010, so the application used is pls62-w_gwinswup_rev02.010_arn01.000.05_crn00119.02.
We do have JRC MIDlet as separate files, but the AT^SJAM=0 command does not work on these broken modules (but it works well on the good ones). Depending on the bugged device, we can successfully upload the .jad and .jar files to the modules, but there are other modules were the flash is that bugged that it can not even receive the files. Anyway, in the case we successfully upload the file, the following command: AT^SJAM=0,"a:/JRC-1.62.03.jad","" raises an ERROR. Note that the device is still responsive to simple AT commands.
Changing the USB cable does not solve the problem, and we do not have any USB HUB on the way. Regarding RS232, it is very difficult for us to access those pins in our application. Moreover, the update time is very long compared to USB so we would like to solve the problem this way.
Best regards,
Best regards,
Hello,
You could set AT+CMEE=2 before the installation attempt to get some error description. Or try to install some other MIDlet to check if that works. Or you could try to install with OTAP.
Anyway based on your last comment it seems to me that there may be some issue with the flash memory in these modules if even uploading the MIDlet may not work. Or some data corruption on the flash. Is it possible to list the installed or running MIDlets? In such a case you could also try to mark the "Recovery File System" checkbox in gWinSwup.
BTW was everything fine with these modules before the firmware update attempt? Were these devices already in the field or are they new?
If everything fails it may mean that there is really some issue with the flash. Then I think that you could report it to the Thales support directly or via your distributor.
Regards,
Bartłomiej
Hello Bartłomiej,
Unless you have another idea, we will report it to Thales.
Best regards,
"operation not allowed" on MIDlet installation attempt you would probably see if the the other version of it is still running. As I understand this is not the case here. If these modules were already malfunctioning, please report this officially.
BR,
Bartłomiej
This is what we will do. Many thanks for your help!
Best regards,
Nil