<?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>MCUXpresso IDE中的主题 Re: Blocking i2c module problem</title>
    <link>https://community.nxp.com/t5/MCUXpresso-IDE/Blocking-i2c-module-problem/m-p/2134925#M10432</link>
    <description>Sorry, any answers on that?</description>
    <pubDate>Wed, 16 Jul 2025 10:25:28 GMT</pubDate>
    <dc:creator>Transidico</dc:creator>
    <dc:date>2025-07-16T10:25:28Z</dc:date>
    <item>
      <title>Blocking i2c module problem</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/Blocking-i2c-module-problem/m-p/2133390#M10427</link>
      <description>&lt;P&gt;Good morning,&lt;/P&gt;&lt;P&gt;I am carrying out a large project. I am running multiple interrupts every few ms. Unfortunately I realised that it conflicts with the i2c module because I was polling it with the I2C_MasterTransferBlocking function. By doing so, it was blocking my repeated interrupts. This is why I decided to use the i2c module also in interrupt. Unfortunately, I don't know how best to perform the transmission via iterrupt without using a while to wait for the transmission to complete. Attached is a simpler, cleaned-up project of what I am currently doing, so that I can understand how best to carry out i2c transmission and print on the display.&lt;/P&gt;&lt;P&gt;Could you kindly advise me on this?&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;BR /&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2025 14:24:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/Blocking-i2c-module-problem/m-p/2133390#M10427</guid>
      <dc:creator>Transidico</dc:creator>
      <dc:date>2025-07-14T14:24:28Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking i2c module problem</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/Blocking-i2c-module-problem/m-p/2134925#M10432</link>
      <description>Sorry, any answers on that?</description>
      <pubDate>Wed, 16 Jul 2025 10:25:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/Blocking-i2c-module-problem/m-p/2134925#M10432</guid>
      <dc:creator>Transidico</dc:creator>
      <dc:date>2025-07-16T10:25:28Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking i2c module problem</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/Blocking-i2c-module-problem/m-p/2135964#M10435</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/240937"&gt;@Transidico&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;To better assist you, could you clarify whether the I2C transfer needs to be terminated in order to display the message?&lt;BR /&gt;If that is the case, it seems your application is inherently blocking, as it relies on another process to complete before proceeding. Given this dependency, the approach you are currently implementing appears to be the most appropriate solution.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Hope it helps.&lt;BR /&gt;BR&lt;BR /&gt;Habib&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jul 2025 16:16:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/Blocking-i2c-module-problem/m-p/2135964#M10435</guid>
      <dc:creator>Habib_MS</dc:creator>
      <dc:date>2025-07-17T16:16:21Z</dc:date>
    </item>
  </channel>
</rss>

