<?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>I2C master driver problems using Zephy Devicetree method.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/101371/i2c-master-driver-problems-using-zephy-devicetree-method</link><description>Dear sir: 
 We use the VS code IDE with NRF connect SDK 2.4.0 for matter door lock application. 
 We have the problems with the I2C master driver to the motor device. 
 The DT overlay file is defined as follow: 
 
 &amp;amp; i2c0 { 
 compatible = &amp;quot;nordic,nrf</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 30 Jun 2023 07:17:46 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/101371/i2c-master-driver-problems-using-zephy-devicetree-method" /><item><title>RE: I2C master driver problems using Zephy Devicetree method.</title><link>https://devzone.nordicsemi.com/thread/433843?ContentTypeID=1</link><pubDate>Fri, 30 Jun 2023 07:17:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c55ff1a-289c-4035-ae2a-7bb2776c3b2b</guid><dc:creator>Henry_Chou</dc:creator><description>&lt;p&gt;Finally,.....We fix the issue.&lt;/p&gt;
&lt;p&gt;Because the slave address in overlay file should be divided by 2,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The exactly address should be 0x30. Isuue is soloved.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: I2C master driver problems using Zephy Devicetree method.</title><link>https://devzone.nordicsemi.com/thread/433838?ContentTypeID=1</link><pubDate>Fri, 30 Jun 2023 06:51:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7cbffe4c-196d-47fb-b74a-e337bc695a0c</guid><dc:creator>Henry_Chou</dc:creator><description>&lt;p&gt;Fix the bug......&lt;/p&gt;
&lt;div&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; // GPIO_write(CONFIG_GPIO_MTRINT, 0); // wakeup MCU&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span&gt;LOG_INF&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&amp;quot;Enter writeTiny&amp;quot;&lt;/span&gt;&lt;span&gt;);&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; gpio_pin_set_dt(&amp;amp;mtrint, 0);&amp;nbsp;&amp;nbsp;&amp;nbsp;//&lt;/span&gt;&lt;span&gt;gpio_pin_set_dt&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&amp;amp;&lt;/span&gt;&lt;span&gt;mtrint&lt;/span&gt;&lt;span&gt;,&amp;nbsp;&lt;/span&gt;&lt;span&gt;1&lt;/span&gt;&lt;span&gt;);&amp;nbsp; Wake up level should be low,The other should be high.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;But the I2C SDA still is NACK.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: I2C master driver problems using Zephy Devicetree method.</title><link>https://devzone.nordicsemi.com/thread/433832?ContentTypeID=1</link><pubDate>Fri, 30 Jun 2023 06:05:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:afb480dd-a17c-4e2f-915c-3954b98f9e70</guid><dc:creator>Henry_Chou</dc:creator><description>&lt;p&gt;Update the status.....&lt;/p&gt;
&lt;p&gt;Signal from I2C bus is NACK.......&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/_A287555EF764D6536B756297_-2023_2D00_06_2D00_30-134259.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;But the motor driver device which is used working as the other MCU.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>