Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
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.
 
 
 
 
 
 
Sebastian Bøe c7c7917da2 cmake: set IS_TEST in the hello_world sample 8 years ago
.known-issues doc: cleanup .known-issues filters 8 years ago
arch arm: Enable the ARM MPU on the NXP i.MX RT SoC and board 8 years ago
boards mimxrt1050_evk: Fix setting of JLINK_DEVICE 8 years ago
cmake cmake: Refactored EXTRA_FLAGS code into a dedicated script 8 years ago
doc doc: add starter for 1.10 release notes 8 years ago
drivers drivers: crypto: add missing CMakeLists.txt file 8 years ago
dts drivers: i2c: Add DTS support for i2c_sam_twihs driver 8 years ago
ext gpio: Introduce mcux igpio shim driver 8 years ago
include syscalls: REVERTME: clean up warnings when building unit tests 8 years ago
kernel mempool: add assertion for calloc bounds overflow 8 years ago
lib kbuild: Removed KBuild 8 years ago
misc printk: Add padding support to string format specifiers 8 years ago
samples cmake: set IS_TEST in the hello_world sample 8 years ago
scripts scripts: jlink: Don't reset after load 8 years ago
subsys net: lwm2m: fix sending packet w/o token setup when error 8 years ago
tests unittest: Support EXTRA_*_FLAGS 8 years ago
.checkpatch.conf checkpatch: define typedefsfile to deal with a few false positives 8 years ago
.gitattributes First commit 10 years ago
.gitignore doc: report which warnings/errors are new 8 years ago
.gitlint scripts: allow "title" in commit titles 8 years ago
.mailmap mailmap: added axy (for Anas Nashif) 9 years ago
.shippable.yml ci: move doc.warnings up to be evaluated 8 years ago
CMakeLists.txt cmake: Refactored EXTRA_FLAGS code into a dedicated script 8 years ago
CODEOWNERS CODEOWNERS: add cmake owners 8 years ago
CONTRIBUTING.rst CONTRIBUTING.rst: add note about idling on IRC 8 years ago
Kconfig license: Replace Apache boilerplate with SPDX tag 9 years ago
Kconfig.zephyr kconfig: move dts Kconfigs to dts/ 8 years ago
LICENSE add top level Apache 2.0 license file 10 years ago
Makefile build: add top-level Makefile for docs 8 years ago
README.rst doc: update links to new zephyrproject.org site 8 years ago
VERSION cmake: fixed version handling 8 years ago
version.h.in Introduce cmake-based rewrite of KBuild 8 years ago
zephyr-env.sh env: Remove usage of -P in grep 8 years ago

README.rst

Zephyr Project
##############

.. raw:: html

<a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
<img
src="https://api.shippable.com/projects/58ffb2b8baa5e307002e1d79/badge?branch=master">


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

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!

Resources
*********

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. For a quick start, refer to the
`Zephyr Introduction`_ and `Getting Started Guide`_.

* **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
https://zephyrproject.org/doc. Additional documentation is maintained in
the `Zephyr GitHub wiki`_.

* **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 Mailing Lists`_ are perhaps the most convenient
way to track developer discussions and to ask your own support questions to
the Zephyr project community.
You can also read through 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.


.. _supported boards: https://www.zephyrproject.org/doc/boards/boards.html
.. _Zephyr Introduction: https://www.zephyrproject.org/doc/introduction/introducing_zephyr.html
.. _Getting Started Guide: https://www.zephyrproject.org/doc/getting_started/getting_started.html
.. _Contribution Guide: https://www.zephyrproject.org/doc/contribute/contribute_guidelines.html
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Mailing Lists: https://lists.zephyrproject.org/
.. _Sample and Demo Code Examples: https://www.zephyrproject.org/doc/samples/samples.html
.. _Security Overview: https://www.zephyrproject.org/doc/security/security-overview.html