Skip to content

Choose a Dataplicity OS image #

Dataplicity OS provides a small catalog of official factory images for quickstart and reference use. 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.

Most shipping products still bring their own Linux image. The catalog is deliberately not a general board-support matrix. Use Integrate your Linux image when your product needs another board, BSP, kernel, bootloader, partition layout, package set, or security policy.

Image pathDataplicity providesYou own
Official Dataplicity OSA versioned factory image and its matching signed OTA release for a listed platformHardware qualification, commissioning, application software, camera overlay fit, and rollout approval
Your Linux imageAgent integration guidance and optional Device Class OS-image deliveryThe complete image build, BSP, update design, signing trust, testing, and release cadence

Official signed releases publish a production-profile image by default. Staging can also publish an explicit debug channel image for diagnostics. Do not flash the debug channel onto customer or manufacturing units. See Build and customise Dataplicity OS for the lab versus staging versus production differences.

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 #

  1. Confirm the exact board and storage variant.
  2. Select an official catalog image only when its platform matches.
  3. Flash and qualify the factory image on production-equivalent hardware.
  4. Use the corresponding official OTA line for later root filesystem updates.
  5. 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.