zephyrproject-rtos/example-application

Example out-of-tree application that is also a module

Hosted by Linux Foundation

View on GitHub ↗Jump to charts ↓

zephyrproject-rtos/example-application has 350+ stars and 200+ forks on GitHub, is written in C, and was last pushed on Sep 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 13 minutes ago
Type:Template / ExampleCategory(s):Embedded & IoTSystems, Hardware & HPC
Added to GitGenius on October 15th, 2026
Created on January 12th, 2021
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 237
Total Stargazers: 365 (+0)
Total Subscribers: 77 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Zephyr Example Application is a reference implementation that demonstrates how to structure out-of-tree applications and modules for the Zephyr RTOS.

The project addresses the need for developers to understand best practices when building applications on Zephyr. It provides a working template that shows how to organize code, configure builds, and integrate with the Zephyr ecosystem. The example demonstrates workspace applications, custom board definitions, out-of-tree drivers and libraries, devicetree bindings, and west extensions, allowing developers to see these patterns in a concrete, buildable form rather than in documentation alone.

Developers should use this repository as a starting point when creating new Zephyr projects or when learning how to structure applications for the platform. It suits teams building embedded systems on Zephyr who want to follow established patterns for modularity and maintainability. The repository is versioned in lockstep with Zephyr itself, so the example always reflects the current state of the framework and remains compatible with the version of Zephyr it targets.

The project maintains active CI workflows that validate both the build process and documentation generation on every push. The repository includes comprehensive documentation setup with both Doxygen for API documentation and Sphinx for user-facing guides, demonstrating how to document Zephyr projects properly. Development activity shows consistent attention to keeping the example synchronized with Zephyr's evolution and ensuring that the demonstrated patterns remain current and functional.