OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/samples/sensor/adxl372/CMakeLists.txt

12 lines
288 B
CMake
Raw Normal View History

samples: sensor: adxl372: Add ADXL372 sample application This sample application produces slightly different outputs based on the chosen driver configuration mode. In Measuring Mode with trigger support, the acceleration on all three axis is printed in m/s^2 at the sampling rate (ODR). In polled Measuring Mode the instantaneous acceleration is polled every 2 seconds. In most high-g applications, a single (3-axis) acceleration sample at the peak of an impact event contains sufficient information about the event, and the full acceleration history is not required. In this Max Peak Detect Mode the device returns only the over threshold peak acceleration between two consecutive sample fetches or trigger events. Instead of printing the acceleration on all three axis, the sample application calculates the vector magnitude (root sum squared) and displays the result in g rather than in m/s^2, together with an bar graph. Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
2018-08-17 15:31:42 +08:00
#
# Copyright (c) 2018 Analog Devices Inc.
#
# SPDX-License-Identifier: Apache-2.0
#
cmake_minimum_required(VERSION 3.8.2)
include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
samples, tests: Use semi-accurate project names When using an IDE (e.g. Eclipse, Qt Creator), the project name gets displayed. This greatly simplifies the navigation between projects when having many of them open at the same time. Naming every project "NONE" defeats this functionality. This patch tries to use sensible project names while not duplicating too much of what is already represented in the path. This is done by using the name of the directory the relevant CMakeLists.txt file is stored in. To ensure unique project names in the samples (and again, in the tests folder) folder, small manual adjustments have been done. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
2018-10-25 22:54:09 +08:00
project(adxl372)
samples: sensor: adxl372: Add ADXL372 sample application This sample application produces slightly different outputs based on the chosen driver configuration mode. In Measuring Mode with trigger support, the acceleration on all three axis is printed in m/s^2 at the sampling rate (ODR). In polled Measuring Mode the instantaneous acceleration is polled every 2 seconds. In most high-g applications, a single (3-axis) acceleration sample at the peak of an impact event contains sufficient information about the event, and the full acceleration history is not required. In this Max Peak Detect Mode the device returns only the over threshold peak acceleration between two consecutive sample fetches or trigger events. Instead of printing the acceleration on all three axis, the sample application calculates the vector magnitude (root sum squared) and displays the result in g rather than in m/s^2, together with an bar graph. Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
2018-08-17 15:31:42 +08:00
FILE(GLOB app_sources src/*.c)
target_sources(app PRIVATE ${app_sources})