<?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: Inconsistency in I2C Interface in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Inconsistency-in-I2C-Interface/m-p/750934#M116868</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;SPAN style="font-size: 12.0pt;"&gt;Sachin&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;issue may be caused by signals noise or operating systems delays, so one can try to&lt;/P&gt;&lt;P&gt;decrease operating i2c frequency, add delays and descrease pull resistors values.&lt;/P&gt;&lt;P&gt;May be recommended to try with baremetal sdk (or freertos)&lt;/P&gt;&lt;P&gt;Github SDK&lt;BR /&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fgithub.com%2Fbackenklee%2Fswp-report%2Ftree%2Fmaster%2FiMX6_Platform_SDK" rel="nofollow" target="_blank"&gt;https://github.com/backenklee/swp-report/tree/master/iMX6_Platform_SDK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 May 2018 02:10:47 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2018-05-21T02:10:47Z</dc:date>
    <item>
      <title>Inconsistency in I2C Interface</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Inconsistency-in-I2C-Interface/m-p/750933#M116867</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;We notice inconsistency in data received from touch controller.&lt;/SPAN&gt;&lt;/P&gt;&lt;UL style="margin-top: 0cm;"&gt;&lt;LI&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;We get valid data for few cycle&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;We get data read error for few touch input&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;We get NAK for data read from touch after address cycle.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;We get ACK for the data but data read is FF all the time( here the I2C clock is held low for one or more cycle in between 8 bit read) &lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;I have summarized all data in &lt;SPAN style="text-decoration: underline;"&gt;Touch panel I2C Issue.PPT&lt;/SPAN&gt; and LA waveform capture(PNG Image).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;Sachin&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2018 14:47:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Inconsistency-in-I2C-Interface/m-p/750933#M116867</guid>
      <dc:creator>sachinmohankura</dc:creator>
      <dc:date>2018-05-14T14:47:36Z</dc:date>
    </item>
    <item>
      <title>Re: Inconsistency in I2C Interface</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Inconsistency-in-I2C-Interface/m-p/750934#M116868</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;SPAN style="font-size: 12.0pt;"&gt;Sachin&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;issue may be caused by signals noise or operating systems delays, so one can try to&lt;/P&gt;&lt;P&gt;decrease operating i2c frequency, add delays and descrease pull resistors values.&lt;/P&gt;&lt;P&gt;May be recommended to try with baremetal sdk (or freertos)&lt;/P&gt;&lt;P&gt;Github SDK&lt;BR /&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fgithub.com%2Fbackenklee%2Fswp-report%2Ftree%2Fmaster%2FiMX6_Platform_SDK" rel="nofollow" target="_blank"&gt;https://github.com/backenklee/swp-report/tree/master/iMX6_Platform_SDK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 May 2018 02:10:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Inconsistency-in-I2C-Interface/m-p/750934#M116868</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-05-21T02:10:47Z</dc:date>
    </item>
  </channel>
</rss>

