<?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: When PCF2129 information should be read/write? in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/When-PCF2129-information-should-be-read-write/m-p/967295#M8039</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Fabian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chapters 8.8.8 of the &lt;A href="https://www.nxp.com/docs/en/data-sheet/PCF2129.pdf"&gt;PCF2129 datasheet&lt;/A&gt; and 18 of the &lt;A href="https://www.nxp.com/docs/en/user-guide/UM10301.pdf"&gt;UM10301&lt;/A&gt; provide&amp;nbsp;additional information regarding reading to/writing from the time and date registers. Our recommendation is to read all time registers in one single read operation, using the auto-increment function.&amp;nbsp;Is this what you are doing in your code?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Tomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Sep 2019 11:31:56 GMT</pubDate>
    <dc:creator>TomasVaverka</dc:creator>
    <dc:date>2019-09-25T11:31:56Z</dc:date>
    <item>
      <title>When PCF2129 information should be read/write?</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/When-PCF2129-information-should-be-read-write/m-p/967294#M8038</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have managed to send and receive information from the PCF2129 via SPI with a microcontroller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Both writing and reading is done from address 0x03 (seconds) to address 0x09 (years).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I have discovered that sometimes you write or receive erroneous data. For example, once the RTCC has been correctly matched, both time and date, such information obtains inconsistent data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;I read section 8.8.8 of the datasheets and it indicates that regions from address 0x03 to 0x09 are blocked for security.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Could that be the cause that sometimes I get incongruous data?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the answer is yes, my question is: How can I know what is the right time to read the information from these regions of the RAM?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any comments or suggestions are welcome.&lt;BR /&gt;&lt;BR /&gt;Fabián&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Sep 2019 20:06:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/When-PCF2129-information-should-be-read-write/m-p/967294#M8038</guid>
      <dc:creator>dominusdrr</dc:creator>
      <dc:date>2019-09-24T20:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: When PCF2129 information should be read/write?</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/When-PCF2129-information-should-be-read-write/m-p/967295#M8039</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Fabian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chapters 8.8.8 of the &lt;A href="https://www.nxp.com/docs/en/data-sheet/PCF2129.pdf"&gt;PCF2129 datasheet&lt;/A&gt; and 18 of the &lt;A href="https://www.nxp.com/docs/en/user-guide/UM10301.pdf"&gt;UM10301&lt;/A&gt; provide&amp;nbsp;additional information regarding reading to/writing from the time and date registers. Our recommendation is to read all time registers in one single read operation, using the auto-increment function.&amp;nbsp;Is this what you are doing in your code?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Tomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Sep 2019 11:31:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/When-PCF2129-information-should-be-read-write/m-p/967295#M8039</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2019-09-25T11:31:56Z</dc:date>
    </item>
    <item>
      <title>Re: When PCF2129 information should be read/write?</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/When-PCF2129-information-should-be-read-write/m-p/967296#M8040</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's exactly what I'm doing, I point to address 0x03 and by auto increment I read all the other bytes up to address 0x09&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Sep 2019 13:02:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/When-PCF2129-information-should-be-read-write/m-p/967296#M8040</guid>
      <dc:creator>dominusdrr</dc:creator>
      <dc:date>2019-09-25T13:02:39Z</dc:date>
    </item>
    <item>
      <title>Re: When PCF2129 information should be read/write?</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/When-PCF2129-information-should-be-read-write/m-p/967297#M8041</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had to solder wires to the SPI lines and the CE to connect a logic analyzer and determine what was happening.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;It was a silly mistake, I was forgetting to put the CE terminal in logical 1 when the reading of all bytes was finished.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2019 02:00:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/When-PCF2129-information-should-be-read-write/m-p/967297#M8041</guid>
      <dc:creator>dominusdrr</dc:creator>
      <dc:date>2019-09-26T02:00:57Z</dc:date>
    </item>
    <item>
      <title>Re: When PCF2129 information should be read/write?</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/When-PCF2129-information-should-be-read-write/m-p/967298#M8042</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Fabian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OK, good to know what was behind this issue, I also always use a logic analyzer to make sure the format and timing of the SPI traffic meet datasheet recommendations.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Tomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2019 07:07:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/When-PCF2129-information-should-be-read-write/m-p/967298#M8042</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2019-09-26T07:07:07Z</dc:date>
    </item>
  </channel>
</rss>

