<?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: RTC/API in MPC5606B stops incrementing RTCCNT  in MPC5xxx</title>
    <link>https://community.nxp.com/t5/MPC5xxx/RTC-API-in-MPC5606B-stops-incrementing-RTCCNT/m-p/903346#M13415</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pavel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found out that this has been already reported some time ago. Design team confirmed this behavior - if RTCVAL is zero, interrupts are not triggered. I can see that there was a request to add this information to the reference manual but it has not been processed yet.&lt;/P&gt;&lt;P&gt;So, please avoid writing zero to the registers as a workaround.&lt;/P&gt;&lt;P&gt;Sorry for inconvenience.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lukas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 10 May 2019 08:19:38 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2019-05-10T08:19:38Z</dc:date>
    <item>
      <title>RTC/API in MPC5606B stops incrementing RTCCNT</title>
      <link>https://community.nxp.com/t5/MPC5xxx/RTC-API-in-MPC5606B-stops-incrementing-RTCCNT/m-p/903343#M13412</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I ran into problem with FIRC clocking RTC/API module. I use the module for periodic wakup during sleep (stop mode -10) Usually it works fine but from time to time, interrupts stop comming and and I discovered, that the RTCCNT timer is not being incremented.&lt;/P&gt;&lt;P&gt;The question is a little vague but is it possible at all, that FIRC can stop under any circumstances?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for any reply&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pavel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 May 2019 16:01:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/RTC-API-in-MPC5606B-stops-incrementing-RTCCNT/m-p/903343#M13412</guid>
      <dc:creator>snafu</dc:creator>
      <dc:date>2019-05-07T16:01:19Z</dc:date>
    </item>
    <item>
      <title>Re: RTC/API in MPC5606B stops incrementing RTCCNT</title>
      <link>https://community.nxp.com/t5/MPC5xxx/RTC-API-in-MPC5606B-stops-incrementing-RTCCNT/m-p/903344#M13413</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pavel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FIRC definitely shouldn't stop if not requested. Have you tried to build just very simple application which use RTC/API for periodical wake up? It sounds rather like some kind of SW issue. Do you have more boards? Can you see the same behavior on all of them?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lukas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 May 2019 07:58:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/RTC-API-in-MPC5606B-stops-incrementing-RTCCNT/m-p/903344#M13413</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2019-05-09T07:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: RTC/API in MPC5606B stops incrementing RTCCNT</title>
      <link>https://community.nxp.com/t5/MPC5xxx/RTC-API-in-MPC5606B-stops-incrementing-RTCCNT/m-p/903345#M13414</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lukas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the reply.&lt;/P&gt;&lt;P&gt;The situation happens on more boards so it doesn't seem to problem of the board.&lt;/P&gt;&lt;P&gt;Most of the time wakeup works but I found out one weird thing. When I put zero into RTCVAL in RTCC register, interrupts stop comming (but RTCCNT keeps on incrementing) and when I put other value into RTCVAL interrups work fine.&lt;/P&gt;&lt;P&gt;I looked at other flags in RTCC when 0 is in RTCVAL but all are correctly set (CNTEN, RTCIE are set, CLKSEL is ok).&lt;/P&gt;&lt;P&gt;Is value 0 in RTCVAL somehow special? I didn't find anything about it in reference manual.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Pavel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 May 2019 10:56:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/RTC-API-in-MPC5606B-stops-incrementing-RTCCNT/m-p/903345#M13414</guid>
      <dc:creator>snafu</dc:creator>
      <dc:date>2019-05-09T10:56:12Z</dc:date>
    </item>
    <item>
      <title>Re: RTC/API in MPC5606B stops incrementing RTCCNT</title>
      <link>https://community.nxp.com/t5/MPC5xxx/RTC-API-in-MPC5606B-stops-incrementing-RTCCNT/m-p/903346#M13415</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pavel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found out that this has been already reported some time ago. Design team confirmed this behavior - if RTCVAL is zero, interrupts are not triggered. I can see that there was a request to add this information to the reference manual but it has not been processed yet.&lt;/P&gt;&lt;P&gt;So, please avoid writing zero to the registers as a workaround.&lt;/P&gt;&lt;P&gt;Sorry for inconvenience.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lukas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 May 2019 08:19:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/RTC-API-in-MPC5606B-stops-incrementing-RTCCNT/m-p/903346#M13415</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2019-05-10T08:19:38Z</dc:date>
    </item>
    <item>
      <title>Re: RTC/API in MPC5606B stops incrementing RTCCNT</title>
      <link>https://community.nxp.com/t5/MPC5xxx/RTC-API-in-MPC5606B-stops-incrementing-RTCCNT/m-p/903347#M13416</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lukas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thank you for the confirmation of the bug. Workaround is not a problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pavel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 May 2019 21:18:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/RTC-API-in-MPC5606B-stops-incrementing-RTCCNT/m-p/903347#M13416</guid>
      <dc:creator>snafu</dc:creator>
      <dc:date>2019-05-11T21:18:35Z</dc:date>
    </item>
  </channel>
</rss>

