meta-scobc

Prerequisite

Important

We store .xsa files using Git LFS. Make sure Git LFS is installed; otherwise you won't get the actual .xsa files and the build will fail.

Setup

We use uv to manage the Python environment for kas and related tooling.

$ uv sync
$ source .venv/bin/activate

Build

Builds are managed using kas.

Build command

To build a machine:

$ kas build <kas configuration file>

Example:

$ kas build kas/scobc-v1-sdt.yml

The resulting images will be available under:

build/tmp/deploy/images/<machine>/

Supported Machines

Machine	Machine configuration file	kas configuration file
SC-OBC Module V1 Space Grade	versal-scobc-v1-sdt-full	kas/scobc-v1-sdt.yml
SC-OBC Module V1 Developer Grade	versal-scobc-v1-ve2302e-sdt-full	kas/scobc-v1-devgrade.yml
SC-OBC Module V1 VE2002 Variant	versal-scobc-v1-ve2002e-sdt-full	kas/scobc-v1-devgrade-ve2002.yml

Note

SC-OBC Module V1 VE2002 Variant is not commercially available.

Faster builds (shared caches)

For faster incremental builds, you should keep the downloaded files and the shared state cache. By default, the download directory and the shared state directory are placed under the build directory. This means that when you remove the build directory, those artifacts are removed as well.

Instead, set the DL_DIR and SSTATE_DIR environment variables to fixed locations outside the build directory. This keeps the artifacts available even if you delete and recreate the build directory.

$ export DL_DIR=/opt/yocto/downloads
$ export SSTATE_DIR=/opt/yocto/sstate-cache
$ kas build kas/scobc-v1-sdt.yml