Zephyr: West Manifest For Application Development
In this blog post, I show a simpler way to create custom West manifest files. This technique eliminates the need to duplicate the complex West manifest from upstream Zephyr. I also show how we can use the West manifest to include out-of-tree board and SoC definitions, and include our own out-of-tree drivers.
Summary
This blog post demonstrates a simpler approach to authoring West manifest files for Zephyr-based projects, avoiding duplication of the upstream manifest. It shows how to reference upstream repositories while adding out-of-tree board, SoC, and driver definitions so engineers can keep project manifests minimal and maintainable.
Key Takeaways
- Create compact custom West manifests that reference upstream Zephyr to avoid duplicating complex manifests.
- Include out-of-tree board and SoC definitions via manifest entries instead of copying upstream files.
- Organize and reference out-of-tree drivers in the manifest so they integrate seamlessly with Zephyr builds.
- Integrate manifest-based repository references into CI/build workflows to simplify multi-repo project management.
Who Should Read This
Embedded firmware and platform engineers with some Zephyr or RTOS experience who want to simplify project manifests, integrate out-of-tree boards/SoCs, and manage custom drivers and CI.
Still RelevantIntermediate
Related Documents
- Consistent Overhead Byte Stuffing TimelessIntermediate
- PID Without a PhD TimelessIntermediate
- Introduction to Embedded Systems - A Cyber-Physical Systems Approach Still RelevantIntermediate
- Can an RTOS be really real-time? TimelessAdvanced
- Memory Mapped I/O in C TimelessIntermediate
