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/bme280/Kconfig

23 lines
396 B
Plaintext
Raw Normal View History

samples: bme280: enable sensor logging This helps debug issues with the device. Samples should try to be helpful to first-time users. Send printk() to logging so it doesn't fight over the UART. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 03:04:35 +08:00
# Copyright (c) 2020, Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0
config LOG
default y
config LOG_PRINTK
default y
config SENSOR_LOG_LEVEL
default 4
samples: bme280: provide generic arduino I2C and SPI support Adjust the documentation and devicetree overlays so the sample can be built for any board with an Arduino I2C and SPI pinout, defaulting I2C and SPI to y to make it easier to switch between the two without requiring a pristine build. The user has to choose an appropriate overlay or have a sensor built in to the board. Use the newly introduced DEVICE_DT_GET_ANY() in main.c to ask for a bosch,bme280 without worrying over the details or exposing DT_DRV_COMPAT-based functionality that is really meant for drivers. Remove the no-longer-needed board specific overlay for nRF52840 DK; this is covered by the generic Arduino overlays now. Fix the datasheet link while we're here. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-11-06 02:29:59 +08:00
# Enable SPI and I2C support by default so that the sample works with
# the device connected either way. These defaults can be overridden if
# needed.
samples: bme280: enable the appropriate bus by default I personally don't find it very useful to have to maintain prj.conf and prj_spi.conf for this sample. The information we need to make this application "just work" with regards to the bus is available in the devicetree, and Kconfig can now access it using dt_compat_on_bus(). Do so, enabling I2C and SPI appropriately when a sensor of the right type is on either of those buses. If no sensors are enabled, the user gets the build-time error message in main.c about no devices being found. This approach is prone to the "stuck symbol" Kconfig problem covered in our documentation, so a pristine build is necessary to change the default settings from a previous build. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-04-11 06:40:01 +08:00
config SPI
samples: bme280: provide generic arduino I2C and SPI support Adjust the documentation and devicetree overlays so the sample can be built for any board with an Arduino I2C and SPI pinout, defaulting I2C and SPI to y to make it easier to switch between the two without requiring a pristine build. The user has to choose an appropriate overlay or have a sensor built in to the board. Use the newly introduced DEVICE_DT_GET_ANY() in main.c to ask for a bosch,bme280 without worrying over the details or exposing DT_DRV_COMPAT-based functionality that is really meant for drivers. Remove the no-longer-needed board specific overlay for nRF52840 DK; this is covered by the generic Arduino overlays now. Fix the datasheet link while we're here. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-11-06 02:29:59 +08:00
default y
samples: bme280: enable the appropriate bus by default I personally don't find it very useful to have to maintain prj.conf and prj_spi.conf for this sample. The information we need to make this application "just work" with regards to the bus is available in the devicetree, and Kconfig can now access it using dt_compat_on_bus(). Do so, enabling I2C and SPI appropriately when a sensor of the right type is on either of those buses. If no sensors are enabled, the user gets the build-time error message in main.c about no devices being found. This approach is prone to the "stuck symbol" Kconfig problem covered in our documentation, so a pristine build is necessary to change the default settings from a previous build. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-04-11 06:40:01 +08:00
config I2C
samples: bme280: provide generic arduino I2C and SPI support Adjust the documentation and devicetree overlays so the sample can be built for any board with an Arduino I2C and SPI pinout, defaulting I2C and SPI to y to make it easier to switch between the two without requiring a pristine build. The user has to choose an appropriate overlay or have a sensor built in to the board. Use the newly introduced DEVICE_DT_GET_ANY() in main.c to ask for a bosch,bme280 without worrying over the details or exposing DT_DRV_COMPAT-based functionality that is really meant for drivers. Remove the no-longer-needed board specific overlay for nRF52840 DK; this is covered by the generic Arduino overlays now. Fix the datasheet link while we're here. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-11-06 02:29:59 +08:00
default y
samples: bme280: enable the appropriate bus by default I personally don't find it very useful to have to maintain prj.conf and prj_spi.conf for this sample. The information we need to make this application "just work" with regards to the bus is available in the devicetree, and Kconfig can now access it using dt_compat_on_bus(). Do so, enabling I2C and SPI appropriately when a sensor of the right type is on either of those buses. If no sensors are enabled, the user gets the build-time error message in main.c about no devices being found. This approach is prone to the "stuck symbol" Kconfig problem covered in our documentation, so a pristine build is necessary to change the default settings from a previous build. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-04-11 06:40:01 +08:00
samples: bme280: enable sensor logging This helps debug issues with the device. Samples should try to be helpful to first-time users. Send printk() to logging so it doesn't fight over the UART. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
2020-03-25 03:04:35 +08:00
source "Kconfig.zephyr"