Running the BME680 sample (zephyr/samples/sensor/bme680) on the nrf52840-dk fails and printk "Device (nil) name is". My BME680 is already packaged (DFRobot SEN0248), and provides connections only for

#i2c #nrf52840 #sensor

I've had a quick look and am confused as there is reference to a file: #include "lis2mdl_reg.h" It appears that when this driver was created they may have forgotten to include both lis2mdl_reg.c and l

#i2c #driver #lis2dw12

Yes, that is what I though, the layout of the board is a bit strange. Thank you very much for your input! The idea of having a dedicated sensor thread has also occurred to me. We are using the Thunder

#driver #i2c

Hello there, I'm trying to connect my board (nrf52dk-nrf52832) to a development kit, through I2C, which has external pull up resistors. I would like to configure the I2C port to accept the external pu

#pullup #i2c

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

#i2c #sensor

Hello guys, I would like to implement an application with NFC tag reader via NXP PN532 or other NFC controllers, which communicates with board via I2C, is there any suggestion or sample to follow how

#nxp #i2c #nvs

After further testing, I found that if I step through each instruction with the debugger the individual messages send correctly, but not if I let the program run regularly. In neither case does the i2

#i2c #driver #nrf5340

I forgot to include the overlay file…here it is.

#i2c

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 Roman, you need to update boards pinmux.c file to add the I2C pins. You could check olimexino_stm32 board's pinmux file for reference. Yannis https://github.com/zephyrproject-rtos/zephyr/tree/d6e3f

#i2c #stm32 #nrf51822