https://devzone.nordicsemi.com/f/nordic-q-a/89110/i2c-and-pinctrlWhile migrating my project to use the new pinctrl mechanism in I ran into an issue where the I2C communication on some busses was not working. Further investigation revealed that I needed to add the `nordic,drive-mode = &lt;NRF_DRIVE_S0D1&gt;;` property toen-USTelligent Community 13Fri, 01 Jul 2022 10:41:47 GMThttps://devzone.nordicsemi.com/thread/375049?ContentTypeID=1Fri, 01 Jul 2022 10:41:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:79921446-b564-4c50-b187-b4d98a8259ba&#216;ivind<p>Zephyr has a PR up for this now:</p> <p><a href="https://github.com/zephyrproject-rtos/zephyr/pull/47145">https://github.com/zephyrproject-rtos/zephyr/pull/47145</a></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/375042?ContentTypeID=1Fri, 01 Jul 2022 10:14:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:070b9b19-020a-4bea-821d-078fd908285c&#216;ivind<p>Hi,</p> <p>We are looking into this bug now. At the moment we have only seen the issue on nrf52833. Are you seeing the issue on an nrf5340 DK? If so are you building for secure or non-secure?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/373758?ContentTypeID=1Wed, 22 Jun 2022 15:33:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:848017a4-38b1-4b00-9e21-5a6ca40bf7bdJoakim Jakobsen<p>Hi!</p> <p>I agree, S0D1 has been the default and would work for most I2C configurations.</p> <p>Talked to one of my colleagues about this; And it seems that the driver sets skip_gpio_config. So it should have been done for pins configured for TWI/I2C.</p> <p>This is probably just be a bug from moving to pin control. I&#39;ll talk to our developers and get back to you.</p> <p></p> <p>Br, <br />Joakim</p><div style="clear:both;"></div>