How zephyrproject-rtos/example-application works
Main Components
a) Application Layer
• Main application code (/app)
• Board-specific configurations
• Custom configurations (prj.conf, debug.conf)
b) Driver Layer
• Custom LED driver (drivers/blink)
• Custom sensor driver (drivers/sensor/example_sensor)
• Device Tree bindings (dts/bindings)
c) Library Layer
• Custom library implementation (lib/custom)
• Headers (include/app)
d) Testing Framework
• Test cases (tests/lib)
• Integration tests
e) Build & Tools Layer
• West extension (scripts/example_west_command.py)
• Custom runner (scripts/example_runner.py)
• CMake build system
• Documentation generation
┌─────────────────────────────────────────────────────┐
• Application Layer │
• ┌─────────────┐ ┌────────────┐ ┌───────────────┐ │
• App Core │ │ Boards │ │ Configuration │ │
• ┘ └────────────┘ └───────────────┘ │
• ┤
• Driver Layer │
• ┌─────────────┐ ┌────────────┐ ┌───────────────┐ │
• LED Driver │ │ Sensor │ │ DTS Bindings │ │
• ┘ └────────────┘ └───────────────┘ │
• ┤
• Library Layer │
• ┌─────────────────────┐ ┌───────────────────────┐ │
• Custom Library │ │ Include Headers │ │
• ┘ └───────────────────────┘ │
• ┤
• Zephyr RTOS Core │
• ┘
Additional Elements
• Version information (from app/VERSION)
• Documentation generation flow
• CI/CD integration points
Relationships to Emphasize
• How custom drivers interact with the Zephyr RTOS
• How the application uses custom libraries
• How board configurations affect the system
• How West extensions integrate with the build system