<?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>LPC MicrocontrollersのトピックLPC3250FET296: i2c bus hang</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC3250FET296-i2c-bus-hang/m-p/723202#M29224</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;I am using a custom board based on&amp;nbsp;LPC3250FET296 . It is running Linux 3.18 kernel.&lt;/P&gt;&lt;P&gt;I am seeing i2c bus hangs with the following messages:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: Master timed out. stat = 2a60, cntrl = 000e. Resetting master...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus busy. Slave addr = 40, cntrl = 0, stat = 2a60&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus is still active after xfer. Reset it...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus is still active after xfer. Reset it...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: Master timed out. stat = 2a60, cntrl = 000e. Resetting master...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus busy. Slave addr = 40, cntrl = 0, stat = 2a60&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus is still active after xfer. Reset it...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus is still active after xfer. Reset it...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:59 (none) user.err kernel: i2c-adapter i2c-1: Master timed out. stat = 2a60, cntrl = 000e. Resetting master...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:59 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus busy. Slave addr = 41, cntrl = 0, stat = 2a60&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After googling a bit I found the following thread:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/316813"&gt;https://community.nxp.com/thread/316813&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This talks about recovering the i2c bus by making the master send 9 clock pulses. I see that some of the i2c controllers have (ST, OMAP etc.) have implemented the recovery mechanism but the recovery mechanism is not implemented for&amp;nbsp;&lt;/P&gt;&lt;P&gt;Philips-IP3204 I2C controllers.&lt;/P&gt;&lt;P&gt;Just wanted to know if someone has tried this out. From my understanding of the data sheet apparently GPIO functionality is not available for SCL pin here.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Jan 2018 08:52:36 GMT</pubDate>
    <dc:creator>kimran</dc:creator>
    <dc:date>2018-01-15T08:52:36Z</dc:date>
    <item>
      <title>LPC3250FET296: i2c bus hang</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC3250FET296-i2c-bus-hang/m-p/723202#M29224</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;I am using a custom board based on&amp;nbsp;LPC3250FET296 . It is running Linux 3.18 kernel.&lt;/P&gt;&lt;P&gt;I am seeing i2c bus hangs with the following messages:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: Master timed out. stat = 2a60, cntrl = 000e. Resetting master...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus busy. Slave addr = 40, cntrl = 0, stat = 2a60&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus is still active after xfer. Reset it...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus is still active after xfer. Reset it...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: Master timed out. stat = 2a60, cntrl = 000e. Resetting master...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus busy. Slave addr = 40, cntrl = 0, stat = 2a60&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus is still active after xfer. Reset it...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:58 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus is still active after xfer. Reset it...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:59 (none) user.err kernel: i2c-adapter i2c-1: Master timed out. stat = 2a60, cntrl = 000e. Resetting master...&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Jan 1 01:43:59 (none) user.err kernel: i2c-adapter i2c-1: PNX4008-I2C1: Bus busy. Slave addr = 41, cntrl = 0, stat = 2a60&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After googling a bit I found the following thread:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/316813"&gt;https://community.nxp.com/thread/316813&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This talks about recovering the i2c bus by making the master send 9 clock pulses. I see that some of the i2c controllers have (ST, OMAP etc.) have implemented the recovery mechanism but the recovery mechanism is not implemented for&amp;nbsp;&lt;/P&gt;&lt;P&gt;Philips-IP3204 I2C controllers.&lt;/P&gt;&lt;P&gt;Just wanted to know if someone has tried this out. From my understanding of the data sheet apparently GPIO functionality is not available for SCL pin here.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Jan 2018 08:52:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC3250FET296-i2c-bus-hang/m-p/723202#M29224</guid>
      <dc:creator>kimran</dc:creator>
      <dc:date>2018-01-15T08:52:36Z</dc:date>
    </item>
    <item>
      <title>Re: LPC3250FET296: i2c bus hang</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC3250FET296-i2c-bus-hang/m-p/723203#M29225</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Imran,&lt;/P&gt;&lt;P&gt;As a complementary information regarding the thread that you already found, you could also refer to the following:&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.nxp.com/thread/429674"&gt;https://community.nxp.com/thread/429674&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will be useful for you.&lt;/P&gt;&lt;P&gt;Best regards!&lt;/P&gt;&lt;P&gt;/Carlos&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>Thu, 18 Jan 2018 22:57:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC3250FET296-i2c-bus-hang/m-p/723203#M29225</guid>
      <dc:creator>CarlosCasillas</dc:creator>
      <dc:date>2018-01-18T22:57:19Z</dc:date>
    </item>
  </channel>
</rss>

