<?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: A version of i2c_int_k_fb.c without reg_addr in MQX Software Solutions</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/A-version-of-i2c-int-k-fb-c-without-reg-addr/m-p/340054#M10951</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Sol! It has been worked around by using the register address as a configuration byte.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hui&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 06 Oct 2014 20:17:25 GMT</pubDate>
    <dc:creator>huishao2</dc:creator>
    <dc:date>2014-10-06T20:17:25Z</dc:date>
    <item>
      <title>A version of i2c_int_k_fb.c without reg_addr</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/A-version-of-i2c-int-k-fb-c-without-reg-addr/m-p/340052#M10949</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In thread &lt;A _jive_internal="true" data-content-finding="Community" href="https://community.nxp.com/message/325465#325465"&gt;&lt;SPAN style="color: #3778c7;"&gt;MQX 4.0 I2C Locks Up&lt;/SPAN&gt;&lt;/A&gt;, i2c_int_k_fb.c is used to replace interrupt based I2C driver to resolve lock up problem. Question is, is there a version of this driver that does NOT need to configure register address like the highlighted below (from AN4652)? My I2C device doesn't have a register inside for access.&amp;nbsp; It only receives simply read and write without need to specify register index.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ioctl(file_iic0, IO_IOCTL_I2C_SET_BAUD, &amp;amp;param);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i2c_buf_tx.dst_addr = 0x50; // The I2C slave address&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000;"&gt;i2c_buf_tx.reg_addr = 0; // You may view this as a register&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000;"&gt;// address or a command to slave.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i2c_buf_rx.dst_addr = 0x50; // The same as above, for receiving&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i2c_buf_rx.reg_addr = 0; // The same as above, for receiving&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for(i=0;i&amp;lt;8;i++) // initialize data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i2c_buf_tx.data[i] = 0xb0+i;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;while(1)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;printf("---------------------\n");&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;// send 4 bytes to slave&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;len = fwrite(&amp;amp;i2c_buf_tx, 1, 4, file_iic0);&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Sep 2014 23:19:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/A-version-of-i2c-int-k-fb-c-without-reg-addr/m-p/340052#M10949</guid>
      <dc:creator>huishao2</dc:creator>
      <dc:date>2014-09-23T23:19:02Z</dc:date>
    </item>
    <item>
      <title>Re: A version of i2c_int_k_fb.c without reg_addr</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/A-version-of-i2c-int-k-fb-c-without-reg-addr/m-p/340053#M10950</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hui Shao,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;Did you check the i2c driver that is included in MQX? You can find more information about this driver in the Freescale MQX™ RTOS I/O Drivers User’s Guide chapter 12.&amp;nbsp; (C:\Freescale\Freescale_MQX_4_1\doc\mqx)&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri','sans-serif';"&gt;In addition you can find some examples at the path: C:\Freescale\Freescale_MQX_4_1\mqx\examples&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt; Sol &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>Mon, 06 Oct 2014 19:44:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/A-version-of-i2c-int-k-fb-c-without-reg-addr/m-p/340053#M10950</guid>
      <dc:creator>soledad</dc:creator>
      <dc:date>2014-10-06T19:44:56Z</dc:date>
    </item>
    <item>
      <title>Re: A version of i2c_int_k_fb.c without reg_addr</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/A-version-of-i2c-int-k-fb-c-without-reg-addr/m-p/340054#M10951</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Sol! It has been worked around by using the register address as a configuration byte.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hui&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Oct 2014 20:17:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/A-version-of-i2c-int-k-fb-c-without-reg-addr/m-p/340054#M10951</guid>
      <dc:creator>huishao2</dc:creator>
      <dc:date>2014-10-06T20:17:25Z</dc:date>
    </item>
  </channel>
</rss>

