Hello! Today almost whole day frustrating trying to make work I2C on Zephyr. Tested on 2 different boards with nrf51822 and stm32f103 MCU-s and got no success. Any options for both MCU-s different tha

#i2c #stm32 #nrf51822

Hi Roman, I was taking a look at the list and I've found something that may help you. Go to the link https://lists.zephyrproject.org/g/users/message/371 and check the solution. I think that maybe you

#i2c #stm32 #nrf51822

Describe better your environment. Which board (and no MCU) are you using? Based on the http://docs.zephyrproject.org/boards/arm/nucleo_f103rb/doc/nucleof103rb.html it seems that the i2c_1 that it migh

#i2c #stm32 #nrf51822

MCU is this https://github.com/zephyrproject-rtos/zephyr/tree/d6e3f22fddccf4b542cb5ec780440cb629c12290/arch/arm/soc/st_stm32/stm32f1 Using this board https://github.com/zephyrproject-rtos/zephyr/tree/

#i2c #stm32 #nrf51822

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

Please find the logs in attachment.

#nrf52840 #i2c #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

We are trying to understand how to configure sercom3 to allow I2C support. The I2C device is the adafruit_oled_featherwing. I believe I have the I2C, SSD1306, framebuffer (cfg), and display. Below is

#i2c

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

#i2c

I am attempting to write a basic I2C program using Zephyr, but I am currently unable to sent a single byte over I2C. The program hangs after the first clock falling & rising edge. I'm using external 1

#i2c #driver #nrf5340

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

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

Hi, I am trying to connect a BME280 sensor to NXP MiMX RT1020 and run samples/sensor/bme280 application but the output is always [00:00:00.000,000] <dbg> BME280.bme280_init: initializing BME280 [00:00

#i2c #sensor

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 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

Hi Nikolaus, I assume that your MCU allows alternative SDA/SCL configurations but not simultaneous, i.e. you can decide on which SDA/SCL pair of pins you can have I2C bus, but not on all pairs at the

#driver #i2c

Hi Nikolaus I have yet to see a SOC that allows connecting one internal I2C controller to two sets of external pins at one time. Although theoretically possible it would be an unusual feature, and of

#driver #i2c

Dear Lawrence, Thank you for your reply! Indeed, after rereading the data sheet I also realised my confusion. The problem with the rerouting however persists. The chip allows to reroute the SDA and SL

#driver #i2c

I just looked at the wiring for the Thunderboard Sense 2. It is crazy…. Normally all of the I2C devices on a board are wired to a single I2C Bus. But the designers of the Thunderboard decided to conne

#driver #i2c

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