Updating Your Edge Computing Gateway

Updating Your Edge Computing Gateway

Before every update

Two things, every time.

1
It is your rollback point, and where automatic recovery lands. The device never makes one itself.
2
Know the package type
A firmware update, a full-image install or a clone restore. They do very different things.

Updating a RobustOS Pro device is built around one principle: the package you apply decides what happens — never the path it arrives by. This guide covers the delivery paths, what to expect from each update type, the software tracks that update separately, and what to check before downgrading.

Before every update — the two-item checklist

1. Create a backup. The device never creates a backup automatically — not even before an update. Your most recent manual backup is your rollback point, and it is also where the automatic boot-failure recovery will land. On-device backups do not survive a full-image install, so for a copy that leaves the device, create a clone package and write it to external storage (see Clone packages, below).

2. Know which package type you are applying. A standard firmware update removes nothing you added (though a package version can change — see What an Update Changes); a full-image install starts the device over; a clone restore replaces the device's state with the clone. If you are unsure which type a file is, check its documentation before applying it.

Three kinds of package

What happens to your software depends on which one you apply.

Firmware update
The normal field update. Installs in place.
Nothing you installed is removed
Full-image install
Re-flashes the base system by USB.
Everything you installed is erased
Clone restore
Puts a golden image on the device.
Replaced by the clone
Package typeWhat it doesYour software, settings, data
Firmware update (the standard field update)Installs the Robustel system components that come with that release, in place — no re-flash, no wipe. Not every release carries a new kernel; the release notes say whether one doesNothing removed — your apps, containers, settings and data are untouched; your installed packages are still installed
Full-image installRe-flashes the base operating systemErased — containers and on-device backups included
Clone restoreReplaces the device's entire software state with a prepared "golden image" — system software included, up to the base OS itself when the clone was built on a different version; the clone becomes the new factory baselineReplaced by the clone's content

The full part-by-part promise table is in What an Update Changes.

Four ways an update arrives

The path does not change what happens. The package does.

Web UI
Apply from the browser: System → Update.
Command line
The same operations over SSH, for scripts.
RCMS
Firmware, Robustel apps and settings across a fleet. Not your own software.
USB stick
Off by default. Needs your USB key when switched on.
Nothing installs or reboots on its own. You start every update, or your fleet operator does through RCMS.

Web UI. Sign in as an administrator and apply the update from the browser. Debian packages are installed and removed on the Debian Management page — note that it has no upgrade action, so moving a package to a newer version is a command-line operation (see Shipping a new version of your own software). RobustOS Pro apps are uploaded through the App Center.

Web UISystem → Update
Drop a screenshot of the firmware update page
The standard field update, applied from the browser.

Command line. The same operations are available over SSH for scripted or advanced workflows.

RCMS (fleet management). For fleets managed through RCMS — the cloud agent is disabled by default and must be enabled on the device — RCMS pushes firmware updates, distributes Robustel-built apps, and applies device configuration. It has no delivery path for your own Debian packages or containers on 2.4.x — updating those is your own route (see Shipping a new version of your own software, below). The device must be online; interrupted downloads retry automatically. Full-image installs are not an RCMS operation. Rollout planning (phasing, scheduling across a fleet) is handled on the RCMS side — see the RCMS documentation.

Updates are operator-initiated
RobustOS Pro 2.4.x does not schedule or apply updates on its own — nothing installs and nothing reboots unless you initiate it.

Debian package patching is likewise performed per device, at the time you choose. Plan updates into your maintenance windows.

One USB port, three jobs

Only one of them uses the USB key.

Storage
Plain file storage. Not a software operation.
USB update
Firmware, apps, settings or a clone from a stick, checked against your USB key. Off by default.
Image flashing
A full re-install or last-resort recovery. Needs hands on the device, not the key.
Use 1 · Storage
Mass storage
Plain file storage for the device — not a software operation; no keys involved.
Use 2 · USB update
Key-gated servicing
Firmware/app install, config import, clone restore — gated by your USB key; runs with no login.
Use 3 · Image flashing
Factory re-flash
Full-image install / recovery — a physical-access operation; not gated by the USB key.
Three different jobs on one port — only the USB update path uses the USB key.

USB update. A stick prepared with a firmware/app package and the device's USB key file updates the device automatically — no login needed once the key validates. This is a deliberate field-service feature: a technician can service a device without credentials being shared. This path is disabled by default (Interface → USB → USB → Enable Automatic Upgrade); if you enable it, the USB key is what makes it yours — the shared factory-default key must be changed (see Securing Your Device). The same path can also import configuration and restore a clone from the stick — and a clone is a complete software state, so restoring one can replace system software too, up to the base OS when the clone carries a different version (see What an Update Changes).

USB image flashing / recovery. The factory full-image install path — a fresh base OS install or last-resort recovery. This path is not gated by the USB key. It is a physical-access operation — it requires the device in front of you and a prepared USB stick.

What happens when you apply one

A firmware update is checked, installed in place, then the device restarts.

Verified
Its signature is checked. One that fails does not install.
→
Installed in place
No wipe. Your software stays.
→
Restart
The new version runs.
If the install fails
It aborts. The old software keeps running.
If the device cannot boot
After three failed attempts it restores your last backup.

A standard firmware update is signature-verified. The update — the kernel and Robustel system components it delivers — is cryptographically signed (RSA-4096) and verified before it installs; a package that fails verification does not install. A full-image install is not held to the same check. The device checks an image’s signature only when a signature file is supplied with it, and nothing requires one; what protects that path is physical access — see USB, above. On devices provisioned for verified boot, the device still boots Robustel-signed software only.

A standard firmware update installs in place and finishes with a reboot. If the installation fails, it aborts cleanly — the device keeps running its old software, nothing is left half-applied. If the device cannot boot afterwards, the automatic recovery restores your last backup after three failed attempts (see When Something Goes Wrong).

A full-image install re-flashes the base OS. It is performed via USB, with physical access to the device. Everything you installed is erased — copy container data off the device, or capture the whole device state in a clone package, first. A fresh factory baseline is generated from the new image on first boot.

A clone restore applies a prepared golden image from the command line or USB (factory pre-installation is available through Technical Support). The device checks the clone's integrity and model match and refuses on mismatch. After the restore, the clone is the device's new factory baseline.

Parts that update on their own track

Not everything moves with a firmware update.

KernelWith any of the three package types when they carry one, or as its own package. Never through a package operation.
Boot softwareOnly with a full-image install or a clone restore.
Modem firmwareOnly its own vendor package.
WiFi / Bluetooth firmwareWith the operating system.
RobustOS Pro appsApp Center, one device at a time.
Your packages and containersYou, with apt and docker.
  • Kernel and boot software never come from a software repository — no package operation changes them. The kernel is replaced by all three package types above when they carry one, and can also be shipped on its own as a standalone kernel package (offline file, signature-verified, reboot required). Boot software moves only with a full-image install or a clone restore, never with a standard firmware update.
  • Cellular modem firmware is never part of an OS update. It is updated only by its own dedicated, vendor-provided firmware package, on its own track. If a modem update is interrupted, the module keeps its old firmware.
  • WiFi/Bluetooth firmware ships with the operating system and is refreshed when the OS is — it is not a separate customer operation.
  • RobustOS Pro apps are installed, updated and removed in the App Center. You update one by uploading the newer version of its package, one device at a time.
  • Your own Debian packages are yours to move between versions — see Shipping a new version of your own software, below.
  • There is no automatic rollback of a package or app change. Treat one with the same care as a firmware update — back up first.
  • Containers are managed with the docker command line (Docker is not pre-installed) and follow standard Docker semantics. Which container ports can be reached from outside is controlled with Custom Rules (Network → Firewall).

Updating your own software

The device gives you a Debian machine to update on, not a service that updates for you.

1 · Publish
To a signed apt repository you control.
→
2 · Drive
Over SSH, with the tools you already use.
→
3 · Stage
One device first, then widen.
→
4 · Watch
Validate each new firmware release on one device.
Design this before you deploy. Once devices are in the field, a golden image is not an update route.

Everything above concerns software Robustel publishes. Your own packages, applications and containers are yours to update — the device gives you a Debian machine to do it on, rather than a distribution service to do it for you.

What the device gives you. SSH, with apt and docker behaving as they do on any Debian 11 host. Since Debian's support for Debian 11 ended on 31 August 2026, the Debian 11 repositories receive no new fixes; see Maintenance After Debian 11 for what that means and how it is fixed. That is the working path, and it is the only one that moves your software to a new version: the web interface's Debian Management page installs and removes packages but has no upgrade action, and the App Center takes an uploaded package one device at a time. Package sources are stock Debian, verified by signature the way apt always verifies them.

What it does not give you. Nothing updates on its own — there is no scheduled or unattended updating on 2.4.x, and package operations run per device. RCMS carries Robustel firmware, Robustel-built apps and device configuration; it does not carry yours.

For a fleet, bring your own route. The shape that works on a Debian estate works here:

  • Publish to your own repository. Serve your packages from a signed apt repository you control and add it to the device's sources. Devices then install your software the same verified way they install Debian's.
  • Drive it with your own tooling. SSH is the transport — configuration management, a job you schedule yourself, your own agent. Whatever you already run against Linux servers runs against these.
  • Stage it. One device first, confirm your software behaves, then widen. There is no automatic rollback of a package operation — your rollback is a previous version in your own repository, plus the backup you took first.
  • Watch the baseline. A firmware update can move a Debian package version underneath you; validate a new release on one device before rolling it out (see What an Update Changes).
Design this before you deploy
Once devices are in the field, a golden image is not an update route — restoring one is a per-device operation with no fleet push behind it.

Clone packages

The most complete copy of a device, and how you build a fleet from one unit.

Created on the command line
There is no Web UI button to create one.
Same hardware only
Same model and same hardware variant.
Carries credentials
Every unit built from it shares the reference unit's keys.

A clone package is the most complete copy of a device you can take off it: a single package holding the configuration, the packages and apps you installed, container images and data, and your user data — more complete than an on-device backup, which does not include the full system image. It is the recommended way to keep a copy that survives the device itself, and the basis of the golden-image workflow for fleets.

  • Create it from the command line (rbt-system-mgmt clone create). Write it straight to mounted external storage such as a USB stick, or generate it and copy it off afterwards. There is no Web UI button to create one.
  • Restore it from the Web UI (Software Update), the command line, or a USB stick.
  • Where it restores: onto the same device — including after a full-image install — or onto another device of the same model and the same hardware variant. The match has to be exact: a package built on a unit with 2 GB of RAM will not restore onto the same model fitted with 1 GB. The device keeps its own serial number and MAC addresses; the clone does not overwrite the target's identity.
  • Before you build one: clear the package cache (apt-get clean), make sure the writable layer has at least 50% free space, and use an ext4-formatted USB stick. Check the finished package with rbt-system-mgmt clone info before you rely on it.
  • One clone, a whole fleet: send the package to Robustel Technical Support and it can be pre-installed during manufacturing — the practical route for volume. Restoring per device by USB works too, one unit at a time.
  • It carries your credentials. A clone contains the device's SSH host keys, TLS certificates, VPN credentials and cloud identifiers, so every unit built from the same golden image shares them. Plan for that before you deploy at scale — see Securing Your Device.

Step-by-step instructions for building and deploying a clone package are published in the Robustel knowledge base: How to Bulk Copy EG Device Configurations & Applications.

Going back to an older version

Possible, but not an update in reverse.

1Feature loss2Hardware-support loss3Third-party software breakage4Settings fall back to defaults

A downgrade re-opens whatever the newer version had fixed. Back up first, and check the release notes.

A downgrade is not an update in reverse. The package verifies and installs like any other — but the version you land on is the version as it was, and four things can bite:

1
Feature loss
Features introduced after the target version don't exist there.
2
Hardware-support loss
Hardware modules enabled in later releases are not recognized by older firmware — a module can go dead on downgrade, and with it the device's connectivity.
3
Third-party software breakage
Your own software configured against the newer environment can fail on the older one.
4
Settings fallback
Configuration written by newer firmware may not be understood by the older version; affected settings fall back to defaults.
The four downgrade restriction classes. On devices provisioned for verified boot, boot software is additionally never downgraded after Secure Boot is locked.

Before downgrading:

  • List what you depend on that arrived after the target version — features, hardware modules, and third-party software.
  • Create a backup (and a clone package for an off-device copy).
  • Remember that a downgrade also returns the device to an older security baseline — it re-opens whatever the newer version had fixed. If in doubt about a specific target version, check its release notes or ask Robustel support.
What an Update Changes
What each operation keeps, replaces or erases.
When Something Goes Wrong
Recovering from a failed update.
Securing Your Device
USB key management and hardening.
Keeping Your Device Secure Over Time
When updates exist and how long releases are supported.

What this guide does not cover

Next · step 9 of 13When something goes wrong →The recovery ladder, from a failed install to a re-flash.