<?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: Interfacing S32K144 with an external EEPROM using I2C in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1695726#M25611</link>
    <description>&lt;P&gt;There is no need to initialize the driver and to set the address in every function, do it just once.&lt;/P&gt;
&lt;P&gt;The driver changes the R/W bit in the address depending on the LPI2C API used:&lt;/P&gt;
&lt;P&gt;LPI2C_DRV_MasterSendDataBlocking()&lt;/P&gt;
&lt;P&gt;LPI2C_DRV_MasterReceiveDataBlocking()&lt;/P&gt;
&lt;P&gt;Don't change the address using the LPI2C_DRV_MasterSetSlaveAddr() function.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is important to measure the bus using an oscilloscope or a logic analyzer to make sure the signals are correct.&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;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 31 Jul 2023 08:54:46 GMT</pubDate>
    <dc:creator>danielmartynek</dc:creator>
    <dc:date>2023-07-31T08:54:46Z</dc:date>
    <item>
      <title>Interfacing S32K144 with an external EEPROM using I2C</title>
      <link>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1695483#M25599</link>
      <description>&lt;P&gt;Interfacing EEPROM&amp;nbsp;BR24T512-3AM with S32K144. I have tried to establish the interface by writing a value to a particular address&amp;nbsp; and then reading it back from the same address.&lt;/P&gt;&lt;P&gt;However I'm getting the status while sending and receiving data over I2C as "STATUS_I2C_RECEIVED_NACK".&lt;/P&gt;&lt;P&gt;PFA the sample code for this task. Kindly review and help sort out the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 03:53:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1695483#M25599</guid>
      <dc:creator>Rambo1310</dc:creator>
      <dc:date>2023-07-31T03:53:47Z</dc:date>
    </item>
    <item>
      <title>Re: Interfacing S32K144 with an external EEPROM using I2C</title>
      <link>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1695617#M25604</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/208187"&gt;@Rambo1310&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Can you menasure the bus with an oscilloscope?&lt;/P&gt;
&lt;P&gt;If there is no ACK, check the address.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;BR, Daniel&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 07:42:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1695617#M25604</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-07-31T07:42:22Z</dc:date>
    </item>
    <item>
      <title>Re: Interfacing S32K144 with an external EEPROM using I2C</title>
      <link>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1695696#M25608</link>
      <description>The 7 bit address is 0x50.&lt;BR /&gt;The read/write bit i.e the 8th bit is 0 for writing and 1 for reading.&lt;BR /&gt;I have implemented the logic in the respective function.&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Jul 2023 08:36:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1695696#M25608</guid>
      <dc:creator>Rambo1310</dc:creator>
      <dc:date>2023-07-31T08:36:54Z</dc:date>
    </item>
    <item>
      <title>Re: Interfacing S32K144 with an external EEPROM using I2C</title>
      <link>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1695701#M25610</link>
      <description>&lt;P&gt;The write and read cycle as per datasheet has been attached for your reference. I don't understand where am going wrong with this. Is the I2C peripheral initialized and APIs used correctly?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 08:41:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1695701#M25610</guid>
      <dc:creator>Rambo1310</dc:creator>
      <dc:date>2023-07-31T08:41:19Z</dc:date>
    </item>
    <item>
      <title>Re: Interfacing S32K144 with an external EEPROM using I2C</title>
      <link>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1695726#M25611</link>
      <description>&lt;P&gt;There is no need to initialize the driver and to set the address in every function, do it just once.&lt;/P&gt;
&lt;P&gt;The driver changes the R/W bit in the address depending on the LPI2C API used:&lt;/P&gt;
&lt;P&gt;LPI2C_DRV_MasterSendDataBlocking()&lt;/P&gt;
&lt;P&gt;LPI2C_DRV_MasterReceiveDataBlocking()&lt;/P&gt;
&lt;P&gt;Don't change the address using the LPI2C_DRV_MasterSetSlaveAddr() function.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is important to measure the bus using an oscilloscope or a logic analyzer to make sure the signals are correct.&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;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 08:54:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1695726#M25611</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-07-31T08:54:46Z</dc:date>
    </item>
    <item>
      <title>Re: Interfacing S32K144 with an external EEPROM using I2C</title>
      <link>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1697608#M25711</link>
      <description>&lt;P&gt;I made these changes but didn't work. Same status is returned.&lt;/P&gt;&lt;P&gt;I even tried changing the component to I2C_pal from LPI2C but still no luck am not able to write and read the desired data.&lt;/P&gt;&lt;P&gt;PFA the modified code.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Aug 2023 12:14:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1697608#M25711</guid>
      <dc:creator>Rambo1310</dc:creator>
      <dc:date>2023-08-02T12:14:42Z</dc:date>
    </item>
    <item>
      <title>Re: Interfacing S32K144 with an external EEPROM using I2C</title>
      <link>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1698450#M25739</link>
      <description>&lt;P&gt;I don't see any obvious issue in the code.&lt;/P&gt;
&lt;P&gt;As I said, it is necessary to scope the bus, and compare it with the expected signal as per the datasheet of the EEPROM.&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;</description>
      <pubDate>Thu, 03 Aug 2023 08:38:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Interfacing-S32K144-with-an-external-EEPROM-using-I2C/m-p/1698450#M25739</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-08-03T08:38:07Z</dc:date>
    </item>
  </channel>
</rss>

