Skip to main content
Version: master

Structure

meta-pantavisor is the Yocto/OpenEmbedded layer that builds Pantavisor-based BSP images for embedded Linux. It provides recipes, BitBake classes, and KAS configurations for producing initramfs images and container pvrexport bundles.

This section covers the project structure, build system architecture, and how the layer is organized. Start here, then follow the build guide below.

Just want to deploy your own container onto an existing device? Skip the build guide — grab a ready-made image via Starter Image / Flashing Images and go straight to Develop applications. The build guide below is for building your own custom image from source.

Coming from Buildroot, Mender, RAUC, or another build/update system? See Benchmarks for a direct comparison before committing to the Yocto/BitBake build guide below.

Topics​

  1. Layer Layout — directory structure, key recipes, BitBake classes, PANTAVISOR_FEATURES, and Yocto compatibility
  2. Build System — KAS configuration hierarchy, multiconfig architecture, build outputs, and the relationship between targets
  3. Starter Image — how pantavisor-starter composes core containers with the BSP into the initial device trail
  4. Flashing Images — where to get a ready-made image (pantavisor.io/downloads), pvflasher, and which flashing method applies to your board
  5. Boot Flow — how boot.cmd.pvgeneric boots Pantavisor: FIT/trail loading, try-boot, MMC vs NAND/UBIFS, and PV_BOOT_OEMARGS
  6. USB factory-flash bundle — the over-USB factory-flash archive recipe (Toradex, Variscite, NXP MEK via UUU; Rockchip via rkdeveloptool): design, PV_FLASH_* variables, and how to wire up a new machine
  7. Lab controller container (pv-labutils) — the pv-labutils container recipe: package split, GPIO reset/recovery control (pv-gpio-set, raspi-gpio), and mdev device-access rules

Build Guide​

  1. Get Started — prerequisites, repository setup, git worktrees, and your first KAS build
  2. Managing Layers with repo — fold meta-pantavisor into an existing repo/manifest.xml multi-layer workflow
  3. Supported Devices — machines supported and built by CI
  4. Pantavisor Development — build against a local pantavisor source checkout using the workspace overlay
  5. Container Development — author and iterate on app containers: recipe structure, pvrexport, and local testing
  6. Manifest Audit — audit rootfs content with pv-manifest-audit and enforce strict mode
  7. Component Docs — generate per-component documentation tarballs from the build
  8. Bootchartd — enable boot performance profiling with bootchartd in Pantavisor images

Continuous Integration​

  • Continuous Integration — CI system overview, machine matrix, release builds, tag sync, and docs publishing

Also in this section​

  • Porting Pantavisor — add support for a new board: platform and machine KAS files, CI registration, and building.
  • Composable Firmware — what "composable firmware" actually means here.
  • Examples — worked xconnect and pvwificonnect examples.
  • Testing — development and automated test workflows.
  • Glossary — every term used throughout these docs, defined in one place.