<?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>Kinetis Microcontrollers中的主题 Re: R41Z I2C compatibility with Raspberry Pi?</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/R41Z-I2C-compatibility-with-Raspberry-Pi/m-p/884681#M52391</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Estephania,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First of all thank you for your concern about the issue. As I said to perform my application I took as a baseline the "&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;frdmkw41z_wireless_examples_thread_router_eligible_device_freertos" project. In this project I want to transmit data from my Raspberry Pi Zero to the R41Z module and viceversa. The R41Z module is the I2C slave so I initialize the I2C pins and the slave configuration as follows:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;Defines of I2C:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77061iE289840F19588318/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;I2C pins initialization:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77107iC7F8B66C4A5DAF66/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;I2C slave configuration:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_3.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77146i5DD85BD4871A2DFF/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_3.png" alt="pastedImage_3.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;I2C slave callback:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_4.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77180iB4ED0AAA02428879/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_4.png" alt="pastedImage_4.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;All I2C configuration and use is taken from the &lt;STRONG&gt;"frdmkw41z_driver_examples_i2c_interrupt_transfer"&lt;/STRONG&gt; example project. I put a NVIC priority of the slave in my application to 6:&amp;nbsp;NVIC_SetPriority(I2C_SLAVE_IRQ, 6);&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;I DO NOT USE SERIAL MANAGER I do not know if it is the way I should take but&amp;nbsp;I did not find any&amp;nbsp;documentation explaining how to carry the I2C operations with Serial Manager, I use I2C direct drivers (i2c interrupt transfer).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;So if the R41Z module want to transmit data to the RPZ it is done inside a CoAP callback, in this CoAP callback I send to the RPZ a digital pin interrupt and in this moment the RPZ read to the R41Z 32 bytes of data that at 100 kHz it does not work correctly.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Viceversa, if the RPZ want to transmit data to the R41Z periodically, the RPZ send a digital output that my R41Z takes as an interrupt, I put to the CoAP queue message a CoAP transmision function. In this function, I wait that the RPZ write 64 bytes of data to the R41Z in a for loop waiting for 64 g_SlaveCompletionFlags and finally, I send a CoAP POST with the frame of data (the images I posted of the incorrect frame of data received are from this operation).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;I send here the code of the transmission from RPZ to the R41Z:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;The input interrupt in the R41Z when I send a digital output with the Raspberry Pi Zero. (I put the APP_ReportAviso function to the CoAP messages queue).&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_10.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77181i97DBBB873A1BC948/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_10.png" alt="pastedImage_10.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;The APP_ReportAviso function:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_12.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77062iE2CBE8B1A11E9898/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_12.png" alt="pastedImage_12.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_13.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77455iDC9E762DFF93FEC2/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_13.png" alt="pastedImage_13.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;In this function I clean the I2C receive buffer and I wait 64 bytes of transfer with 64 g_slaveCompletionFlag. After that I print the frame of data received and I send a CoAP POST. &lt;STRONG&gt;Here I realize that my frame of data are not correctly transmited by I2C between Raspberry Pi Zero and R41Z.&amp;nbsp;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;I do not know if you need more information about my application to solve the I2C transmission issue between RPZ and R41Z. I appreciate so much your help Estephania.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Diego Comín&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 Jan 2019 08:52:51 GMT</pubDate>
    <dc:creator>diegocomin</dc:creator>
    <dc:date>2019-01-24T08:52:51Z</dc:date>
    <item>
      <title>R41Z I2C compatibility with Raspberry Pi?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/R41Z-I2C-compatibility-with-Raspberry-Pi/m-p/884678#M52388</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a setup, where a R41Z module is connected via I2C to my Raspberry Pi Zero. The R41Z acts as a slave and my Raspberry Pi Zero as the master. I put simple communications via I2C to transmit some frames and I realized that the R41Z modules only transmit all the caracters well with only 10kHz Speed Bus!!! How this can be possible??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I increment the bus speed, for example at 100 kHz I attach here the frame of data I obtain:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/63856iEA27991915F7C0E1/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;If I increment the bus speed to 400 kHz (I2C standard speed) I obtain a horrible response to the R41Z:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/63857i7FD268A12E57C00F/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I took a look to the I2C protocol with a protocol analyzer and the data are being sent correctly from the Raspberry Pi to the R41Z.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_3.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/63894iF60BD629D5420A47/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_3.png" alt="pastedImage_3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The R41Z can not interpret the I2C commands with more than 10 kHz. How can be it possible? How can I solve this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Diego Comín&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jan 2019 13:54:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/R41Z-I2C-compatibility-with-Raspberry-Pi/m-p/884678#M52388</guid>
      <dc:creator>diegocomin</dc:creator>
      <dc:date>2019-01-18T13:54:04Z</dc:date>
    </item>
    <item>
      <title>Re: R41Z I2C compatibility with Raspberry Pi?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/R41Z-I2C-compatibility-with-Raspberry-Pi/m-p/884679#M52389</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thr program base I used to make the communication is the&amp;nbsp;frdmkw41z_wireless_examples_thread_router_eligible_device_freertos&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jan 2019 13:04:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/R41Z-I2C-compatibility-with-Raspberry-Pi/m-p/884679#M52389</guid>
      <dc:creator>diegocomin</dc:creator>
      <dc:date>2019-01-21T13:04:47Z</dc:date>
    </item>
    <item>
      <title>Re: R41Z I2C compatibility with Raspberry Pi?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/R41Z-I2C-compatibility-with-Raspberry-Pi/m-p/884680#M52390</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is most likely that the issue you are seeing it's related to the implementation in the application layer. How are you doing it?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you using the serial manager or the direct drivers?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Estephania&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2019 16:10:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/R41Z-I2C-compatibility-with-Raspberry-Pi/m-p/884680#M52390</guid>
      <dc:creator>stephanie_m</dc:creator>
      <dc:date>2019-01-23T16:10:57Z</dc:date>
    </item>
    <item>
      <title>Re: R41Z I2C compatibility with Raspberry Pi?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/R41Z-I2C-compatibility-with-Raspberry-Pi/m-p/884681#M52391</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Estephania,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First of all thank you for your concern about the issue. As I said to perform my application I took as a baseline the "&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;frdmkw41z_wireless_examples_thread_router_eligible_device_freertos" project. In this project I want to transmit data from my Raspberry Pi Zero to the R41Z module and viceversa. The R41Z module is the I2C slave so I initialize the I2C pins and the slave configuration as follows:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;Defines of I2C:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77061iE289840F19588318/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;I2C pins initialization:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77107iC7F8B66C4A5DAF66/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;I2C slave configuration:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_3.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77146i5DD85BD4871A2DFF/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_3.png" alt="pastedImage_3.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;I2C slave callback:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_4.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77180iB4ED0AAA02428879/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_4.png" alt="pastedImage_4.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;All I2C configuration and use is taken from the &lt;STRONG&gt;"frdmkw41z_driver_examples_i2c_interrupt_transfer"&lt;/STRONG&gt; example project. I put a NVIC priority of the slave in my application to 6:&amp;nbsp;NVIC_SetPriority(I2C_SLAVE_IRQ, 6);&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;I DO NOT USE SERIAL MANAGER I do not know if it is the way I should take but&amp;nbsp;I did not find any&amp;nbsp;documentation explaining how to carry the I2C operations with Serial Manager, I use I2C direct drivers (i2c interrupt transfer).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;So if the R41Z module want to transmit data to the RPZ it is done inside a CoAP callback, in this CoAP callback I send to the RPZ a digital pin interrupt and in this moment the RPZ read to the R41Z 32 bytes of data that at 100 kHz it does not work correctly.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Viceversa, if the RPZ want to transmit data to the R41Z periodically, the RPZ send a digital output that my R41Z takes as an interrupt, I put to the CoAP queue message a CoAP transmision function. In this function, I wait that the RPZ write 64 bytes of data to the R41Z in a for loop waiting for 64 g_SlaveCompletionFlags and finally, I send a CoAP POST with the frame of data (the images I posted of the incorrect frame of data received are from this operation).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;I send here the code of the transmission from RPZ to the R41Z:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;The input interrupt in the R41Z when I send a digital output with the Raspberry Pi Zero. (I put the APP_ReportAviso function to the CoAP messages queue).&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_10.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77181i97DBBB873A1BC948/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_10.png" alt="pastedImage_10.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="background-color: #ffffff; color: #51626f; "&gt;The APP_ReportAviso function:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_12.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77062iE2CBE8B1A11E9898/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_12.png" alt="pastedImage_12.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_13.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/77455iDC9E762DFF93FEC2/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_13.png" alt="pastedImage_13.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;In this function I clean the I2C receive buffer and I wait 64 bytes of transfer with 64 g_slaveCompletionFlag. After that I print the frame of data received and I send a CoAP POST. &lt;STRONG&gt;Here I realize that my frame of data are not correctly transmited by I2C between Raspberry Pi Zero and R41Z.&amp;nbsp;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;I do not know if you need more information about my application to solve the I2C transmission issue between RPZ and R41Z. I appreciate so much your help Estephania.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Diego Comín&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jan 2019 08:52:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/R41Z-I2C-compatibility-with-Raspberry-Pi/m-p/884681#M52391</guid>
      <dc:creator>diegocomin</dc:creator>
      <dc:date>2019-01-24T08:52:51Z</dc:date>
    </item>
    <item>
      <title>Re: R41Z I2C compatibility with Raspberry Pi?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/R41Z-I2C-compatibility-with-Raspberry-Pi/m-p/884682#M52392</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/estephania_martinez"&gt;estephania_martinez&lt;/A&gt;‌ Have you found any solution to the issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2019 15:31:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/R41Z-I2C-compatibility-with-Raspberry-Pi/m-p/884682#M52392</guid>
      <dc:creator>diegocomin</dc:creator>
      <dc:date>2019-01-30T15:31:55Z</dc:date>
    </item>
  </channel>
</rss>

