Yocto bsp bringup
Skill prashantdivate/awesome-yocto-ai-agent-skills/yocto-bsp-bringup
Claude Agent Skills for Yocto Project, OpenEmbedded, and BitBake workflows - AI coding assistant skills for recipes, layers, images, BSPs, SDKs, metadata, QA, sstate, and build troubleshooting.
npx -y skills add prashantdivate/awesome-yocto-ai-agent-skills --skill yocto-bsp-bringupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Yocto BSP and board bring-up skill for AI coding agents. Use for vendor BSP import, machine configuration, layer dependencies, bootloader recipes, trusted firmware, U-Boot, Linux kernel recipes, device trees, defconfigs, KERNEL_DEVICETREE, COMPATIBLE_MACHINE, virtual/kernel providers, storage variants, serial console, first boot, and hardware enablement.
SKILL.md
1.4 KB, as published. Nobody here has run it
Yocto BSP Bring-Up
Workflow
- Identify board, SoC, BSP vendor, Yocto release, kernel version, boot chain, storage medium, and RAM/storage variant.
- Inspect layer structure,
conf/layer.conf,conf/machine/*.conf, andLAYERSERIES_COMPAT. - Confirm collection names with
BBFILE_COLLECTIONS; use collection names inLAYERDEPENDS. - Identify providers for
virtual/kernel, bootloader, trusted firmware, OP-TEE, firmware blobs, and image recipes. - Trace device tree and kernel config from machine config through recipe appends.
- Keep board-specific fixes in the BSP/product layer.
References
- bsp-playbook.md: machine, kernel, bootloader, DTB, and vendor BSP workflows.
Guardrails
- Do not mix machine names across RAM/storage variants.
- Do not copy full vendor recipes when a
.bbappendor config fragment is enough. - Do not assume a layer directory name is the layer collection name.
- Do not change bootloader/kernel provider policy without checking all machines in the layer.