Source Tree Structure
Understanding the Zephyr source tree can be helpful in locating the code associated with a particular Zephyr feature.
The Zephyr source tree provides the following top-level directories, each of which may have one or more additional levels of subdirectories which are not described here.
archArchitecture-specific kernel and system-on-chip (SoC) code. Each supported architecture (for example, x86 and ARM) has its own subdirectory, which contains additional subdirectories for the following areas:
- architecture-specific kernel source files
- architecture-specific kernel include files for private APIs
- SoC-specific code
boards- Board related code and configuration files.
doc- Zephyr documentation source files and tools.
drivers- Device driver code.
ext- Externally created code that has been integrated into Zephyr from other sources, such as hardware interface code supplied by manufacturers and cryptographic library code.
fs- File system code.
include- Include files for all public APIs, except those defined under
lib. kernel- Architecture-independent kernel code.
lib- Library code, including the minimal standard C library.
misc- Miscellaneous code that doesn’t belong to any of the other top-level directories.
net- Networking code, including the Bluetooth stack and networking stacks.
samples- Sample applications that demonstrate the use of Zephyr features.
scripts- Various programs and other files used to build and test Zephyr applications.
tests- Test code and benchmarks for Zephyr features.
usb- USB device stack code.