<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>**urgent** Problem with TWIM in newer Zephyr version</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/93214/urgent-problem-with-twim-in-newer-zephyr-version</link><description>Hi, 
 We just upgraded to the latest version of Zephyr, and all of our out-of-tree driver using I2C (TWIM) are now broken. 
 All the i2c_xxx function return -5 with a NACK from the slave. 
 I&amp;#39;ve checked the device tree and all the pins are correct. 
</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 26 Oct 2022 11:49:05 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/93214/urgent-problem-with-twim-in-newer-zephyr-version" /><item><title>RE: **urgent** Problem with TWIM in newer Zephyr version</title><link>https://devzone.nordicsemi.com/thread/392604?ContentTypeID=1</link><pubDate>Wed, 26 Oct 2022 11:49:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:32e033f4-e3ed-4e1a-a852-da8a76a0f591</guid><dc:creator>GiulianoFranchetto</dc:creator><description>&lt;p&gt;I&amp;#39;m going to close this ticket as it is in discussion with Zephyr teams.&lt;/p&gt;
&lt;p&gt;Long story short, when using the new &amp;quot;pin control&amp;quot; API, a default register configuration changes: the pin drive becomes S0S1 instead of S0D1.&lt;/p&gt;
&lt;p&gt;In our case, this change broke the bus.&lt;/p&gt;
&lt;p&gt;Adding &lt;em&gt;nordic,drive-mode = &amp;lt;6&amp;gt;; &lt;/em&gt;to our pinctrl dtsi fixes the issue&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>