You have performed the proper steps to push software updates but devices are stuck on (Ready To Update) for a prolonged period and the upgrade is not downloading.
Why is this happening?
We have identified two reasons why his stage could occur; the gateway is unable to check for new updates, and the downloadTimeoutSeconds parameter is set too low.
1. The gateway is unable to check for new updates,
At times, the MGOS device is unable to check if there are new software updates on its repository (resolved in later firmware). The device will remain state remain in a "Ready To Update" state unless the device is manually triggered to check and download new software.
One way is a Reboot or performs a link bounce (idling and then re-activating the WAN connection).
Or
You can navigate the LCI and choose General Tab β Tools β Download - New Software.
The software download will start, once all packages have been downloaded the device will ask you to reboot so that the upgrade take effect.
Here is an example:
2. The downloadTimeoutSeconds parameter is set too low.
The current download timeout default for oMG v3.14 is 600s. In other words, If this parameter is below 600 seconds the firmware update downloads will not occur; however, if it is set to at least 600 seconds it will help to ensure successful downloads
How to increase the downloadTimeoutSeconds parameter?
In the swupdated.yaml configuration file, the downloadTimeoutSeconds parameter has to be updated to at least 600 seconds. In this case, we will set it to 1200.
Configuration>Deployment>Configuration Control> Files>click to display files> swupdated.yaml
Update the downloadTimeoutSeconds parameter from 300 to 1200
Save the changes.
Finally, we can proceed with the Core and application updates deployment.
Deploy the Core-Software-3.14.5-20170515.1 & oMG-Application-9.48804.v3.sdk4-20200319.3 updates, and reboot the device once the update files are downloaded. If this process does not go on its own, a clean-local-software-update-cache and download-new-software-updates can be done through the gateway's LCI
Deploy the oMG-Core-Software-3.15.1-20180417.1, and reboot the device once the update files are downloaded.
Deploy the oMG-Core-Software-3.15.2-20200416.1, and reboot the device once the update files are downloaded.
Notes:
1- After you issue the reboot, the device will be offline and cannot be used for the duration of the upgrade process, and this can take between 15 minutes and 20 minutes
2- The Ignition in the vehicle needs to be ON otherwise the download won't take place and the logs will show an error (Condition Not Met)
3- The cellular link needs not to be on (High Cost), otherwise, the download won't take place and the logs will show an error (Condition Not Met)
4- Do NOT unplug the power or interrupt power during the upgrade process, as this can potentially brick the device
β