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/sample.yaml

15 lines
345 B
YAML
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
sample:
name: ADXL372 High-g Accelerometer Sensor
tests:
samples: add test identifier Add unique identifier instead of just 'test' for samples. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-03-29 23:44:43 +08:00
sample.sensor.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
harness: sensor
tests/samples: cleanup tags Remove redundant 'sample' tag and add something that matches the functionality and features being tested, demonstrated. Avoid short abbriviations and using full names for fs. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-10-16 03:28:35 +08:00
tags: sensors
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
depends_on: spi
boards: nrf52_pca10040: Rename to nrf52dk_nrf52832 The board name for the nRF52 DK, so far known as nrf52_pca10040, is renamed to nrf52dk_nrf52832. Its documentation and all references to its name in the tree are updated accordingly. Overlay and configuration files specific to this board are also renamed, to match the new board name. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2020-04-03 00:24:56 +08:00
platform_whitelist: nrf52dk_nrf52832
samples: add test identifier Add unique identifier instead of just 'test' for samples. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-03-29 23:44:43 +08:00
sample.sensor.adxl372.i2c:
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
harness: sensor
tests/samples: cleanup tags Remove redundant 'sample' tag and add something that matches the functionality and features being tested, demonstrated. Avoid short abbriviations and using full names for fs. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-10-16 03:28:35 +08:00
tags: sensors
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
depends_on: i2c
sensor: adxl372: Convert to new DT_<COMPAT>_<INSTANCE> defines Convert adxl372 sensor driver to use new defines so we can remove the dts_fixup.h code for it. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-01-30 04:03:33 +08:00
platform_whitelist: frdm_k64f
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
extra_args: "CONF_FILE=prj_i2c.conf"