C C++ Python Assembly CMake Perl
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
.known-issues doc: known issues: Fix regexes for Windows Jul 13, 2018
arch arch/mcimx7_m4: Add i.MX7 Solo Kconfig SoC partnumber define Aug 21, 2018
boards boards: Add support for WaRP7 board Aug 21, 2018
cmake cmake: change policy CMP0000 to NEW Aug 15, 2018
doc doc: add tracing section Aug 21, 2018
drivers drivers: sensors: adxl372: Add driver for ADXL372 high-g accelerometer Aug 22, 2018
dts dts: Fix cmake warning about missing id field for fsl,imx7d-i2c Aug 21, 2018
ext ext/hal/nxp/imx: Add all UARTs clock frequency information Aug 21, 2018
include systemview: add support natively using tracing hooks Aug 21, 2018
kernel systemview: add support natively using tracing hooks Aug 21, 2018
lib lib: cmsis_rtos_v1: fix couple of nonconformities Aug 21, 2018
misc Kconfig: Use a short, consistent style for prompts Aug 15, 2018
samples samples: sensor: adxl372: Add ADXL372 sample application Aug 22, 2018
scripts sanitycheck: Overcommit the default number of jobs Aug 19, 2018
subsys Bluetooth: GATT: Make CCC cfg_changed optional Aug 21, 2018
tests tests: qmsi: remove soc watch sample Aug 21, 2018
.checkpatch.conf checkpatch: define typedefsfile to deal with a few false positives Oct 9, 2017
.codecov.yml ci: add .codecov.yml for codecov.io configuration Jan 3, 2018
.gitattributes First commit Apr 10, 2015
.gitignore Kconfig: Have CMake print a note about the changed 'default' behavior Aug 10, 2018
.gitlint gitlint: use custom rule for line length violations Feb 7, 2018
.mailmap mailmap: add entry for ruuddw Jul 5, 2018
.shippable.yml ci: Handle errors and exit on them Aug 16, 2018
.uncrustify.cfg scripts: cleanup scripts directory Apr 3, 2018
CMakeLists.txt linker: Re-implement {APP,KERNEL}_INPUT_SECTION Aug 17, 2018
CODEOWNERS codeowners: Assign tests/boards/native_posix to aescolar Aug 1, 2018
CONTRIBUTING.rst doc: simplify CONTRIBUTING, merge non-apache Jul 27, 2018
Kconfig license: Replace Apache boilerplate with SPDX tag Jan 19, 2017
Kconfig.zephyr Kconfig: Switch to improved globbing statements Aug 15, 2018
LICENSE add top level Apache 2.0 license file Feb 6, 2016
Makefile doc: Makefile: Switch to Ninja as a generator Jul 19, 2018
README.rst doc: Correct arch spellings in README.rst Aug 2, 2018
VERSION release: Post-release patch level update Jun 11, 2018
version.h.in Introduce cmake-based rewrite of KBuild Nov 9, 2017
zephyr-env.cmd scripts: create meta-tool package, "west" May 19, 2018
zephyr-env.sh env: Remove usage of -P in grep Jul 15, 2017


The Zephyr Project is a scalable real-time operating system (RTOS) supporting multiple hardware architectures, optimized for resource constrained devices, and built with security in mind.

The Zephyr OS is based on a small-footprint kernel designed for use on resource-constrained systems: from simple embedded environmental sensors and LED wearables to sophisticated smart watches and IoT wireless gateways.

The Zephyr kernel supports multiple architectures, including ARM Cortex-M, Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V, and a large number of supported boards.

Getting Started

To start developing Zephyr applications refer to the Getting Started Guide in the Zephyr Documentation pages. A brief introduction to Zephyr can be found in the Zephyr Introduction page.

Community Support

The Zephyr Project Developer Community includes developers from member organizations and the general community all joining in the development of software within the Zephyr Project. Members contribute and discuss ideas, submit bugs and bug fixes, and provide training. They also help those in need through the community's forums such as mailing lists and IRC channels. Anyone can join the developer community and the community is always willing to help its members and the User Community to get the most out of the Zephyr Project.

Welcome to the Zephyr community!


Here's a quick summary of resources to find your way around the Zephyr Project support systems:

  • Zephyr Project Website: The https://zephyrproject.org website is the central source of information about the Zephyr Project. On this site, you'll find background and current information about the project as well as all the relevant links to project material.

  • Releases: Source code for Zephyr kernel releases are available at https://zephyrproject.org/developers/#downloads. On this page, you'll find release information, and links to download or clone source code from our GitHub repository. You'll also find links for the Zephyr SDK, a moderated collection of tools and libraries used to develop your applications.

  • Source Code in GitHub: Zephyr Project source code is maintained on a public GitHub repository at https://github.com/zephyrproject-rtos/zephyr. You'll find information about getting access to the repository and how to contribute to the project in this Contribution Guide document.

  • Samples Code: In addition to the kernel source code, there are also many documented Sample and Demo Code Examples that can help show you how to use Zephyr services and subsystems.

  • Documentation: Extensive Project technical documentation is developed along with the Zephyr kernel itself, and can be found at http://docs.zephyrproject.org. Additional documentation is maintained in the Zephyr GitHub wiki.

  • Cross-reference: Source code cross-reference for the Zephyr kernel and samples code is available at https://elixir.bootlin.com/zephyr/latest/source.

  • Issue Reporting and Tracking: Requirements and Issue tracking is done in the Github issues system: https://github.com/zephyrproject-rtos/zephyr/issues. You can browse through the reported issues and submit issues of your own.

  • Security-related Issue Reporting and Tracking: For security-related inquiries or reporting suspected security-related bugs in the Zephyr OS, please send email to vulnerabilities@zephyrproject.org. We will assess and fix flaws according to our security policy outlined in the Zephyr Project Security Overview.

    Security related issue tracking is done in JIRA. The location of this JIRA is https://zephyrprojectsec.atlassian.net.

  • Mailing List: The Zephyr Development mailing list is perhaps the most convenient way to track developer discussions and to ask your own support questions to the Zephyr project community. There are also specific Zephyr mailing list subgroups for announcements, builds, marketing, and Technical Steering Committee notes, for example. You can read through the message archives to follow past posts and discussions, a good thing to do to discover more about the Zephyr project.

  • IRC Chatting: You can chat online with the Zephyr project developer community and other users in our IRC channel #zephyrproject on the freenode.net IRC server. You can use the http://webchat.freenode.net web client or use a client-side application such as pidgin.