Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
Go to file
Andrew Boie 0b9f9f3023 tests: context: move idle test to the end
On some devices, when k_cpu_idle() was called we were getting
interrupts that were not the timer interrupt. On bbc_micro
a power clock control driver interrupt was happening instead
and k_cpu_idle() was returning without the system tick advancing,
failing the test.

The clock control interrupts seem to only happen early in device
boot; moving the idle test much later lets the test pass on this
board (and likely all other NRF5 based boards).

Issue: ZEP-2257
Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-06-08 15:12:03 -04:00
.known-issues doc: update known issues with blutooth APIs 2017-04-30 11:40:26 -04:00
arch stack_sentinel: hang system on failure 2017-06-08 13:49:36 -05:00
boards frdm_k64f: default to pyocd.sh for flashing/debug 2017-06-08 13:49:36 -05:00
doc doc: fix linenum references in api example 2017-06-07 22:54:29 -04:00
drivers drivers: serial: uart_fe310: fix function definiton name for UART1 IRQ 2017-06-07 12:17:15 -05:00
dts sam3x: report correct number of IRQ priority bits 2017-06-08 12:23:37 -05:00
ext drivers: clock_control: provide LL based driver to stm32f1xx series 2017-06-02 14:11:13 -04:00
include k_oops: force unlock IRQs on ARMv7M 2017-06-08 13:49:36 -05:00
kernel stack_sentinel: change cooperative check 2017-06-08 13:49:36 -05:00
lib lib: json: add helper macros for arrays of objects 2017-06-08 15:11:23 -04:00
misc kconfig: misc: Conditionally remove FLASH_LOAD options 2017-06-08 07:37:44 -05:00
samples license: add missing licenses and copyright 2017-06-08 10:41:56 -04:00
scripts toolchain.gccarmemb: Fix support for where to find newlib 2017-06-08 14:52:49 -04:00
subsys license: add missing licenses and copyright 2017-06-08 10:41:56 -04:00
tests tests: context: move idle test to the end 2017-06-08 15:12:03 -04:00
.checkpatch.conf checkpatch: update checkpatch to warn about C99 type usage 2017-04-21 17:24:04 +00:00
.gitattributes
.gitignore doc: tweak .gitignore to allow doc theme dev 2017-02-23 13:20:04 +00:00
.gitlint gitlint: Ignore signed-off-by line 2017-06-06 09:35:50 -04:00
.gitreview cc3220sf: Add support for the TI CC3220SF SoC 2017-04-28 15:06:41 -05:00
.mailmap mailmap: added axy (for Anas Nashif) 2016-12-21 13:49:59 +00:00
.shippable.yml ci: update to latest docker image 2017-05-20 07:04:46 -04:00
Kbuild build: Add separate DTS target 2017-04-20 14:36:10 +00:00
Kconfig license: Replace Apache boilerplate with SPDX tag 2017-01-19 03:50:58 +00:00
Kconfig.zephyr license: Replace Apache boilerplate with SPDX tag 2017-01-19 03:50:58 +00:00
LICENSE
MAINTAINERS doc: remove reference to legacy.h header 2017-05-08 12:53:06 -04:00
Makefile release: Update version of master to 1.8.99 2017-06-07 21:33:10 -04:00
Makefile.inc build: Add separate DTS target 2017-04-20 14:36:10 +00:00
Makefile.test tests: introduce Makefile.test 2017-01-03 17:48:44 +00:00
README.rst doc: misspelling and UTF-8 fixes 2017-05-09 20:15:49 -04:00
zephyr-env.sh build: Treat MSYS2 build as a UNIX build 2017-05-19 16:12:05 -04:00

README.rst

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

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 and RISC V, and a large number of
`supported boards`_.

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/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`_ wiki article.

* **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
  our JIRA system: https://jira.zephyrproject.org. You can browse through the
  reported issues and submit issues of your own.

* **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://github.com/zephyrproject-rtos/zephyr/wiki/Contribution-Guide
.. _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