<?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 Re: Kinetis K66 I2C controller hang issue in MQX Software Solutions</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/Kinetis-K66-I2C-controller-hang-issue/m-p/689197#M17450</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We captured the I2C bus using logic analyzer and observed that the SCL line is pulled&amp;nbsp;low after completion of Setup Write / Setup Read transaction. It seems like the I2C ACK interrupt is not invoked by the I2C controller even though the logic analyzer data capture shows ACK send by the slave device in the bus. As per K66 reference manual "&lt;STRONG&gt;&lt;EM&gt;SCL is held low until TXAK is written&lt;/EM&gt;&lt;/STRONG&gt;" (as per section&amp;nbsp;&lt;EM&gt;58.4.3 I2C Control Register 1)&lt;/EM&gt; and it is during ACK / NAK interrupt that the TXAK bit is written in the MQX interrupt routine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any chance for the K66 I2C controller to miss ACK / NAK interrupt. Is there any dependency on this with module clock frequency settings. We are not able to ship our product due to this issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Jul 2017 18:42:32 GMT</pubDate>
    <dc:creator>geovarghese</dc:creator>
    <dc:date>2017-07-11T18:42:32Z</dc:date>
    <item>
      <title>Kinetis K66 I2C controller hang issue</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Kinetis-K66-I2C-controller-hang-issue/m-p/689196#M17449</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there any known issue with K66 I2C controller which hangs at higher frequencies? We are observing that the K66 I2C controller hangs and the SCL line is pulled low. This happens frequently at 400KHz and rarely at 100KHz. At 40KHz the I2C bus does not hang. We are using MQX RTOS ver 4.0. We need the I2C bus to operate at 400KHz. Please help!&lt;/P&gt;&lt;P&gt;We have reset all other devices in the I2C bus when it hangs but still the SCL line is held low. So it seems like the issue is with the K66 I2C controller itself.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 08 Jul 2017 17:29:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Kinetis-K66-I2C-controller-hang-issue/m-p/689196#M17449</guid>
      <dc:creator>geovarghese</dc:creator>
      <dc:date>2017-07-08T17:29:14Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis K66 I2C controller hang issue</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Kinetis-K66-I2C-controller-hang-issue/m-p/689197#M17450</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We captured the I2C bus using logic analyzer and observed that the SCL line is pulled&amp;nbsp;low after completion of Setup Write / Setup Read transaction. It seems like the I2C ACK interrupt is not invoked by the I2C controller even though the logic analyzer data capture shows ACK send by the slave device in the bus. As per K66 reference manual "&lt;STRONG&gt;&lt;EM&gt;SCL is held low until TXAK is written&lt;/EM&gt;&lt;/STRONG&gt;" (as per section&amp;nbsp;&lt;EM&gt;58.4.3 I2C Control Register 1)&lt;/EM&gt; and it is during ACK / NAK interrupt that the TXAK bit is written in the MQX interrupt routine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any chance for the K66 I2C controller to miss ACK / NAK interrupt. Is there any dependency on this with module clock frequency settings. We are not able to ship our product due to this issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jul 2017 18:42:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Kinetis-K66-I2C-controller-hang-issue/m-p/689197#M17450</guid>
      <dc:creator>geovarghese</dc:creator>
      <dc:date>2017-07-11T18:42:32Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis K66 I2C controller hang issue</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Kinetis-K66-I2C-controller-hang-issue/m-p/689198#M17451</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;SPAN class=""&gt;&lt;A _jive_internal="true" data-content-finding="Community" data-userid="224774" data-username="geovarghese" href="https://community.nxp.com/people/geovarghese"&gt;Geo Varghese&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest you dump I2C register to get the real baud-rate when this issue happens.&lt;/P&gt;&lt;P&gt;Could you please send us your schematics and your scope shot and i2c register dump?&lt;/P&gt;&lt;P&gt;You can submit a ticket&amp;nbsp; (support requests) to us if you won't post your schematics in public.&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="http://www.nxp.com/support/support:SUPPORTHOME?tid=sbmenu" title="http://www.nxp.com/support/support:SUPPORTHOME?tid=sbmenu"&gt;Support|NXP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jul 2017 06:45:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Kinetis-K66-I2C-controller-hang-issue/m-p/689198#M17451</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2017-07-12T06:45:17Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis K66 I2C controller hang issue</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Kinetis-K66-I2C-controller-hang-issue/m-p/689199#M17452</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/danielchen@fsl"&gt;danielchen@fsl&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The I2C register dump captures using JTAG tool when the bus hangs is given below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_A1,0xC0,0x40067000&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_A2,0xC2,0x40067009&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_C1,0xF0,0x40067002&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_C2,0x00,0x40067005&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_D,0x41,0x40067004&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_F,0x1C,0x40067001&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_FLT,0x20,0x40067006&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_RA,0x00,0x40067007&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_S,0xA4,0x40067003&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_SLTH,0x00,0x4006700a&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_SLTL,0x00,0x4006700b&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Inter-Integrated Circuit (I2C1),I2C1_SMB,0x00,0x40067008&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The screenshot from the Logic analyzer is attached for the last transaction just before I2C hangs. &lt;span class="lia-inline-image-display-wrapper" image-alt="imgpsh_fullsize.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/27647i16B2B2B5085302B5/image-size/large?v=v2&amp;amp;px=999" role="button" title="imgpsh_fullsize.png" alt="imgpsh_fullsize.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Need to check if I can share the schematics privately and will confirm after that. Basically we have the K66 and the Panasonic HDMI switching chip&amp;nbsp;MN864788 on the I2C bus. All other devices are currently isolated by removing series resistors. 4.7K pullup is used for I2C SCL and SDA lines (Also tried with 1.5K pull up without any improvement).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jul 2017 11:16:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Kinetis-K66-I2C-controller-hang-issue/m-p/689199#M17452</guid>
      <dc:creator>geovarghese</dc:creator>
      <dc:date>2017-07-12T11:16:02Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis K66 I2C controller hang issue</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Kinetis-K66-I2C-controller-hang-issue/m-p/689200#M17453</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have opened new private support ticket to share the relevant details.&lt;/P&gt;&lt;P&gt;Case:00124676:Kinetis K66 I2C controller hang issue&lt;/P&gt;&lt;P&gt;Case:00124679:Attachment for Case 00124676&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jul 2017 04:32:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Kinetis-K66-I2C-controller-hang-issue/m-p/689200#M17453</guid>
      <dc:creator>geovarghese</dc:creator>
      <dc:date>2017-07-13T04:32:30Z</dc:date>
    </item>
  </channel>
</rss>

