<?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>topic S32K312EVB-Q172 I2C timeout error in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K312EVB-Q172-I2C-timeout-error/m-p/2065815#M47031</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have a problem with the I2C AUTOSAR driver for S32K312. I have the code working and I am able to communicate with the device.&lt;/P&gt;
&lt;P&gt;However, once a timeout error occurs on the bus for any reason, the MCU somehow gets stuck and everytime there is a attempt to send more data over I2C, nothing gets transmitted on the I2C lines, the SCL line remains high while the SDA line remains low. Is there any way to fix this?&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2025-03-20 203025.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/329142iEF5267AFD4D65F36/image-size/large?v=v2&amp;amp;px=999" alt="Screenshot 2025-03-20 203025.png" title="Screenshot 2025-03-20 203025.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Here is a screenshot of a line of code executing a I2C_SynchTransmit - the capture is not triggered because nothing gets transmitted on the lines and it results in a timeout again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am using S32DS 3.5 with RTD 3.0.0&lt;/P&gt;</description>
    <pubDate>Thu, 20 Mar 2025 19:54:22 GMT</pubDate>
    <dc:creator>tkubincova</dc:creator>
    <dc:date>2025-03-20T19:54:22Z</dc:date>
    <item>
      <title>S32K312EVB-Q172 I2C timeout error</title>
      <link>https://community.nxp.com/t5/S32K/S32K312EVB-Q172-I2C-timeout-error/m-p/2065815#M47031</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have a problem with the I2C AUTOSAR driver for S32K312. I have the code working and I am able to communicate with the device.&lt;/P&gt;
&lt;P&gt;However, once a timeout error occurs on the bus for any reason, the MCU somehow gets stuck and everytime there is a attempt to send more data over I2C, nothing gets transmitted on the I2C lines, the SCL line remains high while the SDA line remains low. Is there any way to fix this?&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2025-03-20 203025.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/329142iEF5267AFD4D65F36/image-size/large?v=v2&amp;amp;px=999" alt="Screenshot 2025-03-20 203025.png" title="Screenshot 2025-03-20 203025.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Here is a screenshot of a line of code executing a I2C_SynchTransmit - the capture is not triggered because nothing gets transmitted on the lines and it results in a timeout again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am using S32DS 3.5 with RTD 3.0.0&lt;/P&gt;</description>
      <pubDate>Thu, 20 Mar 2025 19:54:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K312EVB-Q172-I2C-timeout-error/m-p/2065815#M47031</guid>
      <dc:creator>tkubincova</dc:creator>
      <dc:date>2025-03-20T19:54:22Z</dc:date>
    </item>
    <item>
      <title>Re: S32K312EVB-Q172 I2C timeout error</title>
      <link>https://community.nxp.com/t5/S32K/S32K312EVB-Q172-I2C-timeout-error/m-p/2066168#M47061</link>
      <description>&lt;P&gt;Hi&amp;nbsp;Tereza,&lt;/P&gt;
&lt;P&gt;This is the slave device that holds the SDA line low.&lt;/P&gt;
&lt;P&gt;Refer to UM10204 I2C-bus specification and user manual&lt;/P&gt;
&lt;P&gt;&lt;A href="https://assets.nexperia.com/documents/user-manual/UM10204.pdf" target="_blank"&gt;https://assets.nexperia.com/documents/user-manual/UM10204.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="danielmartynek_0-1742544510691.png" style="width: 582px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/329231iB813C0D33A331754/image-dimensions/582x163?v=v2" width="582" height="163" role="button" title="danielmartynek_0-1742544510691.png" alt="danielmartynek_0-1742544510691.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;danielmartynek_0-1742544510691.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The RTD I2C driver cannot have such a feature though. This would require the PORT/DIO driver.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;An example is in&amp;nbsp;AN4803 I2C Non-Blocking Communication&lt;/P&gt;
&lt;P&gt;tI2C_fault I2C_Restore(void)&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/docs/en/application-note/AN4803.pdf" target="_blank"&gt;https://www.nxp.com/docs/en/application-note/AN4803.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2025 08:38:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K312EVB-Q172-I2C-timeout-error/m-p/2066168#M47061</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2025-03-21T08:38:40Z</dc:date>
    </item>
  </channel>
</rss>

