agentleFS
D-RoboticsD-Robotics/dsh-plugin-rdk/skills/bsp-skills/bsp-source-sync/SKILL.md

bsp-source-sync

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

Sync the RDK Linux source tree (kernel, bootloader, hobot-* package sources) using repo and the official manifests — X5 uses D-Robotics/x5-manifest, X3 uses D-Robotics/manifest. Use when the user wants to download/checkout the BSP source, switch branches, or repo init/sync fails. 触发词:repo init、repo sync、同步源码、下载源码、manifest、源码树、develop 分支. Do not use for building after the source is ready (bsp-image-build and later skills), or for S-series source acquisition (bsp-s-series).

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, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    After the sync, the build workspace contains the rdk-gen scripts plus a source/ tree (bootloader, hobot-boot, hobot-dtb, …

    line 53
  2. Very specific:

    Never mix manifests in one workspace — check .repo/manifests.git origin before re-init.

    line 60

≈ “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

BSP Source Sync

Purpose

Bring down the full RDK Linux source tree — kernel, bootloader, and all hobot-* package sources — so the other bsp-* skills can build from it. The entry point is the Google repo tool plus a board-specific manifest.

When to use

Use when:

  • Starting a new BSP workspace (repo init / repo sync)
  • Switching between the main (stable, matches the latest released image) and develop (rolling) branches
  • repo sync fails or the user asks where the source lives

Do not use:

  • For S-series source acquisition — bsp-s-series
  • For building once sources exist — bsp-image-build etc.

Instructions

  1. Confirm the target board first: X5 → x5-manifest, X3 → manifest. The manifests are different; mixing them breaks the workspace.
  2. Prerequisites (from bsp-env-setup): GitHub SSH key registered, repo installed.
  3. Optional but recommended in China: switch repo to the Tsinghua mirror:
    export REPO_URL='https://mirrors.tuna.tsinghua.edu.cn/git/git-repo/'
  4. Initialize the manifest (main line matches the latest officially released image version):
    # RDK X5
    repo init -u git@github.com:D-Robotics/x5-manifest.git -b main
    # RDK X3
    repo init -u git@github.com:D-Robotics/manifest.git -b main
  5. Sync the code:
    repo sync
  6. After the sync, the build workspace contains the rdk-gen scripts plus a source/ tree (bootloader, hobot-boot, hobot-dtb, hobot-kernel-headers, hobot-* packages, kernel). Report what landed and where.
  7. Branch guidance: -b develop gets the rolling development line (new features and fixes, less stable than main). Mention this when the user asks for the newest code.

Safety

  • repo init writes a .repo/ workspace and network volume is large: confirm disk space (tens of GB) and the working directory with the user first.
  • Never mix manifests in one workspace — check .repo/manifests.git origin before re-init.
  • Cloning uses SSH (git@github.com): if it fails with permission errors, that is a GitHub SSH-key problem (see bsp-env-setup), not a manifest problem.

Sources: x5-rdk-gen README v3.5.0「下载源码」chapter; rdk-gen README v3.0.3「下载源码」chapter.

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.