407b49b35c
Using find_package to locate Zephyr.
Old behavior was to use $ENV{ZEPHYR_BASE} for inclusion of boiler plate
code.
Whenever an automatic run of CMake happend by the build system / IDE
then it was required that ZEPHYR_BASE was defined.
Using ZEPHYR_BASE only to locate the Zephyr package allows CMake to
cache the base variable and thus allowing subsequent invocation even
if ZEPHYR_BASE is not set in the environment.
It also removes the risk of strange build results if a user switchs
between different Zephyr based project folders and forgetting to reset
ZEPHYR_BASE before running ninja / make.
Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
|
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| prj.conf | ||
| README.rst | ||
| sample.yaml | ||
.. _fxas21002: FXAS21002 Gyroscope Sensor ########################## Overview ******** A sensor application that demonstrates how to use the fxas21002 data ready interrupt to read gyroscope data synchronously. Building and Running ******************** This project outputs sensor data to the console. It requires an fxas21002 sensor, which is present on the :ref:`hexiwear_k64` board. It does not work on QEMU. .. zephyr-app-commands:: :zephyr-app: samples/sensor/fxas21002 :board: hexiwear_k64 :goals: build :compact: Sample Output ============= .. code-block:: console X= -2.063 Y= 0.813 Z= 0.188 X= -1.750 Y= 1.063 Z= 0.063 X= -2.000 Y= 0.625 Z= 0.063 X= -2.188 Y= 0.625 Z= 0.188 X= -2.125 Y= 1.313 Z= -0.063 X= -2.188 Y= 1.188 Z= 0.313 <repeats endlessly>