Skip to main content
Version: Torizon OS 7.x.y

Remote OTA Updates Overview

Introduction​

In this article, you learn the basics about Secure Remote Updates with Torizon. This article also directs you through the steps on how to use the feature.

What is the Torizon Secure Remote Updates Feature?​

Remote Updates is a feature in Torizon that enables Over-The-Air (OTA) remote updates. It is an alternative to the Torizon Secure Offline Updates and uses the same technology stack: OSTree and Aktualizr. The Remote Updates feature brings the capability to perform secure and reliable application and OS updates to Torizon OS based devices.

You can learn more about updates with Torizon on the overview article, and for more in depth knowledge, read the Torizon Updates Architecture.

Main Features​

With the Remote Updates feature it is possible to:

  • Securely update the Operating System and/or Application components of a running device with an active internet connection
  • Automatically update a device whenever a new update is available on the server
  • Perform synchronous - both the OS and the Application as a single component - remote updates securely
  • Automatically roll back to the last working version of the OS or the application in case the update fails
  • Block updates from happening from the application’s side, in case you have a critical application that cannot stop for an update to take place

The Update Process​

The update processes of a device with Secure Offline Updates and Remote Updates are similar since both are based on the same technology stack. You can see the workflow in the following diagram:

Remote Update Workflow

Creating the Packages​

The first step is to bring your package - subsystem packages, bootloader, OS and/or Application - to the Torizon Cloud domain. Learn how Torizon manages Software Packages reading the Feature Overview

You can create a Torizon Cloud Application Package from the web UI, TorizonCore Builder or an IDE with Extension for Torizon. You also need to push your application to a Docker registry, so the device can download it.

To create a Torizon OS Package, you should use TorizonCore Builder to push images built by you or other collaborators. Remember, you can always use Toradex's provided images out-of-the-box.

Initiating the Update​

The next step is selecting the components in the Torizon Cloud. You can choose any package type for updating: subsystem packages, bootloader, OS and/or Application packages to be updated in a single device or in an entire fleet. When you initiate an update, it means that the target device or the devices in a fleet have a new update to process when it goes online and reaches the Torizon Cloud.

You can also initiate updates programmatically with the Torizon Cloud API, which lets you integrate updates into your own CI/CD pipelines or fleet management solution.

Deploying the Remote Update​

The provisioned devices periodically search for newly available instructions and update packages on the server. The next time any device addressed for updates goes online it downloads, validates, and deploys the update.

info

The update process is fully automated and no user intervention is required at any time, unless explicitly configured to do so. If you are performing an OS or synchronous update, the board automatically reboots once.

Next Steps​

Take your next steps with a practical example:

Webinars​

Toradex has presented webinars about Secure Offline and Online Updates and you can watch them on demand.

Secure Offline and Online Updates for Linux Devices​

Learn more about this webinar on the landing page, or watch it following:

Send Feedback!