<?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>i.MX ProcessorsのトピックWhy MX6Q PMIC i2c access failed after entered linux kernel</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Why-MX6Q-PMIC-i2c-access-failed-after-entered-linux-kernel/m-p/243837#M20770</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My sabresd based new custom board, kernel report error:&lt;/P&gt;&lt;P&gt;mc_pfuze 1-0008: recv failed!:-5,0&lt;/P&gt;&lt;P&gt;mc_pfuze: probe of 1-0008 failed with error -5&lt;/P&gt;&lt;P&gt;Hardware reset to PMIC, boot loader can probe PMIC properly:&lt;/P&gt;&lt;P&gt;Found PFUZE100! deviceid=10,revid=11&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Because our linux system software reset is WDOG based, it won't reset PMIC. &lt;/P&gt;&lt;P&gt;After reset ,boot loader will not report PFUZE100 found. Strange issue, Why?&lt;/P&gt;&lt;P&gt; With oscilloscope support, I found the PFUZE100 i2c access failed with no ACK in 9th i2c clk.&lt;/P&gt;&lt;P&gt;Anyone ever encounter issue like this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 21 Sep 2013 11:55:44 GMT</pubDate>
    <dc:creator>raymondwang</dc:creator>
    <dc:date>2013-09-21T11:55:44Z</dc:date>
    <item>
      <title>Why MX6Q PMIC i2c access failed after entered linux kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Why-MX6Q-PMIC-i2c-access-failed-after-entered-linux-kernel/m-p/243837#M20770</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My sabresd based new custom board, kernel report error:&lt;/P&gt;&lt;P&gt;mc_pfuze 1-0008: recv failed!:-5,0&lt;/P&gt;&lt;P&gt;mc_pfuze: probe of 1-0008 failed with error -5&lt;/P&gt;&lt;P&gt;Hardware reset to PMIC, boot loader can probe PMIC properly:&lt;/P&gt;&lt;P&gt;Found PFUZE100! deviceid=10,revid=11&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Because our linux system software reset is WDOG based, it won't reset PMIC. &lt;/P&gt;&lt;P&gt;After reset ,boot loader will not report PFUZE100 found. Strange issue, Why?&lt;/P&gt;&lt;P&gt; With oscilloscope support, I found the PFUZE100 i2c access failed with no ACK in 9th i2c clk.&lt;/P&gt;&lt;P&gt;Anyone ever encounter issue like this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Sep 2013 11:55:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Why-MX6Q-PMIC-i2c-access-failed-after-entered-linux-kernel/m-p/243837#M20770</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2013-09-21T11:55:44Z</dc:date>
    </item>
    <item>
      <title>Re: Why MX6Q PMIC i2c access failed after entered linux kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Why-MX6Q-PMIC-i2c-access-failed-after-entered-linux-kernel/m-p/243838#M20771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Touch panel and PMIC share the same i2c bus but has different pull up power voltage.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2013 07:26:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Why-MX6Q-PMIC-i2c-access-failed-after-entered-linux-kernel/m-p/243838#M20771</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2013-09-26T07:26:47Z</dc:date>
    </item>
  </channel>
</rss>

