Skip to main content
Version: 029-rc4

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.

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. Flashing NXP devices — the UUU factory-flash archive recipe (Toradex, Variscite, NXP MEK): design, PV_FLASH_* variables, and how to wire up a new machine

Build Guide​

  1. Get Started — prerequisites, repository setup, git worktrees, and your first KAS build
  2. Supported Devices — machines supported and built by CI
  3. Pantavisor Development — build against a local pantavisor source checkout using the workspace overlay
  4. Container Development — author and iterate on app containers: recipe structure, pvrexport, and local testing
  5. Manifest Audit — audit rootfs content with pv-manifest-audit and enforce strict mode
  6. Component Docs — generate per-component documentation tarballs from the build
  7. 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