SKILL verified MIT Self-run

Qemu Uboot Build

Name: Qemu Uboot Build
Availability: InStock
Author: processmission

skill-processmission-oh-my-qemu-qemu-uboot-build · by processmission

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.

↗ Website ↗ Repository

— No reviews yet

0 installs

8 views

0.0% view→install

Install

$ agentstack add skill-processmission-oh-my-qemu-qemu-uboot-build

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

✓ Prompt-injection patterns
✓ Secret / credential exfiltration
✓ Dangerous shell & filesystem operations
✓ Untrusted network calls
✓ Known-malicious package signatures

What it can access

✓ Network access No
✓ Filesystem access No
✓ Shell / process execution No
✓ Environment & secrets No
✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Qemu Uboot Build? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.

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

Use qemu-flow-plan for the task workspace.
Use qemu-source-provenance for U-Boot and every external binary input.
Build with the local U-Boot tree's board documentation.
Update source-provenance.md with all boot-stage outputs and hashes.
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:

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
Source: 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.

Reviews

No reviews yet — be the first.

Write a review

Versions

v0.1.0 Imported from the upstream source.