Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
Go to file
Peter A. Bigot 889a55c86a drivers: counter: nrf: make name configuration consistent
Using `COUNTER_2_NAME` when all other properties are
`COUNTER_TIMER2_foo` is confusing.  Make the names consistent.

Signed-off-by: Peter A. Bigot <pab@pabigot.com>
2019-02-07 16:14:00 -05:00
.github/ISSUE_TEMPLATE templates: Update issue templates 2018-12-07 08:27:20 -05:00
.known-issues doc: introduce final structure 2019-02-05 07:04:40 -05:00
arch arch: arm: minor style fixes in funtion and headers' documentation 2019-02-07 11:15:52 -06:00
boards drivers: hwinfo: add driver support for NXP i.mx RT device ID 2019-02-07 15:08:18 -06:00
cmake cmake: kconfig: Expose ZEPHYR_TOOLCHAIN_VARIANT to Kconfig 2019-02-06 14:25:47 +01:00
doc doc: coccinelle: Add documentation for SPFLAGS usage 2019-02-07 08:12:20 -05:00
drivers drivers: counter: nrf: make name configuration consistent 2019-02-07 16:14:00 -05:00
dts dts: boards: Add bindings and nodes for the rocktech lcd module 2019-02-07 14:28:55 -06:00
ext drivers: counter: Counter API implementation for nRF Series (RTC). 2019-02-07 16:14:00 -05:00
include drivers: counter: rtc: Deprecating legacy counter and rtc API 2019-02-07 16:14:00 -05:00
kernel kernel: Enforce k_mem_slab block size alignment 2019-02-06 07:18:45 -05:00
lib lib: cmsis_rtos_v2: Default thread prioity 2019-02-06 10:20:17 -05:00
misc printk: move into lib/os 2019-01-22 07:45:22 -05:00
samples samples: gui: Add support for imx rt boards to lvgl sample 2019-02-07 14:28:55 -06:00
scripts scripts: bossac: Support flashing at an offset. 2019-02-07 15:13:11 -05:00
soc rtc: rename CONFIG_RTC_0_NAME to DT_RTC_0_NAME. 2019-02-07 16:14:00 -05:00
subsys bluetooth: host: Fix endianness issue for group end_handle. 2019-02-07 21:00:42 +02:00
tests drivers: counter: nrf: make name configuration consistent 2019-02-07 16:14:00 -05:00
.checkpatch.conf
.clang-format clang-format: add support for clang-format 2018-11-19 09:31:44 -05:00
.codecov.yml
.editorconfig editorconfig: basic EditorConfig configuration 2019-02-07 08:15:23 -05:00
.gitattributes
.gitignore gitignore: ignore IDE files 2018-11-21 15:05:07 +01:00
.gitlint gitlint: do not start with subsys: 2018-11-28 09:22:01 -08:00
.mailmap
.shippable.yml ci: do not send CI messages to slack 2019-02-01 19:04:55 -05:00
.uncrustify.cfg
CMakeLists.txt Build: Offsets lib as OBJECT not STATIC 2019-02-04 13:14:09 -05:00
CODEOWNERS CODEOWNERS: Add @pfalcon for POSIX-related things 2019-02-01 05:28:55 -06:00
CODE_OF_CONDUCT.md coc: move to markdown format 2019-01-24 15:37:15 -05:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr dts: stop generating CONFIG_FLASH_LOAD_{OFFSET,SIZE} 2019-02-01 10:16:06 -06:00
LICENSE
Makefile doc: add clean target to Makefile 2019-02-05 16:58:14 -05:00
README.rst doc: restructure and create index pages 2019-02-05 07:04:40 -05:00
VERSION
version.h.in
west.yml west: add west.yml 2019-01-29 10:15:01 +01:00
zephyr-env.cmd scripts: remove west from scripts/ 2019-01-29 10:15:01 +01:00
zephyr-env.sh shell: Piped output of cd to /dev/null when setting ZEPHYR_BASE. 2018-12-06 19:14:50 -05:00

README.rst

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <img src="doc/images/Zephyr-Project.png">
     </p>
   </a>

   <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

Getting Started
***************

To start developing Zephyr applications refer to the `Getting Started Guide`_
in the `Zephyr Documentation`_ pages.
A brief introduction to Zephyr can be found in the  `Zephyr Introduction`_
page.

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.

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

* **Cross-reference**: Source code cross-reference for the Zephyr
  kernel and samples code is available at
  https://elixir.bootlin.com/zephyr/latest/source.

* **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 Development mailing list`_ is perhaps the most convenient
  way to track developer discussions and to ask your own support questions to
  the Zephyr project community.  There are also specific `Zephyr mailing list
  subgroups`_ for announcements, builds, marketing, and Technical
  Steering Committee notes, for example.
  You can read through the message archives to follow
  past posts and discussions, a good thing to do to discover more about the
  Zephyr project.

* **Chatting**: You can chat online with the Zephyr project developer
  community and other users in two ways:

  * On `Slack`_: Zephyr has dedicated channels on Slack. To register, use the
    following `Slack Invite`_.

  * 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 (Note that all discussions have moved to Slack, although we still
    have many developers still available on the IRC channel).

.. _Slack Invite: https://tinyurl.com/yarkuemx
.. _Slack: https://zephyrproject.slack.com
.. _supported boards: http://docs.zephyrproject.org/latest/boards
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Zephyr Introduction: http://docs.zephyrproject.org/latest/introduction
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/getting_started
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Development mailing list: https://lists.zephyrproject.org/g/devel
.. _Zephyr mailing list subgroups: https://lists.zephyrproject.org/g/main/subgroups
.. _Sample and Demo Code Examples: http://docs.zephyrproject.org/latest/samples
.. _Security Overview: http://docs.zephyrproject.org/latest/security