<?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: PCA21125 RTC Writing the Registers in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/PCA21125-RTC-Writing-the-Registers/m-p/1743611#M19754</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;SPAN&gt;Ashwini,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I always recommend to check at first the SPI format and timing&amp;nbsp;as in most cases it is the root cause of such issues.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The PCA21225 uses&amp;nbsp;&lt;FONT face="Arial, sans-serif"&gt;mode 0 (CPOL = CPHA = 0), meaning the&amp;nbsp;&lt;/FONT&gt;SPI clock idles at a low level and samples on the rising edge.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;As for the timing, make sure the dynamic characteristics shown in Table 43 of the datasheet are met.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hope it helps.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;BR, Tomas&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 20 Oct 2023 10:02:25 GMT</pubDate>
    <dc:creator>TomasVaverka</dc:creator>
    <dc:date>2023-10-20T10:02:25Z</dc:date>
    <item>
      <title>PCA21125 RTC Writing the Registers</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PCA21125-RTC-Writing-the-Registers/m-p/1743479#M19748</link>
      <description>&lt;P&gt;Hello NXP,&lt;BR /&gt;When I attempt to read the written registers using SPI Command 0x90, the default value of the registers remains unchangeable. I have attempted to write the registers of the PCA21125 RTC clock using SPI Command 0x10.&lt;/P&gt;&lt;P&gt;Eg.&amp;nbsp;&lt;BR /&gt;1. Writing register Minute_Alarm with value 0x11&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;i. Expected read value of Minute_Alarm Reg : 0x11 : 0001 0001&lt;/P&gt;&lt;P&gt;2. Reading Minute_Alarm after write command :&lt;BR /&gt;&amp;nbsp; i.&amp;nbsp; observed read value of Minute_Alarm : 0x91 : 1001 0001&lt;/P&gt;</description>
      <pubDate>Fri, 20 Oct 2023 07:14:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PCA21125-RTC-Writing-the-Registers/m-p/1743479#M19748</guid>
      <dc:creator>AshBirari</dc:creator>
      <dc:date>2023-10-20T07:14:17Z</dc:date>
    </item>
    <item>
      <title>Re: PCA21125 RTC Writing the Registers</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PCA21125-RTC-Writing-the-Registers/m-p/1743611#M19754</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;SPAN&gt;Ashwini,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I always recommend to check at first the SPI format and timing&amp;nbsp;as in most cases it is the root cause of such issues.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The PCA21225 uses&amp;nbsp;&lt;FONT face="Arial, sans-serif"&gt;mode 0 (CPOL = CPHA = 0), meaning the&amp;nbsp;&lt;/FONT&gt;SPI clock idles at a low level and samples on the rising edge.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;As for the timing, make sure the dynamic characteristics shown in Table 43 of the datasheet are met.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hope it helps.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;BR, Tomas&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Oct 2023 10:02:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PCA21125-RTC-Writing-the-Registers/m-p/1743611#M19754</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2023-10-20T10:02:25Z</dc:date>
    </item>
    <item>
      <title>Re: PCA21125 RTC Writing the Registers</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PCA21125-RTC-Writing-the-Registers/m-p/1746621#M19804</link>
      <description>&lt;P&gt;PCA21125 is having 3 wire SPI protocol, as per my knowledge here spi modes are not configurable. can you elaborate on timing issue with an example.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2023 05:41:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PCA21125-RTC-Writing-the-Registers/m-p/1746621#M19804</guid>
      <dc:creator>AshBirari</dc:creator>
      <dc:date>2023-10-26T05:41:07Z</dc:date>
    </item>
  </channel>
</rss>

