<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>S32KのトピックRe: S32K LPI2C slave communication problem</title>
    <link>https://community.nxp.com/t5/S32K/S32K-LPI2C-slave-communication-problem/m-p/1752893#M28430</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/134727"&gt;@kawadaxi&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Can you scope the bus?&lt;/P&gt;
&lt;P&gt;Is the Slave device holding the bus low?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;</description>
    <pubDate>Mon, 06 Nov 2023 14:51:23 GMT</pubDate>
    <dc:creator>danielmartynek</dc:creator>
    <dc:date>2023-11-06T14:51:23Z</dc:date>
    <item>
      <title>S32K LPI2C slave communication problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K-LPI2C-slave-communication-problem/m-p/1752740#M28422</link>
      <description>&lt;P&gt;&amp;nbsp; &amp;nbsp; Hi, I currently have two S32K144 boards and are conducting I2C communication experiments. One is the Master and the other is the Slave.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; The Master reads data from the Slave every 50ms, one byte each time, and Slave returns incremental data from 0 to 255.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Now the problem is that after normal reading for a period of time, the communication will be abnormal. Master will always return &lt;STRONG&gt;STATUS_BUSY&lt;/STRONG&gt; after returning &lt;STRONG&gt;STATUS_TIMEOUT&lt;/STRONG&gt; once.Please help tell me what is probably causing this, my code is derived from the S32DS example.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; Thanks .&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1. The Master code&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="kawadaxi_0-1699264922742.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/248608i3958EBA7F57BA695/image-size/medium?v=v2&amp;amp;px=400" role="button" title="kawadaxi_0-1699264922742.png" alt="kawadaxi_0-1699264922742.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2.The Slave code&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="kawadaxi_1-1699265031404.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/248609iCF5DBE0C6EE207AF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="kawadaxi_1-1699265031404.png" alt="kawadaxi_1-1699265031404.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Nov 2023 10:09:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K-LPI2C-slave-communication-problem/m-p/1752740#M28422</guid>
      <dc:creator>kawadaxi</dc:creator>
      <dc:date>2023-11-06T10:09:59Z</dc:date>
    </item>
    <item>
      <title>Re: S32K LPI2C slave communication problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K-LPI2C-slave-communication-problem/m-p/1752893#M28430</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/134727"&gt;@kawadaxi&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Can you scope the bus?&lt;/P&gt;
&lt;P&gt;Is the Slave device holding the bus low?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Mon, 06 Nov 2023 14:51:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K-LPI2C-slave-communication-problem/m-p/1752893#M28430</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-11-06T14:51:23Z</dc:date>
    </item>
    <item>
      <title>Re: S32K LPI2C slave communication problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K-LPI2C-slave-communication-problem/m-p/1753117#M28439</link>
      <description>&lt;P&gt;Hi, thank you for your reply.&lt;/P&gt;&lt;P&gt;Yes, I observed that Slave pulls SDA down. And this problem seems to be irregular. Sometimes it appears easily, and sometimes it takes a long time to reappear.&lt;BR /&gt;Is this problem possibly related to interrupt priority? I now use SysTick, LpTMR, CAN, and ADC interrupts at the same time. In addition, may it be related to my jumper wire, because I used two wires to connect the I2C of the two boards,i&amp;nbsp;am not sure whether this will cause unstable communication.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 02:02:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K-LPI2C-slave-communication-problem/m-p/1753117#M28439</guid>
      <dc:creator>kawadaxi</dc:creator>
      <dc:date>2023-11-07T02:02:37Z</dc:date>
    </item>
    <item>
      <title>Re: S32K LPI2C slave communication problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K-LPI2C-slave-communication-problem/m-p/1753348#M28450</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;This problem does seem to be related to jumper wires. After I changed to a new twisted pair wire, the situation became stable. Of course, further observation may be required.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 07:57:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K-LPI2C-slave-communication-problem/m-p/1753348#M28450</guid>
      <dc:creator>kawadaxi</dc:creator>
      <dc:date>2023-11-07T07:57:11Z</dc:date>
    </item>
  </channel>
</rss>

