You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Robert Lubos 004fe43b9d net: mqtt: Improve PUBLISH message length validation 1 year ago
.buildkite ci: copy correct junit output 1 year ago
.github ci: add compliance checking via GH actions 1 year ago
.known-issues doc: add .known-issue regex for struct bt_mesh_model_pub warnings 1 year ago
arch arc: fix the bug where regular irq comes out in user mode 7 months ago
boards boards: arm: bl65x_dvk: fix reset not working 1 year ago
cmake toolchain: disable newlib for x86_64 1 year ago
doc release: Update security section for 1.14.2 1 year ago
drivers eth: mcux: Do not set carrier ON if interface is not known 9 months ago
dts dts: arm: nxp: Add dtsi for RT1020 2 years ago
ext ext: lib: mcumgr: Fix slot-1 image upload deadlock condition 7 months ago
include net: gptp: Allow user to tweak priority1 and priority2 values 9 months ago
kernel tracing: swap: bug fix and enhancement for ARC 9 months ago
lib lib/newlib: revert treatment of libc files as system includes 2 years ago
misc license: cleanup: add SPDX Apache-2.0 license identifier 2 years ago
samples random: Include header where it is used 1 year ago
scripts ci: run sanitycheck in verbose mode 1 year ago
soc soc: k64f MPU configured to always allow ENET 2 years ago
subsys net: mqtt: Improve PUBLISH message length validation 3 months ago
tests net: mqtt: Improve PUBLISH message length validation 3 months ago
.checkpatch.conf checkpatch: define typedefsfile to deal with a few false positives 4 years ago
.clang-format clang-format: add support for clang-format 3 years ago
.codecov.yml ci: add .codecov.yml for configuration 4 years ago
.editorconfig editorconfig: Set insert_final_newline true 2 years ago
.gitattributes First commit 6 years ago
.gitignore gitignore: ignore IDE files 3 years ago
.gitlint gitlint: do not start with subsys: 3 years ago
.mailmap mailmap: add entry for ruuddw 3 years ago
.shippable.yml ci: use docker image with 0.10.3 SDK 1 year ago
.uncrustify.cfg uncrustify: Add a rule to remove space inside function argument 3 years ago
CMakeLists.txt scripts: mpu align for ro section of new memory region on non-XIP system 2 years ago
CODEOWNERS codeowner: add scripts/ci 1 year ago coc: move to markdown format 2 years ago
CONTRIBUTING.rst doc: Fixed a link in CONTRIBUTING.rst 2 years ago
Kconfig license: Replace Apache boilerplate with SPDX tag 4 years ago
Kconfig.zephyr kconfig: Move Kconfig.modules to the root build directory 2 years ago
LICENSE add top level Apache 2.0 license file 5 years ago
Makefile doc: add clean target to Makefile 2 years ago
README.rst doc: Fix links to 2 years ago
VERSION release: bump version to Zephyr 1.14.2 1 year ago Introduce cmake-based rewrite of KBuild 4 years ago
west.yml ci: ci-tools: do not mark docs/license as pending 1 year ago
zephyr-env.cmd build: doc: Add support for a Windows equivalent to .zephyrrc 3 years ago shell: Piped output of cd to /dev/null when setting ZEPHYR_BASE. 3 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.

* **Chatting**: You can chat online with the Zephyr project developer
community and other users in two ways:

* On `Slack`_: Zephyr has dedicated channels on Slack. To register, use the
following `Slack Invite`_.

* IRC channel #zephyrproject on the IRC server. You can use the web client or use a client-side application such
as pidgin (Note that all discussions have moved to Slack, although we still
have many developers still available on the IRC channel).

.. _Slack Invite:
.. _Slack:
.. _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: