<?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: IMXRT105x LPI2C STOP generated when using kLPI2C_TransferNoStopFlag in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT105x-LPI2C-STOP-generated-when-using-kLPI2C/m-p/1702850#M26297</link>
    <description>&lt;P&gt;There seems to be a timeout that I am missing as the transactons work as I expect if I don't insert a breakpoint in between.&lt;/P&gt;</description>
    <pubDate>Thu, 10 Aug 2023 09:36:02 GMT</pubDate>
    <dc:creator>gavin5342</dc:creator>
    <dc:date>2023-08-10T09:36:02Z</dc:date>
    <item>
      <title>IMXRT105x LPI2C STOP generated when using kLPI2C_TransferNoStopFlag</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT105x-LPI2C-STOP-generated-when-using-kLPI2C/m-p/1701979#M26271</link>
      <description>&lt;P&gt;I want to generate a write (for a command) without STOP followed by a read with a repeated START.&lt;/P&gt;&lt;P&gt;When I use&amp;nbsp;LPI2C_RTOS_Transfer to send a transfer with&amp;nbsp;kLPI2C_TransferNoStopFlag set, I see the STOP condition is generated on the I2C bus as though&amp;nbsp;kLPI2C_TransferDefaultFlag were set.&lt;/P&gt;&lt;P&gt;Has anyone else seen this and/or know how to fix?&lt;/P&gt;&lt;P&gt;A workaround would be to make the command subaddress, but I would need to ignore the NAK that the slave sends when it has received the command.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Aug 2023 13:35:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT105x-LPI2C-STOP-generated-when-using-kLPI2C/m-p/1701979#M26271</guid>
      <dc:creator>gavin5342</dc:creator>
      <dc:date>2023-08-09T13:35:41Z</dc:date>
    </item>
    <item>
      <title>Re: IMXRT105x LPI2C STOP generated when using kLPI2C_TransferNoStopFlag</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT105x-LPI2C-STOP-generated-when-using-kLPI2C/m-p/1702850#M26297</link>
      <description>&lt;P&gt;There seems to be a timeout that I am missing as the transactons work as I expect if I don't insert a breakpoint in between.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Aug 2023 09:36:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT105x-LPI2C-STOP-generated-when-using-kLPI2C/m-p/1702850#M26297</guid>
      <dc:creator>gavin5342</dc:creator>
      <dc:date>2023-08-10T09:36:02Z</dc:date>
    </item>
    <item>
      <title>Re: IMXRT105x LPI2C STOP generated when using kLPI2C_TransferNoStopFlag</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT105x-LPI2C-STOP-generated-when-using-kLPI2C/m-p/1703163#M26302</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/195455"&gt;@gavin5342&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I2C timings often will be affected by debug halts, which is why the LPI2C module features a debug mode, described on Section "46.3.4 Debug mode" of the Reference Manual. You could try implementing this feature for further debugging.&lt;/P&gt;
&lt;P&gt;BR,&lt;BR /&gt;Edwin.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Aug 2023 17:48:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT105x-LPI2C-STOP-generated-when-using-kLPI2C/m-p/1703163#M26302</guid>
      <dc:creator>EdwinHz</dc:creator>
      <dc:date>2023-08-10T17:48:37Z</dc:date>
    </item>
  </channel>
</rss>

