Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
Go to file
Kumar Gala 924e8aad12 tests: arm_runtime_nmi: Make test build on v8m
The ICSR[NMIPENDSET] bit got renamed to ICSR[PENDNMISET] in the v8m
architecture.  So we map SCB_ICSR_PENDNMISET_Msk to
SCB_ICSR_NMIPENDSET_Msk to the tests builds and functions.

Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-03-13 10:02:59 -05:00
.known-issues doc: add missing API content 2017-12-01 08:58:56 -05:00
arch soc: nrf5: Use i2c configure options generated from dts 2018-03-13 14:14:13 +01:00
boards soc: nrf5: Use i2c configure options generated from dts 2018-03-13 14:14:13 +01:00
cmake cmake: Find out earlier whether ccache is to be used or not 2018-03-02 07:13:21 +01:00
doc doc: fix doxy syntax for hiding internal symbols 2018-03-13 06:33:38 -07:00
drivers soc: nrf5: Use i2c configure options generated from dts 2018-03-13 14:14:13 +01:00
dts dts: arm: nrf5: Add i2c nodes 2018-03-13 14:14:13 +01:00
ext subsys: fs: Fix fs_file_t and fs_dir_t usage 2018-03-13 09:47:58 -05:00
include crc: make crc8_ccitt() match the other CRC functions. 2018-03-10 21:49:07 -05:00
kernel kernel: Name of static functions should not begin with an underscore 2018-03-10 08:39:10 -05:00
lib crc: make crc8_ccitt() match the other CRC functions. 2018-03-10 21:49:07 -05:00
misc subsys: stats - Statistics support 2018-02-20 22:07:52 +01:00
samples Bluetooth: hci_usb: Read the whole USB EPOUT buffer at once 2018-03-09 21:46:59 -05:00
scripts scripts: extract_dts_includes: Fix path handling in Windows 2018-03-12 09:44:36 -05:00
subsys subsys: fs: Fix fs_file_t and fs_dir_t usage 2018-03-13 09:47:58 -05:00
tests tests: arm_runtime_nmi: Make test build on v8m 2018-03-13 10:02:59 -05:00
.checkpatch.conf
.codecov.yml ci: add .codecov.yml for codecov.io configuration 2018-01-03 13:12:03 -05:00
.gitattributes
.gitignore sample: net: RPL mesh sample over QEMU 2018-02-20 14:47:14 +02:00
.gitlint gitlint: use custom rule for line length violations 2018-02-07 15:28:36 -05:00
.mailmap
.shippable.yml build: deprecate ZEPHYR_GCC_VARIANT 2018-02-13 07:44:45 -08:00
CMakeLists.txt cmake: Find out earlier whether ccache is to be used or not 2018-03-02 07:13:21 +01:00
CODEOWNERS CODEOWNERS: Update entries for nxp soc families, boards, and drivers 2018-03-06 10:52:29 -05:00
CONTRIBUTING.rst doc: add test coverage and proposal policy 2018-03-11 05:11:58 -04:00
Kconfig
Kconfig.zephyr kconfig: Don't source the non-existing zephyr/net/Kconfig 2018-03-13 06:27:07 -07:00
LICENSE
Makefile build: add top-level Makefile for docs 2017-11-08 20:00:22 -05:00
README.rst
VERSION release: Post-release patch level update 2018-03-09 20:18:38 -05:00
version.h.in
zephyr-env.cmd build: win: Add a new zephyr-env.cmd file 2018-02-12 19:22:22 -05:00
zephyr-env.sh

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