<?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: Example project LPI2C_MASTER in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Example-project-LPI2C-MASTER/m-p/685645#M1052</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Yes, that's correct. The S32K144 device has only one LPI2C instance. So you need two boards, one as a master and one as a slave, or another I2C device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Jun 2017 14:23:45 GMT</pubDate>
    <dc:creator>danielmartynek</dc:creator>
    <dc:date>2017-06-14T14:23:45Z</dc:date>
    <item>
      <title>Example project LPI2C_MASTER</title>
      <link>https://community.nxp.com/t5/S32K/Example-project-LPI2C-MASTER/m-p/685642#M1049</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;For the LPI2C_MASTER project&amp;nbsp;, I don't seem to understand the wiring connection.&amp;nbsp;for S32K44EVB-Q100 the following describes the wiring:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIN FUNCTION&amp;nbsp;|&amp;nbsp;S32K144EVB-Q100 |&amp;nbsp;S32K144-MB&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ----------------|---------------|--------------&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; LPI2C SCL (\b PTA3)&amp;nbsp;|J1-3 - Slave SCL&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |J9-30 - Slave SCL&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; LPI2C SDA (\b PTA2)&amp;nbsp;|J1-1 - Slave SDA&amp;nbsp;&amp;nbsp;&amp;nbsp; |J9-29 - Slave SDA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; GND&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (\b GND)&amp;nbsp; |J3-11 - Slave GND&amp;nbsp;&amp;nbsp;&amp;nbsp; |J6 - Slave GND&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So PTA3/PTA2 where are they connected to, don't&amp;nbsp;we&amp;nbsp;need a pull up on SCL(PTA3)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Jun 2017 20:51:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Example-project-LPI2C-MASTER/m-p/685642#M1049</guid>
      <dc:creator>hajianik</dc:creator>
      <dc:date>2017-06-13T20:51:52Z</dc:date>
    </item>
    <item>
      <title>Re: Example project LPI2C_MASTER</title>
      <link>https://community.nxp.com/t5/S32K/Example-project-LPI2C-MASTER/m-p/685643#M1050</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;These pins PTA2/PTA3 are connected only to the J1 header.&lt;/P&gt;&lt;P&gt;Pin configuration of this example is set in 2-pin open drain mode (see register MCFGR1) which requires pull-ups. Internal pull-ups are enabled by default (PORTA[PCR]) so you can see the communication on scope. It might work but in general these internal pull-ups are week for I2C communication so you should use external pull-ups.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jun 2017 08:49:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Example-project-LPI2C-MASTER/m-p/685643#M1050</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2017-06-14T08:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: Example project LPI2C_MASTER</title>
      <link>https://community.nxp.com/t5/S32K/Example-project-LPI2C-MASTER/m-p/685644#M1051</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your reply&lt;/P&gt;&lt;P&gt;So there is actually no Slave device, So who is sending ACK and other frames from Slave. Or this is just sending 255 bytes in one shot with one stop at the end without receiving any thing from any slave?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Koorosh Hajiani&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jun 2017 14:06:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Example-project-LPI2C-MASTER/m-p/685644#M1051</guid>
      <dc:creator>hajianik</dc:creator>
      <dc:date>2017-06-14T14:06:30Z</dc:date>
    </item>
    <item>
      <title>Re: Example project LPI2C_MASTER</title>
      <link>https://community.nxp.com/t5/S32K/Example-project-LPI2C-MASTER/m-p/685645#M1052</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Yes, that's correct. The S32K144 device has only one LPI2C instance. So you need two boards, one as a master and one as a slave, or another I2C device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jun 2017 14:23:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Example-project-LPI2C-MASTER/m-p/685645#M1052</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2017-06-14T14:23:45Z</dc:date>
    </item>
    <item>
      <title>Re: Example project LPI2C_MASTER</title>
      <link>https://community.nxp.com/t5/S32K/Example-project-LPI2C-MASTER/m-p/1694422#M25530</link>
      <description>&lt;P&gt;please uplode working example of lpi2c master for s32k144evb bord&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 19:53:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Example-project-LPI2C-MASTER/m-p/1694422#M25530</guid>
      <dc:creator>peter09</dc:creator>
      <dc:date>2023-07-27T19:53:52Z</dc:date>
    </item>
  </channel>
</rss>

