# Qemu Uboot Build

> Use for building U-Boot artifacts for QEMU firmware boot testing, including defconfig selection, cross compile variables, SPL/TPL, U-Boot proper, FIT or ITB files, BL31 or TF-A dependencies, logs, hashes, and provenance.

- **Type:** Skill
- **Install:** `agentstack add skill-processmission-oh-my-qemu-qemu-uboot-build`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [processmission](https://agentstack.voostack.com/s/processmission)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [processmission](https://github.com/processmission)
- **Source:** https://github.com/processmission/oh-my-qemu/tree/main/.agents/skills/qemu-uboot-build
- **Website:** https://processmission.github.io/oh-my-qemu/

## Install

```sh
agentstack add skill-processmission-oh-my-qemu-qemu-uboot-build
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# QEMU U-Boot Build

Use this workflow when a QEMU task needs U-Boot, SPL, TPL, FIT, ITB, or firmware-chain artifacts.

## Primitive Composition

1. Use `qemu-flow-plan` for the task workspace.
2. Use `qemu-source-provenance` for U-Boot and every external binary input.
3. Build with the local U-Boot tree's board documentation.
4. Update `source-provenance.md` with all boot-stage outputs and hashes.
5. Hand off to `qemu-image-packaging` or `qemu-firmware-linux-boot`.

## Build Flow

Record:

- U-Boot source path, revision, and dirty state;
- board defconfig and any config fragments;
- architecture, cross compiler prefix, compiler version, and output directory;
- external dependencies such as BL31, TEE, firmware blobs, device trees, or DDR init binaries;
- output artifacts such as `spl/u-boot-spl`, `u-boot`, `u-boot.bin`, `u-boot.itb`, or platform-specific combined images;
- exact command, log path, and hashes.

## Command Shape

Use local documentation first. Typical U-Boot patterns are:

```bash
make O= 
make O= CROSS_COMPILE= -j$(nproc)
```

If a firmware chain requires environment variables such as `BL31`, record their resolved paths and hashes before building.

## Output Rules

- Treat each boot stage as a separate provenance item.
- Do not assume a combined image contains the expected stage; inspect and record the packaging command.
- If firmware reaches U-Boot but Linux does not boot, separate U-Boot command/environment issues from QEMU model issues.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [processmission](https://github.com/processmission)
- **Source:** [processmission/oh-my-qemu](https://github.com/processmission/oh-my-qemu)
- **License:** MIT
- **Homepage:** https://processmission.github.io/oh-my-qemu/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-processmission-oh-my-qemu-qemu-uboot-build
- Seller: https://agentstack.voostack.com/s/processmission
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.