agentleFS
Sign inStart free
D-RoboticsD-Robotics/rdk-skills/skills/bsp-bootloader-build/SKILL.md

bsp-bootloader-build

Skill5 starsChanged 3 months agoApache-2.0View on GitHub

Build the minimal boot image (miniboot / nand_disk.img) from the bootloader source using xbuild.sh lunch — covers selecting the board config and compiling uboot/miniboot for RDK X5. Use when the user wants to rebuild bootloader/miniboot, asks what nand_disk.img is, or needs a custom minimal boot firmware. 触发词:miniboot、bootloader、uboot、nand_disk.img、xbuild、最小启动镜像. Do not use for kernel or full image builds; X3 flow is not yet documented — say so instead of guessing.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Verify the outputs under out/product/: nand_disk.img (the minimal boot image), uboot.img, miniboot_all.img.

    line 56
  2. Distinctive:

    Never flash or replace locally built bootloader data without user confirmation, the selected board and boot medium, a recovery plan …

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Bootloader / miniboot Build

Purpose

Build the RDK minimal boot firmware (miniboot.img / nand_disk.img): the image containing the partition table, spl, ddr, bl31, and uboot that runs before the OS. This is the most foundational BSP component — modifying it requires understanding the boot process.

When to use

Use when:

  • The user wants to rebuild the bootloader / miniboot for RDK X5
  • Explaining what nand_disk.img / miniboot_all.img are
  • The user needs a custom minimal boot firmware

Do not use:

  • For X3 — the bootloader build steps for X3 are not documented in the official build README; say so and point to official docs rather than guessing
  • For kernel/image builds — sibling skills

Instructions

  1. Preflight before any build or flash command. Confirm the X5 board variant, boot medium (SD, eMMC, or NAND), the exact boot-logo or bootloader change, a known-good recovery method, and the location of a backup of the current boot artifact. For an immediate flash or replacement request, stop here: flashing bootloader data is irreversible until the target medium and recovery path are confirmed. Route normal OS-image branding or customization to bsp-image-build instead.
  2. Prerequisites after the preflight passes: bsp-source-sync completed; source/bootloader present.
  3. Select the board config:
    cd source/bootloader/build
./xbuild.sh lunch
    The lunch menu offers (X5):
    0. rdk/x5/board_x5_rdk_ubuntu_nand_sdcard_debug_config.mk
1. rdk/x5/board_x5_rdk_ubuntu_nand_sdcard_release_config.mk
    lunch also accepts a number or the config file name:
    ./xbuild.sh lunch 0
./xbuild.sh lunch board_x5_rdk_ubuntu_nand_sdcard_debug_config.mk
  4. Build everything:
    ./xbuild.sh
  5. Verify the outputs under out/product/: nand_disk.img (the minimal boot image), uboot.img, miniboot_all.img. Building does not authorize flashing.
  6. Note for the user: official releases maintain miniboot — downloadable from https://archive.d-robotics.cc/downloads/miniboot/ (the hobot-miniboot package follows the same versions). Rebuilding is only needed for bootloader customization.

Safety

  • Bootloader bugs brick boards: recommend against rebuilding unless the user explicitly needs it; always remind them official miniboot images exist.
  • Never flash or replace locally built bootloader data without user confirmation, the selected board and boot medium, a recovery plan (official miniboot at hand), and a backup of the current artifact.
  • Quote the lunch menu verbatim; do not invent configs for boards not listed.

Sources: x5-rdk-gen README v3.5.0「编译 bootloader」。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free