‹ 首页

board-bringup

@beriberikix · 收录于 昨天 · 上游提交 2 个月前

Custom board bringup for Zephyr RTOS using Hardware Model v2 (HWMv2). Covers directory structure, board.yml metadata, core configuration files (Kconfig, defconfig, CMake), and revision management. Trigger when creating new board definitions or porting Zephyr to custom hardware.

场景嵌入式开发硬件移植

适合你，如果需要在 Zephyr RTOS 中为新硬件定义板级配置

/ 下载安装
https://github.com/beriberikix/zephyr-agent-skills/tree/main/skills/board-bringup ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add beriberikix/zephyr-agent-skills/board-bringup
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- beriberikix/zephyr-agent-skills/board-bringup
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify beriberikix/zephyr-agent-skills/board-bringup
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
58GitHub stars
~507最小装载
~1.5K含声明引用
~1.6K文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 ed63cdf · 表述以原文为准
它做什么

依据 Zephyr RTOS 的 Hardware Model v2 标准，指导你创建或移植自定义板卡定义，包括组织目录结构、填写 board.yml 元数据、配置 Kconfig、defconfig 和 CMake 文件，并管理硬件修订版本。

什么时候触发

当你需要为自定义硬件创建新的 Zephyr 板卡定义，或将 Zephyr 移植到自定义硬件上时触发。

装好后可以这样说
技能原文 SKILL.md作者撰写 · Apache-2.0 · ed63cdf

Zephyr Board Bringup (HWMv2)

Bring your custom hardware into the Zephyr ecosystem using modern Hardware Model v2 standards.

Core Workflows
1. Planning the Structure

Organize your board files by vendor and board name.

  • Reference: [hwmv2_structure.md](references/hwmv2_structure.md)
  • Key Tools: board.yml, naming conventions.
2. Defining Configuration

Implement the essential Kconfig and CMake logic.

  • Reference: [board_files.md](references/board_files.md)
  • Key Tools: Kconfig.board, _defconfig, CMakeLists.txt.
3. Managing Revisions & Variants

Handle hardware iterations and SoC variants cleanly.

  • Reference: [hwmv2_structure.md](references/hwmv2_structure.md#revision-management)
  • Key Tools: Multi-revision board.yml, revision-specific overlays.
Quick Start (Board Skeleton)
boards/<vendor>/<board>/
  board.yml
  <board>_defconfig
  <board>.dts
  Kconfig.board
  Kconfig.defconfig
  CMakeLists.txt
Validation Checklist
  • [ ] board.yml defines board name, SoC, and revisions consistently.
  • [ ] west build -b <board> samples/hello_world completes successfully.
  • [ ] DTS and defconfig settings are applied in the generated build output.
  • [ ] Revision-specific overlays are selected correctly when building a non-default revision.
Automation Tools
  • [board_yaml_lint.py](scripts/board_yaml_lint.py): Validate basic board.yml structure and naming conventions.
Examples & Templates
  • [board_yml_template.yml](assets/board_yml_template.yml): Starter board.yml for HWMv2 board metadata.
Best Practices
  • Use _common.dtsi: Share devicetree definitions across all board revisions.
  • Follow HWMv2: Avoid the legacy board structure (Kconfig.defconfig, etc.).
  • Keep it minimal: Only define what is unique to the board; let the SoC files handle chip-level configuration.
Resources
  • [References](references/):
  • hwmv2_structure.md: Directory layout and board.yml.
  • board_files.md: Kconfig, defconfig, and CMake configuration.
  • [Scripts](scripts/):
  • board_yaml_lint.py: Structural checker for board metadata.
  • [Assets](assets/):
  • board_yml_template.yml: Minimal board metadata template.
按 Apache-2.0 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…