<?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 Support Request: PCA85073A RTC I2C Communication Issue in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Support-Request-PCA85073A-RTC-I2C-Communication-Issue/m-p/2376764#M59026</link>
    <description>&lt;DIV class=""&gt;We are encountering an issue with the external RTC (PCA85073A) during I2C communication. While performing RTC set operations (seconds, minutes, hours) and subsequent RTC read operations, we are not receiving continuous readings for seconds ,minutes and Hours&lt;/DIV&gt;&lt;DIV class=""&gt;Although the RTC cycles through 0 to 59, the readings are inconsistent and certain values appear to be missing. For example, instead of Continuous values, we observe jumps such as 0, 1, ,8,9,10, 11, 18, 19, 40, 41, 50, 51, 58, 59. The same irregularity is observed with minutes as well.&lt;/DIV&gt;&lt;DIV class=""&gt;This behavior is impacting timekeeping accuracy. We kindly request your support in investigating the I2C communication and RTC read sequence to identify the root cause&lt;/DIV&gt;</description>
    <pubDate>Thu, 04 Jun 2026 09:59:17 GMT</pubDate>
    <dc:creator>KRAJASEKHAR</dc:creator>
    <dc:date>2026-06-04T09:59:17Z</dc:date>
    <item>
      <title>Support Request: PCA85073A RTC I2C Communication Issue</title>
      <link>https://community.nxp.com/t5/S32K/Support-Request-PCA85073A-RTC-I2C-Communication-Issue/m-p/2376764#M59026</link>
      <description>&lt;DIV class=""&gt;We are encountering an issue with the external RTC (PCA85073A) during I2C communication. While performing RTC set operations (seconds, minutes, hours) and subsequent RTC read operations, we are not receiving continuous readings for seconds ,minutes and Hours&lt;/DIV&gt;&lt;DIV class=""&gt;Although the RTC cycles through 0 to 59, the readings are inconsistent and certain values appear to be missing. For example, instead of Continuous values, we observe jumps such as 0, 1, ,8,9,10, 11, 18, 19, 40, 41, 50, 51, 58, 59. The same irregularity is observed with minutes as well.&lt;/DIV&gt;&lt;DIV class=""&gt;This behavior is impacting timekeeping accuracy. We kindly request your support in investigating the I2C communication and RTC read sequence to identify the root cause&lt;/DIV&gt;</description>
      <pubDate>Thu, 04 Jun 2026 09:59:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Support-Request-PCA85073A-RTC-I2C-Communication-Issue/m-p/2376764#M59026</guid>
      <dc:creator>KRAJASEKHAR</dc:creator>
      <dc:date>2026-06-04T09:59:17Z</dc:date>
    </item>
    <item>
      <title>Re: Support Request: PCA85073A RTC I2C Communication Issue</title>
      <link>https://community.nxp.com/t5/S32K/Support-Request-PCA85073A-RTC-I2C-Communication-Issue/m-p/2377058#M59040</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;
&lt;P&gt;Please see the &lt;A href="https://www.nxp.com/docs/en/data-sheet/PCA85073A.pdf" target="_self"&gt;datasheet&lt;/A&gt; section 7.4&amp;nbsp;Setting and reading the time.&lt;/P&gt;
&lt;P&gt;During read/write operations, the time counting circuits (memory locations 04h through 0Ah) are blocked.&lt;BR /&gt;The blocking prevents&lt;BR /&gt;• Faulty reading of the clock and calendar during a carry condition&lt;BR /&gt;• Incrementing the time registers during the read cycle&lt;/P&gt;
&lt;P&gt;Because of this method, it is very important to make a read or write access in one go, that is, setting or reading&lt;BR /&gt;seconds through to years should be made in one single access. Failing to comply with this method could result&lt;BR /&gt;in the time becoming corrupted.&lt;BR /&gt;As an example, if the time (seconds through to hours) is set in one access and then in a second access the&lt;BR /&gt;date is set, it is possible that the time will increment between the two accesses. A similar problem exists when&lt;BR /&gt;reading. A roll-over may occur between reads thus giving the minutes from one moment and the hours from the&lt;BR /&gt;next.&lt;BR /&gt;Recommended method for reading the time:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Send a START condition and the target address (see Table 38) for write (A2h)&lt;/LI&gt;
&lt;LI&gt;Set the address pointer to 4 (Seconds) by sending 04h&lt;/LI&gt;
&lt;LI&gt;Send a RESTART condition or STOP followed by START&lt;/LI&gt;
&lt;LI&gt;Send the target address for read (A3h)&lt;/LI&gt;
&lt;LI&gt;Read Seconds&lt;/LI&gt;
&lt;LI&gt;Read Minutes&lt;/LI&gt;
&lt;LI&gt;Read Hours&lt;/LI&gt;
&lt;LI&gt;Read Days&lt;/LI&gt;
&lt;LI&gt;Read Weekdays&lt;/LI&gt;
&lt;LI&gt;Read Months&lt;/LI&gt;
&lt;LI&gt;Read Years&lt;/LI&gt;
&lt;LI&gt;Send a STOP condition&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Please let me know your results!&lt;/P&gt;</description>
      <pubDate>Thu, 04 Jun 2026 19:25:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Support-Request-PCA85073A-RTC-I2C-Communication-Issue/m-p/2377058#M59040</guid>
      <dc:creator>ErikaC</dc:creator>
      <dc:date>2026-06-04T19:25:54Z</dc:date>
    </item>
  </channel>
</rss>

