<?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 I2C bus got stuck on ls1021aiot based custom board  in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/I2C-bus-got-stuck-on-ls1021aiot-based-custom-board/m-p/644417#M2156</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been experiencing some undefined behavior on i2c bus . I have a 4 devices on ls1021aiot based custom board&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;•&amp;nbsp;&lt;/SPAN&gt;Temperature ADT7461 (0x4C) &amp;nbsp; &amp;nbsp; ---- linux driver is attached for this device&amp;nbsp;&lt;BR /&gt;• Board clocking 6V49205B (0x69) &amp;nbsp;---- No driver is attached &amp;nbsp;for this device&amp;nbsp;&lt;BR /&gt;• PMIC MC34VR500V1ES (0x08) &amp;nbsp; ----- No driver is attached for this device&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;• And controller acting as slave at address 0x70 . &amp;nbsp; ---- linux driver is attached for this device&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;When I do i2cdetect on linux I get following&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;root@bravo:~# i2cdetect -y 1&lt;BR /&gt; 0 1 2 3 4 5 6 7 8 9 a b c d e f&lt;BR /&gt;00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f &lt;BR /&gt;10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f &lt;BR /&gt;20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f &lt;BR /&gt;30: -- -- -- -- -- -- -- -- 38 39 3a 3b 3c 3d 3e 3f &lt;BR /&gt;40: 40 41 42 43 44 45 46 47 48 49 4a 4b UU 4d 4e 4f &lt;BR /&gt;50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- &lt;BR /&gt;60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f &lt;BR /&gt;70: UU 71 72 73 74 75 76 77 &lt;BR /&gt;&lt;A href="mailto:root@bravo:~"&gt;root@bravo:~# &lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;And I cannot access&amp;nbsp;any of my devices now ( ADT7461 (0x4C) &amp;nbsp;and &amp;nbsp;at address 0x70). I can't figure out why this is happening. When I do reboot it doesn't solve the problem when I power cycle the board all the devices comes back and work fine . I suspect that one of the devices is pulling the SDA line low , not sure though. If any one of you have experience this kind of problem can you please help. &amp;nbsp;Is there a way to recover it from linux or u-boot. any help or hint &amp;nbsp;I'll appreciate.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Dhruval&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Feb 2017 19:12:48 GMT</pubDate>
    <dc:creator>dhruvalkumarpat</dc:creator>
    <dc:date>2017-02-16T19:12:48Z</dc:date>
    <item>
      <title>I2C bus got stuck on ls1021aiot based custom board</title>
      <link>https://community.nxp.com/t5/Layerscape/I2C-bus-got-stuck-on-ls1021aiot-based-custom-board/m-p/644417#M2156</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been experiencing some undefined behavior on i2c bus . I have a 4 devices on ls1021aiot based custom board&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;•&amp;nbsp;&lt;/SPAN&gt;Temperature ADT7461 (0x4C) &amp;nbsp; &amp;nbsp; ---- linux driver is attached for this device&amp;nbsp;&lt;BR /&gt;• Board clocking 6V49205B (0x69) &amp;nbsp;---- No driver is attached &amp;nbsp;for this device&amp;nbsp;&lt;BR /&gt;• PMIC MC34VR500V1ES (0x08) &amp;nbsp; ----- No driver is attached for this device&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;• And controller acting as slave at address 0x70 . &amp;nbsp; ---- linux driver is attached for this device&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;When I do i2cdetect on linux I get following&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;root@bravo:~# i2cdetect -y 1&lt;BR /&gt; 0 1 2 3 4 5 6 7 8 9 a b c d e f&lt;BR /&gt;00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f &lt;BR /&gt;10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f &lt;BR /&gt;20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f &lt;BR /&gt;30: -- -- -- -- -- -- -- -- 38 39 3a 3b 3c 3d 3e 3f &lt;BR /&gt;40: 40 41 42 43 44 45 46 47 48 49 4a 4b UU 4d 4e 4f &lt;BR /&gt;50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- &lt;BR /&gt;60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f &lt;BR /&gt;70: UU 71 72 73 74 75 76 77 &lt;BR /&gt;&lt;A href="mailto:root@bravo:~"&gt;root@bravo:~# &lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;And I cannot access&amp;nbsp;any of my devices now ( ADT7461 (0x4C) &amp;nbsp;and &amp;nbsp;at address 0x70). I can't figure out why this is happening. When I do reboot it doesn't solve the problem when I power cycle the board all the devices comes back and work fine . I suspect that one of the devices is pulling the SDA line low , not sure though. If any one of you have experience this kind of problem can you please help. &amp;nbsp;Is there a way to recover it from linux or u-boot. any help or hint &amp;nbsp;I'll appreciate.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Dhruval&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Feb 2017 19:12:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/I2C-bus-got-stuck-on-ls1021aiot-based-custom-board/m-p/644417#M2156</guid>
      <dc:creator>dhruvalkumarpat</dc:creator>
      <dc:date>2017-02-16T19:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: I2C bus got stuck on ls1021aiot based custom board</title>
      <link>https://community.nxp.com/t5/Layerscape/I2C-bus-got-stuck-on-ls1021aiot-based-custom-board/m-p/644418#M2157</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; background: white;"&gt;Perhaps that some I2C device on your board requires a few time to start after power up.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt; background: white;"&gt;Add a delay after power up before I2C device reading.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Pavel Chubakov&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&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>Fri, 17 Feb 2017 02:10:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/I2C-bus-got-stuck-on-ls1021aiot-based-custom-board/m-p/644418#M2157</guid>
      <dc:creator>Pavel</dc:creator>
      <dc:date>2017-02-17T02:10:43Z</dc:date>
    </item>
  </channel>
</rss>

