At a high level, between the sensor driver you found in drivers/sensor/lsm6dsl and your program, Zephyr provides an interface layer that makes the calls to sensor_attr_set() reasonably independent of

#sensor #sst26

Using: Windows 10, nRF Connect v3.5.0, SES v4.52, ncs v1.3.0, zephyr v2.3.0 I have a custom board based on the Nordic Thingy91 and the Asset Tracker application. There is also an LIS2DW12 present on S

#driver #sensor #spi #lis2dw12 #nrf9160

Have you tried to connect a logic analyser to your I2C pins to see if there are any transactions occurring? Thanks, Jeremy

#i2c #sensor

Hi im a beginner trying to work with the bbc microbits for my engineering project, my task involves using mesh networking on the bbc microbits to send a message to the user's computer stating motion i

#bluetooth #nrf51822 #zephyrbluetoothmesh #sensor #ble

My environment : Debian 10 zephyr SDK 0.10.3 zephyr 2.1.0-rc2 I'm Interfacing Max44009 with nrf52840 on a custom make board in zephyr. I'm using the sample sensor program for MAX44009. Configured with

#nrf52480 #sensor

Hi, You may want to look at a couple of things to help you answer your own question: In the zephyr folders; It has the list of defines and corresponding pins The other useful information would be a cl

#zephyrbluetoothmesh #sensor #ble #bluetoothmesh #gpio

Hi Yorick, This TEMP sensor are defined within zephyr sensors pattern. You should use it by binding the device to a struct and using the default functions from sensor.h You should use this to bind: st

#nrf52840 #sensor

Hi there, I suspect that sample requires a specific .conf file for nRF52840, since it fails on an invalid GPIO Kconfig symbol. Adding Mieszko and and Andrzej from Nordic. Carles

#nrf52840 #i2c #sensor

Hi Stefan, If your board selects HAS_DTS_I2C_DEVICE, then you should define CONFIG_LSM6DS0_I2C_MASTER_DEV_NAME and CONFIG_LSM6DS0_I2C_ADDR in your board dts.fixup file rather than myboard_defconfig. S

#sensor #dts #defconfig