<?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: I2C Bus 1 issue in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/I2C-Bus-1-issue/m-p/740675#M115265</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jamal&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one can try to debug it in ..drivers/i2c/mxc_i2c.c or use i2c tools&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/docs/DOC-1477"&gt;All Boards I2C-tools&lt;/A&gt;&amp;nbsp;&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>Tue, 13 Feb 2018 08:03:45 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2018-02-13T08:03:45Z</dc:date>
    <item>
      <title>I2C Bus 1 issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I2C-Bus-1-issue/m-p/740674#M115264</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a custom i.MX6QD board. Instead of using WM8962 as codec we used WM8985 Codec.&lt;/P&gt;&lt;P&gt;I was trying to check the I2C Control interface.&lt;/P&gt;&lt;P&gt;i2c probe was able to display the address but i2c md is failing. Can anyone tell me what is going on here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/7976i45CDEB7A4601B21A/image-size/large?v=v2&amp;amp;px=999" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Feb 2018 06:46:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I2C-Bus-1-issue/m-p/740674#M115264</guid>
      <dc:creator>jamalmohiuddin</dc:creator>
      <dc:date>2018-02-13T06:46:45Z</dc:date>
    </item>
    <item>
      <title>Re: I2C Bus 1 issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I2C-Bus-1-issue/m-p/740675#M115265</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jamal&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one can try to debug it in ..drivers/i2c/mxc_i2c.c or use i2c tools&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/docs/DOC-1477"&gt;All Boards I2C-tools&lt;/A&gt;&amp;nbsp;&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>Tue, 13 Feb 2018 08:03:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I2C-Bus-1-issue/m-p/740675#M115265</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-02-13T08:03:45Z</dc:date>
    </item>
  </channel>
</rss>

