Go to file
2018-02-01 21:43:28 +01:00
.known-issues doc: add missing API content 2017-12-01 08:58:56 -05:00
arch spi: use pinmux to configure the pins. 2018-02-01 21:43:23 +01:00
boards boards: enable the SPI ports on mysensors_gw. 2018-02-01 21:43:24 +01:00
cmake cmake: give an assert a useful message 2018-01-29 14:32:01 +01:00
doc doc: user mode overview documentation 2018-01-30 10:32:39 -08:00
drivers spi: sam0: fix txrx, NULL buffers, and add a stub async method. 2018-02-01 21:43:24 +01:00
dts spi: sam0: use Device Tree for configuration. 2018-02-01 21:43:23 +01:00
ext mbedtls: Added support for using an externally built mbedtls 2018-01-29 23:46:15 -05:00
include Merge branch 'bytewise_crc16' into dev_sdhc 2018-02-01 21:43:28 +01:00
kernel kernel: Allow late processing of timeouts 2018-01-29 23:18:13 -05:00
lib crc: add crc16_itu_t which is used in the MMC protocol. 2018-02-01 21:39:38 +01:00
misc config: bootloader: Add support for MCUboot 2018-01-29 18:05:18 -05:00
samples samples: net: Add config and enable CI for OpenThread on nRF52840 2018-01-29 22:42:03 -05:00
scripts scripts: jlink: Do not mass erase flash by default 2018-01-30 11:09:06 -06:00
subsys disk: add a SDHC card over SPI driver. 2018-02-01 21:43:22 +01:00
tests Merge branch 'bytewise_crc16' into dev_sdhc 2018-02-01 21:43:28 +01:00
.checkpatch.conf checkpatch: define typedefsfile to deal with a few false positives 2017-10-09 10:43:05 -04:00
.codecov.yml ci: add .codecov.yml for codecov.io configuration 2018-01-03 13:12:03 -05:00
.gitattributes First commit 2015-04-10 16:44:37 -07:00
.gitignore doc: report which warnings/errors are new 2017-11-13 17:45:42 -05:00
.gitlint gitlint: do not allow title-only commit messages 2018-01-11 06:39:42 -05:00
.mailmap mailmap: added axy (for Anas Nashif) 2016-12-21 13:49:59 +00:00
.shippable.yml doc: recent kconfig changes break doc generation 2018-01-12 15:34:09 -05:00
CMakeLists.txt cmake: do not set CMAKE_SKIP_INSTALL_RULES to ON 2018-01-29 15:12:03 -05:00
CODEOWNERS CODEOWNERS: add @mbolivar for scripts/support/runner 2018-01-29 14:04:15 -06:00
CONTRIBUTING.rst doc: checkpatch: Fix pre-commit hook 2018-01-03 13:15:14 -05:00
Kconfig license: Replace Apache boilerplate with SPDX tag 2017-01-19 03:50:58 +00:00
Kconfig.zephyr kconfig: Prune kconfig files that don't match the ARCH or BOARD 2018-01-12 07:29:05 -05:00
LICENSE add top level Apache 2.0 license file 2016-02-05 20:24:37 -05:00
Makefile build: add top-level Makefile for docs 2017-11-08 20:00:22 -05:00
README.rst doc: update links to new zephyrproject.org site 2017-11-03 19:31:14 -04:00
VERSION release: Update PATCHLEVEL to 99 post 1.10.0 release 2017-12-08 14:31:07 -06:00
version.h.in Introduce cmake-based rewrite of KBuild 2017-11-08 20:00:22 -05:00
zephyr-env.sh env: Remove usage of -P in grep 2017-07-15 11:12:35 -07:00

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