zephyr

History

Gerard Marull-Paretas 79e6b0e0f6 includes: prefer <zephyr/kernel.h> over <zephyr/zephyr.h> As of today <zephyr/zephyr.h> is 100% equivalent to <zephyr/kernel.h>. This patch proposes to then include <zephyr/kernel.h> instead of <zephyr/zephyr.h> since it is more clear that you are including the Kernel APIs and (probably) nothing else. <zephyr/zephyr.h> sounds like a catch-all header that may be confusing. Most applications need to include a bunch of other things to compile, e.g. driver headers or subsystem headers like BT, logging, etc. The idea of a catch-all header in Zephyr is probably not feasible anyway. Reason is that Zephyr is not a library, like it could be for example `libpython`. Zephyr provides many utilities nowadays: a kernel, drivers, subsystems, etc and things will likely grow. A catch-all header would be massive, difficult to keep up-to-date. It is also likely that an application will only build a small subset. Note that subsystem-level headers may use a catch-all approach to make things easier, though. NOTE: This patch is NOT removing the header, just removing its usage in-tree. I'd advocate for its deprecation (add a #warning on it), but I understand many people will have concerns. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>		2022-09-05 16:31:47 +02:00
..
src	includes: prefer <zephyr/kernel.h> over <zephyr/zephyr.h>	2022-09-05 16:31:47 +02:00
CMakeLists.txt	…
README.rst	…
prj.conf	sensors: Remove unnecessary Kconfig setting of sensors	2022-07-25 15:18:56 +02:00
sample.yaml	…

README.rst

.. _i3g4250d:

I3G4250D: 3-axis digital output gyroscope
#########################################

Description
***********

This sample application configures the gyroscope with a fixed
sampling rate and polls the measurements with the same rate and
displays the measurements along with a timestamp since startup.

Requirements
************

This sample application uses the I3G4250D sensor connected via
SPI interface. This is the case for example for stm32f3_disco@E
board devicetree.

Building and Running
********************

To build the application a board with I3G4250D on SPI interface
has to be chosen, or a custom devicetree overlay has to be provided.
Here STM32F3 discovery board is used.

.. zephyr-app-commands::
   :zephyr-app: samples/sensor/i3g4250d
   :board: stm32f3_disco@E
   :goals: build flash

Sample Output
*************

.. code-block:: console

   *** Booting Zephyr OS build zephyr-v2.6.0-1897-ga09838064f26  ***
   Set sensor sampling frequency to 200.000000 Hz.
   Polling at 200.000000 Hz
   12 ms: x 2454.031430 , y 2336.015410 , z -1800.030108
   22 ms: x -248.003106 , y -268.979704 , z 6.018390
   32 ms: x -214.989906 , y -237.023468 , z 6.013926
   41 ms: x -193.978308 , y -205.032232 , z 2.000356
   51 ms: x -158.986716 , y -171.014568 , z 3.969998
   60 ms: x -138.979582 , y -153.003326 , z 3.978748
   70 ms: x -120.981554 , y -129.982800 , z -13.971422
   80 ms: x -106.984060 , y -112.967272 , z -80.006572