SWUpdate to Pantavisor
SWUpdate updates the image: a sw-description file lists images and the
partitions or handlers they are written to, optionally in a double-copy (A/B)
layout, often orchestrated by a hawkBit server. It is flexible and scriptable,
but the unit of update is still a set of partition images. Pantavisor replaces
that model — it owns PID 1 and ships every change as a content-addressed
revision, transferring only the objects that changed.
See also: Pantavisor vs SWUpdate for the capability comparison.
How the concepts map
| SWUpdate | Pantavisor | Notes |
|---|---|---|
meta-swupdate Yocto layer | meta-pantavisor | Swap the layer; Pantavisor builds the BSP, kernel, and containers. |
sw-description + images | A pvr revision | The whole device state is one signed, diffable manifest, not a script over partitions. |
| Double-copy (A/B) partitions | Revisions in the trail | Rollback is to the previous revision; no duplicated partition set. |
| Image handlers (rootfs, raw, files) | Containers + config overlays | Components are containers; file changes are _config/ overlays. |
CMS / signed sw-description | Signed revision (pvr sig) | One signature covers the entire revision. |
| hawkBit deployment server | Pantahub (optional) | Or deploy directly with pvr over the local network. |
Migration path
- Rebuild with
meta-pantavisor. Replacemeta-swupdateand yoursw-descriptioncollections. See Build with Yocto. - Map images to containers. Each image/handler entry becomes a container
(BSP or application) or a
_config/file overlay rather than a partition write. See Concepts and Configure applications. - Flash a Pantavisor image (Install on hardware) and wire up
deployments via
pvror Pantahub.
What changes for your team
- No update script to maintain. The revision manifest describes the whole device declaratively; you do not hand-write per-partition image lists.
- Updates are object-level, so unrelated partitions are not rewritten for a small change. See the benchmarks.
- Rollback is automatic and health-gated rather than dependent on your
sw-descriptionlogic and bootloader scripting.
⚠️ Warning — No hybrid stacks
Do not keep SWUpdate writing the kernel/BSP partitions while Pantavisor handles apps. Pantavisor owns the whole device as a single signed revision.