Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
Go to file
Carles Cufi d0c2be7c8a doc: getting_started: Windows build doc fixes
Correct 2 items in the Windows Getting Started doc:

 * dtc-msys2 is now an upstream Chocolatey package
 * Add instructions to clone and build Ninja for MSYS2

Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-02-12 13:47:42 -05:00
.known-issues doc: add missing API content 2017-12-01 08:58:56 -05:00
arch arch: atmel_sam0: rename samd SoC series to samd21 2018-02-09 08:34:55 -06:00
boards boards: stm32f072b_disco: add supported features 2018-02-10 22:42:38 -05:00
cmake dts: mcuboot: Support for common overlays and mcuboot 2018-02-09 09:11:13 -05:00
doc doc: getting_started: Windows build doc fixes 2018-02-12 13:47:42 -05:00
drivers drivers: i2c: i2c_nios2: Fix format specifiers in log messages 2018-02-09 10:11:52 -05:00
dts dts/arm/st: fix dts inclusion for stm32f334 2018-02-12 09:17:37 -06:00
ext arch: atmel_sam0: rename samd SoC series to samd21 2018-02-09 08:34:55 -06:00
include net: buf: Make net_buf_simple_init() forward compatible 2018-02-11 10:40:57 +02:00
kernel kernel: include: rename nano_internal.h to kernel_internal.h 2018-01-31 10:07:21 -06:00
lib crc: add crc16_itu_t which is used in the MMC protocol. 2018-02-07 16:49:52 -05:00
misc dts: mcuboot: Support for common overlays and mcuboot 2018-02-09 09:11:13 -05:00
samples samples: net: sockets: Clean up/improve socket samples 2018-02-11 09:49:31 -05:00
scripts sanitycheck: Default to using Ninja 2018-02-12 08:24:23 -05:00
subsys Bluetooth: mesh: Account for scan window delaying adv events 2018-02-12 12:13:38 +02:00
tests tests: net/buf: Update to new API 2018-02-10 09:20:42 +02: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
.gitignore doc: report which warnings/errors are new 2017-11-13 17:45:42 -05:00
.gitlint gitlint: use custom rule for line length violations 2018-02-07 15:28:36 -05:00
.mailmap
.shippable.yml sanitycheck: asserts are now enabled by default 2018-02-12 08:24:23 -05:00
CMakeLists.txt cmake: ld: add application source dir to linker script cpp command 2018-02-08 15:57:32 -08:00
CODEOWNERS codeowners: Fix CODEOWNERS for $ZEPHYR_BASE/CMakeLists.txt 2018-02-09 08:54:16 -05:00
CONTRIBUTING.rst doc: update CONTRIBUTING guidelines 2018-02-09 22:48:56 -05:00
Kconfig
Kconfig.zephyr kconfig: Prune kconfig files that don't match the ARCH or BOARD 2018-01-12 07:29:05 -05:00
LICENSE
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

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