<?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 KL03 rtc clock instable in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL03-rtc-clock-instable/m-p/548138#M33403</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have developed a project with a MKL03Z32VFG4 with a 32768Hz crystal and powered by a 2045 coin battery.&lt;/P&gt;&lt;P&gt;The application uses only the RTC seconds counter and in normal run mode the clock remains always precise and correct. The mcu enters in VLSS0 easily and current is under 1uA; but when it exits from low power state the clock counter is incorrect and the seconds count can be a lesser or higher, without any apparent reason.&lt;/P&gt;&lt;P&gt;All the prototypes ( &amp;gt;10) we have tested present this problem. Do someone have an idea of where to look, hw? fw?&lt;/P&gt;&lt;P&gt;Thanks for any suggestion...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Aug 2016 15:09:07 GMT</pubDate>
    <dc:creator>Lupo</dc:creator>
    <dc:date>2016-08-22T15:09:07Z</dc:date>
    <item>
      <title>KL03 rtc clock instable</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL03-rtc-clock-instable/m-p/548138#M33403</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have developed a project with a MKL03Z32VFG4 with a 32768Hz crystal and powered by a 2045 coin battery.&lt;/P&gt;&lt;P&gt;The application uses only the RTC seconds counter and in normal run mode the clock remains always precise and correct. The mcu enters in VLSS0 easily and current is under 1uA; but when it exits from low power state the clock counter is incorrect and the seconds count can be a lesser or higher, without any apparent reason.&lt;/P&gt;&lt;P&gt;All the prototypes ( &amp;gt;10) we have tested present this problem. Do someone have an idea of where to look, hw? fw?&lt;/P&gt;&lt;P&gt;Thanks for any suggestion...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Aug 2016 15:09:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL03-rtc-clock-instable/m-p/548138#M33403</guid>
      <dc:creator>Lupo</dc:creator>
      <dc:date>2016-08-22T15:09:07Z</dc:date>
    </item>
    <item>
      <title>Re: KL03 rtc clock instable</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL03-rtc-clock-instable/m-p/548139#M33404</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Michael,&lt;/P&gt;&lt;P&gt;I would recommend customer to check whether I/O pads (XTAL/EXTAL) are not in latched state as dedicated after recovery from VLLS mode. Check ACKISO definition in PMC module chapter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;R.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Aug 2016 15:33:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL03-rtc-clock-instable/m-p/548139#M33404</guid>
      <dc:creator>rastislav_pavlanin</dc:creator>
      <dc:date>2016-08-22T15:33:31Z</dc:date>
    </item>
    <item>
      <title>Re: KL03 rtc clock instable</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL03-rtc-clock-instable/m-p/548140#M33405</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am using KDS v3.2.0 and KSDK 1.3.0 with some PE components and in Events.c I have:&lt;/P&gt;&lt;P&gt; void LLWU_IRQHandler(void)&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;&amp;nbsp; POWER_SYS_ClearAckIsolation();&lt;/P&gt;&lt;P&gt;&amp;nbsp; POWER_SYS_ClearWakeupPinFlag(kPowerManagerWakeupPin4);&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;Is this not enough?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Aug 2016 16:42:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL03-rtc-clock-instable/m-p/548140#M33405</guid>
      <dc:creator>Lupo</dc:creator>
      <dc:date>2016-08-22T16:42:43Z</dc:date>
    </item>
    <item>
      <title>Re: KL03 rtc clock instable</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL03-rtc-clock-instable/m-p/548141#M33406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;well, it could depend on in what time the function is executed.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_0.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/3464iD880E7D942C31208/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_0.png" alt="pastedImage_0.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;NOTE: &lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;For LLWU Flag X registers: &lt;/P&gt;&lt;UL&gt;&lt;LI&gt;For LLS, this is the source causing the CPU interrupt flow. So, interrupt handler execution is expected.&lt;/LI&gt;&lt;LI&gt;For VLLS, this is the source causing the MCU reset flow&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I would expect that for VLLS0 mode you detect whether the reset was caused by LLWU wake up trought the system reset status registers. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;R.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Aug 2016 07:02:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KL03-rtc-clock-instable/m-p/548141#M33406</guid>
      <dc:creator>rastislav_pavlanin</dc:creator>
      <dc:date>2016-08-23T07:02:19Z</dc:date>
    </item>
  </channel>
</rss>

