Quick Start Guide

There are two ways to get started: use a prebuilt image for your target, or build your own using the Bunker Development Framework.

Option A - Use a prebuilt image

If you have a physical board, download the prebuilt WIC/SD image for your target and flash the WIC image directly using Balena Etcher or dd. Refer to the platform-specific guide for the exact image to download and deployment steps, for example:

If you don’t have the physical hardware you can also try the QEMU ARM64 generic configuration:

Browse the platform directory for other supported boards and images.

Option B - Build from source

Prerequisites

Before starting the build process, ensure you have:

  • Linux host (Ubuntu 20.04+ recommended)

  • Disk space: 100+ GB (Yocto builds are large)

  • RAM: 16+ GB minimum, 32+ GB recommended

  • Tools installed:

    sudo apt-get install -y git curl wget python3 python3-pip build-essential \
  chrpath socat cpio texinfo diffstat unzip zstd lz4 zlib1g-dev

Furthermore, CLARE-Hypervisor is the core component that manages isolation between Bunker OS and Open World. Before building, you must obtain the hypervisor binary.

Option 1: Pre-built Hypervisor (Trial/Non-Commercial)

Download a pre-built trial hypervisor binary from the Accelerat Customer Hub.

Option 2: Custom Build (Licensed)

If you have a CLARE-Hypervisor or a CLARE-Toolkit license, configure your own build according to provided license terms.

Get the Source and Build

KAS is used to orchestrate source fetch and builds. The KAS configuration and instructions live in the bunker-kas-conf repository.

In order to get started, clone bunker-kas-conf repository and create project directory:

git clone <manifest-repo>
mkdir new-project

Then, place CLARE-Hypervisor binary in the project folder:

cd new-project
mkdir clare-hypervisor
cp /path/to/CLARE-Hypervisor.bin clare-hypervisor/uCLARE

Finally, run kas build from inside your project folder

cd new-project
kas build ../bunker-kas-conf/<machine>.conf

KAS will fetch and assemble the Yocto layers and then run the BitBake build according to the provided configuration. Build times vary: first build is typically hours, subsequent builds are faster when cached.

When build is completed, following set of artifacts will be produced (and typically stored in tmp/deploy/images/<MACHINE>/):

  • Boot files (boot binary, op-tee, boot.scr, Image)

  • Bunker OS root filesystem

  • Open World root filesystem

  • WIC images (ready to flash to SD card)

After that, flash the WIC image or copy the individual boot artifacts to your SD card as required by the target platform.

Refer to the platform guide for the exact files, boot mode settings and consult the platform-specific documentation for device-tree, serial-console details and other information about image configuration.

Next Steps