You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
tuxcoder cb4d595b95 tmp 5 years ago
.known-issues doc: known issues: Fix regexes for Windows 5 years ago
arch arch: arm: Use BL instead of B to jump to _PrepC 5 years ago
boards tmp 5 years ago
cmake tmp 5 years ago
doc docs: revamp section introducing Zephyr 5 years ago
drivers tmp 5 years ago
dts gpio: add driver for Intel Apollo Lake SoC 5 years ago
ext ext: lib: Add fnmatch library 5 years ago
include tmp 5 years ago
kernel kernel: stack: Fix k_stack_pop api 5 years ago
lib kernel: Make If statement have essentially Boolean type 5 years ago
misc tmp 5 years ago
samples tmp 5 years ago
scripts shell: Shell subsystem reimplementation 5 years ago
soc gpio: add driver for Intel Apollo Lake SoC 5 years ago
subsys net: context: Select proper network interface when binding 5 years ago
tests samples: subsys: shell: Port sample to new shell subsystem 5 years ago
.checkpatch.conf checkpatch: define typedefsfile to deal with a few false positives 6 years ago
.codecov.yml ci: add .codecov.yml for configuration 6 years ago
.gitattributes First commit 9 years ago
.gitignore Kconfig: Have CMake print a note about the changed 'default' behavior 5 years ago
.gitlint gitlint: use custom rule for line length violations 6 years ago
.mailmap mailmap: add entry for ruuddw 5 years ago
.shippable.yml ci: Print the toolchain database when CI fails 5 years ago
.uncrustify.cfg scripts: cleanup scripts directory 6 years ago
CMakeLists.txt CMakeLists.txt: Set application shared memory dependency 5 years ago
CODEOWNERS CODEOWNERS: Assign maintainers for Nordic SoC .dtsi files 5 years ago
CONTRIBUTING.rst docs: fixed documenation pointers 5 years ago
Kconfig license: Replace Apache boilerplate with SPDX tag 7 years ago
Kconfig.zephyr build: support out of tree SoC definition 5 years ago
LICENSE add top level Apache 2.0 license file 8 years ago
Makefile tmp 5 years ago
README.rst docs: fixed documenation pointers 5 years ago
VERSION release: Post-release patch level update 5 years ago Introduce cmake-based rewrite of KBuild 6 years ago
zephyr-env.cmd scripts: create meta-tool package, "west" 5 years ago env: Remove usage of -P in grep 6 years ago


.. raw:: html

   <a href="">
     <p align="center">
       <img src="doc/images/Zephyr-Project.png">

   <a href=""><img

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`_.

.. below included in doc/introduction/introduction.rst

.. start_include_here

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`_

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 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 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

* **Source Code in GitHub**: Zephyr Project source code is maintained on a
  public GitHub repository at
  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  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

* **Issue Reporting and Tracking**: Requirements and Issue tracking is done in
  the Github issues system:
  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  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

* **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 IRC server. You can use the web
  client or use a client-side application such as pidgin.

.. _supported boards:
.. _Zephyr Documentation:
.. _Zephyr Introduction:
.. _Getting Started Guide:
.. _Contribution Guide:
.. _Zephyr GitHub wiki:
.. _Zephyr Development mailing list:
.. _Zephyr mailing list subgroups:
.. _Sample and Demo Code Examples:
.. _Security Overview: