Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
Go to file
Andrzej Głąbek a7c430f36f scripts: dts: Use DT_ prefix in generated labels
Almost all labels generated by the extracting script are now prefixed
with DT_. The only exceptions are:
- stuff with 'base_label' specified in yaml bindings
- items specified by 'regs_config' and 'name_config' dictionaries
  in globals.py module
- FLASH related labels generated by flash.extract() called separately
  from generate_node_definitions(), e.g. FLASH_WRITE_BLOCK_SIZE -
  these are used directly, not through fixups, from existing code
  so I didn't want to touch them now

Labels generated for aliases are additionally prefixed with information
from the 'compatible' property, e.g. DT_GPIO_LEDS_LED0_* is generated
instead of LED0_*. To provide backward compatibility for code that uses
LEDx_* and SWx_* labels in their previous forms, a command line option
named 'old-alias-names' is added to the extraction script. This option
causes that the labels for aliases are generated in both old and new
forms. Currently this option is always enabled in dts.cmake.

Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2018-11-13 10:44:42 -06:00
.github/ISSUE_TEMPLATE doc: Add issue templates 2018-11-10 15:06:04 -05:00
.known-issues doc: filter expected dup decl warnings 2018-11-05 23:40:26 -05:00
arch xtensa: Disable interrupts on entry to _Cstart 2018-11-12 13:51:20 -05:00
boards usb: Make USB_VBUS_GPIO a Kconfig option 2018-11-13 07:10:04 -06:00
cmake scripts: dts: Use DT_ prefix in generated labels 2018-11-13 10:44:42 -06:00
doc doc: fix the example code typo 2018-11-13 08:09:53 -05:00
drivers pinmux: stm32f4: add MCO pin multiplexing helper 2018-11-13 07:11:15 -06:00
dts sensors: bmi160: Add DTS support 2018-11-13 10:23:22 +01:00
ext ext: qmsi: Remove dead code related to undefined Kconfig symbols 2018-11-10 15:18:24 -05:00
include usb: hid: Define helper definitions and cleanup code 2018-11-13 12:41:39 +01:00
kernel kernel: Make tag identifiers unique 2018-11-06 16:20:15 -05:00
lib lib: fdtable: File descriptor table should reside in kernel memory 2018-11-08 09:47:46 -08:00
misc kconfig: distribute misc/Kconfig option where they belong 2018-11-12 08:01:15 -05:00
samples logging: Add uart backend dependency to shell uart backend 2018-11-13 09:17:05 -05:00
scripts scripts: dts: Use DT_ prefix in generated labels 2018-11-13 10:44:42 -06:00
soc arch: arm: stm32f7: Kconfig: select CPU_HAS_ARM_MPU 2018-11-13 08:58:29 -05:00
subsys Bluetooth: settings: store CCC on write 2018-11-13 16:36:49 +02:00
tests tests: Add new bsim based encrypted BLE link test 2018-11-13 11:14:19 -05:00
.checkpatch.conf
.codecov.yml
.gitattributes
.gitignore gitignore: Ignore default bsimt_bt test output folder 2018-11-13 11:14:19 -05:00
.gitlint
.mailmap
.shippable.yml ci: Run bsim_bt tests and collect coverage results 2018-11-13 11:14:19 -05:00
.uncrustify.cfg uncrustify: Add a rule to remove space inside function argument 2018-10-16 09:50:03 -04:00
CMakeLists.txt cmake: parameterized flags to not include standard defines/files 2018-11-01 16:30:02 -04:00
CODEOWNERS CODEOWNERS: Update list to add `scripts/coccinelle/` directory 2018-11-07 08:19:14 -05:00
CONTRIBUTING.rst doc: Fix a typo 2018-10-25 09:10:44 +01:00
Kconfig
Kconfig.zephyr kconfig: distribute misc/Kconfig option where they belong 2018-11-12 08:01:15 -05:00
LICENSE
Makefile doc: document build target for PDF 2018-09-11 14:55:43 -04:00
README.rst docs: fixed documenation pointers 2018-09-12 12:03:18 -04:00
VERSION release: Post-release patch level update 2018-09-10 22:42:12 -04:00
version.h.in
zephyr-env.cmd scripts: fix west launcher for macOS 2018-09-26 00:33:45 +02:00
zephyr-env.sh

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.

* **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: http://docs.zephyrproject.org/latest/boards/boards.html
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Zephyr Introduction: http://docs.zephyrproject.org/latest/introduction/introducing_zephyr.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/getting_started/getting_started.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/contribute_guidelines.html
.. _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/samples.html
.. _Security Overview: http://docs.zephyrproject.org/latest/security/security-overview.html