Go to file
Maureen Helm 7ae7577145 boards: shields: Append accel/magn sensor nodelabels with bus address
Devicetree aliases, accel0 and magn0, were recently introduced to enable
sensor sample applications to support multiple sensor drivers of the
same type and thereby reduce the number of driver-specific sensor sample
applications.

This was implemented by adding devicetree nodelabels to accelerometer
and magnetometer sensor nodes, which unfortunately can suffer from
naming conflicts when using shield boards. Fix the problem by appending
the I2C bus address or SPI chip select to the devicetree nodelabel for
sensor nodes on shield boards only. Base boards are left alone to keep
their nodelabels as short as possible.

Signed-off-by: Maureen Helm <maureen.helm@intel.com>
2022-08-10 12:00:24 +02:00
.github ci: run bug snapshot daily 2022-08-10 11:59:55 +02:00
arch arch: arm: aarch32: cortex_m: fault: Prevent BusFault from HardFault 2022-08-10 11:59:38 +02:00
boards boards: shields: Append accel/magn sensor nodelabels with bus address 2022-08-10 12:00:24 +02:00
cmake ztest: allow asserts anywhere 2022-08-09 13:30:15 -04:00
doc doc: lwm2m: Announces support for v.1.1 2022-08-10 11:59:48 +02:00
drivers drivers: dai: Enable Zephyr runtime power mgmt in Intel SSP driver 2022-08-10 11:58:45 +02:00
dts drivers: dai: Enable Zephyr runtime power mgmt in Intel SSP driver 2022-08-10 11:58:45 +02:00
include/zephyr ztest: allow asserts anywhere 2022-08-09 13:30:15 -04:00
kernel kernel: Init the base.slice_ticks for dummy_thread 2022-08-04 19:44:24 -04:00
lib lib: os: spsc_pbuf: Fix free space calculation 2022-08-02 08:13:31 -04:00
misc misc: generated: update configs.c template with <zephyr/...> prefix 2022-05-09 12:45:29 -04:00
modules modules: openthread: use zephyr,ieee802154 choice 2022-08-10 11:57:34 +02:00
samples drivers: dai: Enable Zephyr runtime power mgmt in Intel SSP driver 2022-08-10 11:58:45 +02:00
scripts west: Fix handling of modules in the boards command 2022-08-09 16:07:51 +02:00
share cmake: sysbuild: signing support 2022-08-03 16:05:07 +02:00
soc soc: atmel_sam0: fix include path for SAMR35 2022-08-10 12:00:11 +02:00
submanifests
subsys net: lib: config: remove NET_CONFIG_IEEE802154_DEV_NAME 2022-08-10 11:57:34 +02:00
tests tests: lib: cmsis_nn: Initialise bias dimensions for depthwise convolve 2022-08-10 12:00:18 +02:00
.checkpatch.conf
.clang-format clang-format: do not merge blocks/functions into single line 2022-07-15 19:18:28 -04:00
.codecov.yml
.editorconfig editorconfig: Improve verbosity 2022-04-28 08:55:39 -04:00
.gitattributes
.gitignore .gitignore: exempt scripts/build from ignore 2022-07-30 08:29:29 -05:00
.gitlint
.mailmap
CMakeLists.txt scripts: gen_handles: output dependency graph 2022-07-30 08:29:29 -05:00
CODE_OF_CONDUCT.md
CODEOWNERS cmake: initial sysbuild / multi image support 2022-08-03 16:05:07 +02:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr Kconfig: flag LEGACY_INCLUDE_PATH as deprecated 2022-08-05 13:03:54 +02:00
LICENSE
MAINTAINERS.yml maintainers: mcumgr: Add myself as collaborator 2022-08-10 12:00:03 +02:00
README.rst readme: Update stale documentation links 2022-06-06 12:07:12 +02:00
VERSION version: Fix the EXTRAVERSION field 2022-06-05 20:11:17 +02:00
version.h.in
west.yml west.yml: Update NXP HAL to get the latest SDK 2022-08-09 15:52:05 -05:00
zephyr-env.cmd
zephyr-env.sh everywhere: fix typos 2022-03-18 13:24:08 -04:00

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <img src="doc/_static/images/logo-readme.svg">
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <a
   href="https://github.com/zephyrproject-rtos/zephyr/actions/workflows/twister.yaml?query=branch%3Amain">
   <img
   src="https://github.com/zephyrproject-rtos/zephyr/actions/workflows/twister.yaml/badge.svg?event=push"></a>


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-A,
Cortex-R, Cortex-M), Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V,
SPARC, MIPS, and a large number of `supported boards`_.

.. below included in doc/introduction/introduction.rst


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

Welcome to Zephyr! See the `Introduction to Zephyr`_ for a high-level overview,
and the documentation's `Getting Started Guide`_ to start developing.

.. start_include_here

Community Support
*****************

Community support is provided via mailing lists and Discord; see the Resources
below for details.

.. _project-resources:

Resources
*********

Here's a quick summary of resources to help you find your way around:

* **Help**: `Asking for Help Tips`_
* **Documentation**: http://docs.zephyrproject.org (`Getting Started Guide`_)
* **Source Code**: https://github.com/zephyrproject-rtos/zephyr is the main
  repository; https://elixir.bootlin.com/zephyr/latest/source contains a
  searchable index
* **Releases**: https://github.com/zephyrproject-rtos/zephyr/releases
* **Samples and example code**: see `Sample and Demo Code Examples`_
* **Mailing Lists**: users@lists.zephyrproject.org and
  devel@lists.zephyrproject.org are the main user and developer mailing lists,
  respectively. You can join the developer's list and search its archives at
  `Zephyr Development mailing list`_. The other `Zephyr mailing list
  subgroups`_ have their own archives and sign-up pages.
* **Nightly CI Build Status**: https://lists.zephyrproject.org/g/builds
  The builds@lists.zephyrproject.org mailing list archives the CI nightly build results.
* **Chat**: Real-time chat happens in Zephyr's Discord Server. Use
  this `Discord Invite`_ to register.
* **Contributing**: see the `Contribution Guide`_
* **Wiki**: `Zephyr GitHub wiki`_
* **Issues**: https://github.com/zephyrproject-rtos/zephyr/issues
* **Security Issues**: Email vulnerabilities@zephyrproject.org to report
  security issues; also see our `Security`_ documentation. Security issues are
  tracked separately at https://zephyrprojectsec.atlassian.net.
* **Zephyr Project Website**: https://zephyrproject.org

.. _Discord Invite: https://chat.zephyrproject.org
.. _supported boards: http://docs.zephyrproject.org/latest/boards/index.html
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Introduction to Zephyr: http://docs.zephyrproject.org/latest/introduction/index.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/develop/getting_started/index.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/index.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/index.html
.. _Security: http://docs.zephyrproject.org/latest/security/index.html
.. _Asking for Help Tips: https://docs.zephyrproject.org/latest/develop/getting_started/index.html#asking-for-help