<?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 Disabling I2C Automatic Stop? in Kinetis Software Development Kit</title>
    <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Disabling-I2C-Automatic-Stop/m-p/442600#M2860</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For an I2C device I'm trying to use, it's required to gang up a bunch of reads and writes in sequence with a STOP signal only at the very end. Here is the reasoning:&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial, Bold; font-size: 14pt; color: #365f91;"&gt;&lt;STRONG&gt;9.4 End of Communication Session / Window&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN style="font-family: Arial; font-size: 11pt; color: #000000;"&gt;Similar to other Azoteq I&lt;SPAN style="font-size: 7pt;"&gt;2&lt;SPAN style="font-size: 11pt;"&gt;C devices, to end the I&lt;SPAN style="font-size: 7pt;"&gt;2&lt;SPAN style="font-size: 11pt;"&gt;C communication session, a STOP command&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;is given. When sending numerous read and write commands in one communication cycle, a&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;repeated start command must be used to stack them together (since a STOP will jump out of&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;the communication window, which is not desired).&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;The STOP will then end the communication, and the &lt;SPAN style="font-family: Arial, Bold; font-size: 11pt; color: #1f497d;"&gt;&lt;STRONG&gt;IQS263 &lt;/STRONG&gt;&lt;SPAN style="font-family: Arial; font-size: 11pt; color: #000000;"&gt;will return to process a new set of&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;data. Once this is obtained, the communication window will again become available (RDY set&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;LOW).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR style="text-align: -webkit-auto;" /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 11pt; font-family: Arial;"&gt;After running into issue after issue with the PEx I2C_LDD driver, I'm considering a switch to the fsl_i2c driver but it doesn't look like it supports this use case. I can't see any way to NOT send a STOP condition on send or receive. Am I correct in this conclusion?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 Jun 2015 02:26:29 GMT</pubDate>
    <dc:creator>indraastra</dc:creator>
    <dc:date>2015-06-30T02:26:29Z</dc:date>
    <item>
      <title>Disabling I2C Automatic Stop?</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Disabling-I2C-Automatic-Stop/m-p/442600#M2860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For an I2C device I'm trying to use, it's required to gang up a bunch of reads and writes in sequence with a STOP signal only at the very end. Here is the reasoning:&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial, Bold; font-size: 14pt; color: #365f91;"&gt;&lt;STRONG&gt;9.4 End of Communication Session / Window&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN style="font-family: Arial; font-size: 11pt; color: #000000;"&gt;Similar to other Azoteq I&lt;SPAN style="font-size: 7pt;"&gt;2&lt;SPAN style="font-size: 11pt;"&gt;C devices, to end the I&lt;SPAN style="font-size: 7pt;"&gt;2&lt;SPAN style="font-size: 11pt;"&gt;C communication session, a STOP command&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;is given. When sending numerous read and write commands in one communication cycle, a&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;repeated start command must be used to stack them together (since a STOP will jump out of&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;the communication window, which is not desired).&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;The STOP will then end the communication, and the &lt;SPAN style="font-family: Arial, Bold; font-size: 11pt; color: #1f497d;"&gt;&lt;STRONG&gt;IQS263 &lt;/STRONG&gt;&lt;SPAN style="font-family: Arial; font-size: 11pt; color: #000000;"&gt;will return to process a new set of&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;data. Once this is obtained, the communication window will again become available (RDY set&lt;BR /&gt;&lt;SPAN style="font-size: 11pt;"&gt;LOW).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR style="text-align: -webkit-auto;" /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-size: 11pt; font-family: Arial;"&gt;After running into issue after issue with the PEx I2C_LDD driver, I'm considering a switch to the fsl_i2c driver but it doesn't look like it supports this use case. I can't see any way to NOT send a STOP condition on send or receive. Am I correct in this conclusion?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jun 2015 02:26:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Disabling-I2C-Automatic-Stop/m-p/442600#M2860</guid>
      <dc:creator>indraastra</dc:creator>
      <dc:date>2015-06-30T02:26:29Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling I2C Automatic Stop?</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Disabling-I2C-Automatic-Stop/m-p/442601#M2861</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Vishal Talwar:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The I2C driver in KSDK allows one switch from Write to Read in-between a transfer (using a Repeated Start) when calling the function &lt;STRONG&gt;I2C_DRV_MasterReceiveData()&lt;/STRONG&gt; or &lt;STRONG&gt;I2C_DRV_MasterReceiveDataBlocking&lt;/STRONG&gt;. In case you would need more than 1 Write/Read switch before the STOP condition then you are right, this is not supported but that is not a typical use case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Actually I checked the datasheet for your device (IQS263) and the KSDK I2C driver can be used for the 3 types of transfers: &lt;STRONG&gt;Current Address Read&lt;/STRONG&gt;, &lt;STRONG&gt;Random Read&lt;/STRONG&gt; and &lt;STRONG&gt;Write&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps to clarify. Let me know if you still face doubts.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Regards!,&lt;BR /&gt;Jorge Gonzalez&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>Thu, 02 Jul 2015 22:36:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Disabling-I2C-Automatic-Stop/m-p/442601#M2861</guid>
      <dc:creator>Jorge_Gonzalez</dc:creator>
      <dc:date>2015-07-02T22:36:31Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling I2C Automatic Stop?</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Disabling-I2C-Automatic-Stop/m-p/442602#M2862</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm having the same problem.&amp;nbsp; Using SDK 2.2 for KL27.&lt;/P&gt;&lt;P&gt;How do I send Current Address Read?&amp;nbsp; The drivers always send out the register address.&amp;nbsp; Can I put in a NULL for the register address?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Dec 2017 21:44:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Disabling-I2C-Automatic-Stop/m-p/442602#M2862</guid>
      <dc:creator>bcstewart</dc:creator>
      <dc:date>2017-12-21T21:44:44Z</dc:date>
    </item>
  </channel>
</rss>

