bsp-kernel-build

Builds RDK Linux kernel, device-tree, and driver-module artifacts with mk_kernel.sh.

3|Updated Aug 6, 2026
One-click install
npx skills add https://github.com/D-Robotics/rdk-skills --skill bsp-kernel-build-d-robotics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bsp-kernel-build
Source: https://github.com/D-Robotics/rdk-skills/tree/main/skills/bsp-kernel-build
Command: npx skills add https://github.com/D-Robotics/rdk-skills --skill bsp-kernel-build-d-robotics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a custom kernel, DTB, or driver module for D-Robotics RDK boards (X3/X5) requires the correct board family, configuration source, and build script, and a wrong choice can produce unusable artifacts or an unbootable board. This Skill guides the agent through input collection, build execution, and safe deployment planning for kernel work. ## Core Features & Use Cases - Kernel/DTB/Module Builds: Runs mk_kernel.sh to produce kernel, device-tree, and driver-module artifacts in deploy/kernel, with mk_kernel_rt.sh available for X5 real-time kernels. - Dependency-Aware Routing: Explains that kernel artifacts feed the hobot-boot, hobot-dtb, and hobot-kernel-headers deb packages, and routes full-image work to bsp-image-build and packaging to bsp-deb-build. - Safety Gates: Requires confirmed board variant, config source, deployment target, and rollback method before any boot-partition replacement or reboot. - Use Case: A developer modifies a DTS for an X5 board and needs a new DTB plus kernel headers for out-of-tree module development; the Skill confirms inputs, runs the build, and points to deploy/kernel/kernel_headers. ## Quick Start Ask the agent to build the kernel and device tree for your X5 board using mk_kernel.sh after confirming the board variant and DTS configuration.

Frequently Asked Questions about bsp-kernel-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build the kernel and device tree for an RDK board?▼

Run ./mk_kernel.sh from the workspace root after completing one full image build. It produces the kernel, DTB, and driver modules together in deploy/kernel, including Image, Image.lz4, dtb, modules, and kernel_headers.

How do I build a real-time kernel on the RDK X5?▼

Use ./mk_kernel_rt.sh, which is available only on the X5 board family. The RT kernel changes scheduling behavior on the target, so confirm the switch with the user before starting the long build.

Can I build only a DTB or only driver modules with mk_kernel.sh?▼

No, mk_kernel.sh builds the kernel, DTB, and modules together and there is no narrower DTB-only or module-only command. The individual artifacts are then picked from the deploy/kernel output directory.

Does updating the hobot-dtb package require rebuilding the kernel?▼

Yes, the hobot-dtb, hobot-boot, and hobot-kernel-headers deb packages consume the outputs in deploy/kernel, so the kernel must be rebuilt first. Package creation itself is then handled by the bsp-deb-build skill.

When should I not use mk_kernel.sh for RDK builds?▼

Do not use it for a complete flashable or release image, which belongs to bsp-image-build, or for deb-only package rebuilds, which belong to bsp-deb-build. It also does not cover S-series boards.

Why is a full image build required before building the kernel?▼

The full image build downloads the rootfs whose headers and libraries application packages use, plus the official deb packages. Skipping it leads to missing headers and dependencies during later kernel or module work.