Appearance
Choose a Dataplicity OS image #
Dataplicity OS provides a small catalog of official factory images. Choose the entry that exactly matches the board you will flash. Compute Module 5 with eMMC on the official CM5 IO board is the first supported target.
The catalog is deliberately not a general board-support matrix. Use a custom image when your product needs another board, BSP, kernel, bootloader, partition layout, package set, or security policy.
| Image path | Dataplicity provides | You own |
|---|---|---|
| Official Dataplicity OS | A versioned factory image and its matching signed OTA release for a listed platform | Hardware qualification, commissioning, application software, and rollout approval |
| Custom image | Agent integration guidance and optional Device Class OS-image delivery | The complete image build, BSP, update design, signing trust, testing, and release cadence |
Factory flash and OTA are different #
A factory image is a compressed disk image used to initialise blank storage. It creates the partition table, both RAUC root filesystem slots, boot partitions, and persistent dpdata partition.
An OTA release is a signed .raucb installed on a device that already has the qualified A/B layout. The current Dataplicity OS bundle updates the inactive root filesystem only. It does not update the boot, kernel, or firmware partitions. Delivering changes to those partitions requires a separately designed and qualified bundle layout.
Choose before manufacturing #
- Confirm the exact board and storage variant.
- Select an official catalog image only when its platform matches.
- Flash and qualify the factory image on production-equivalent hardware.
- Use the corresponding official OTA line for later root filesystem updates.
- For other hardware, start a custom image integration rather than relabelling an official image.
Continue with Use Dataplicity OS on Compute Module 5 or Integrate Dataplicity with your Linux image.