<?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>Processor Expert SoftwareのトピックRe: RTC programed to the wrong time by PE_LDD</title>
    <link>https://community.nxp.com/t5/Processor-Expert-Software/RTC-programed-to-the-wrong-time-by-PE-LDD/m-p/328752#M2500</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rande&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know the PE generated code but I expect that you can simply add a check of the validity of the timer and abort any initialistion (which should only be done when it is has not yet been configured)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;if ((RTC_SR &amp;amp; RTC_SR_TIF) != 0) {&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; return; // RTC is alread operating so ignore&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;}&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note however that you will still need to ensure that the clock gate is enabled to the RTC after each reset (and to be able to check its validity) so the code will in fact look more like (similar to the uTasker time management solution):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;POWER_UP(6, SIM_SCGC6_RTC);&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;if ((RTC_SR &amp;amp; RTC_SR_TIF) != 0) {&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; return; // RTC is alread operating so ignore&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;}&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;// Continue with the configuration..&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kinetis: &lt;A href="http://www.utasker.com/kinetis.html" title="http://www.utasker.com/kinetis.html"&gt;µTasker Kinetis support&lt;/A&gt;&lt;/P&gt;&lt;P&gt;K22: &lt;A href="http://www.utasker.com/kinetis/FRDM-K22F.html" title="http://www.utasker.com/kinetis/FRDM-K22F.html"&gt;µTasker Kinetis FRDM-K22F support&lt;/A&gt; / &lt;A href="http://www.utasker.com/kinetis/TWR-K22F120M.html" title="http://www.utasker.com/kinetis/TWR-K22F120M.html"&gt;µTasker Kinetis TWR-K22F120M support&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Time Management: &lt;A href="http://www.utasker.com/docs/uTasker/uTasker_Time.pdf" title="http://www.utasker.com/docs/uTasker/uTasker_Time.pdf"&gt;http://www.utasker.com/docs/uTasker/uTasker_Time.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;For the complete "out-of-the-box" Kinetis experience and faster time to market&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 Mar 2015 23:53:29 GMT</pubDate>
    <dc:creator>mjbcswitzerland</dc:creator>
    <dc:date>2015-03-18T23:53:29Z</dc:date>
    <item>
      <title>RTC programed to the wrong time by PE_LDD</title>
      <link>https://community.nxp.com/t5/Processor-Expert-Software/RTC-programed-to-the-wrong-time-by-PE-LDD/m-p/328751#M2499</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How can we stop PE_LDD from overwriting the time in the RTC registers with the values in the PE properties panel on Power up?&lt;/P&gt;&lt;P&gt;Using MK22FX512VLH12 with KDS.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2015 21:23:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Processor-Expert-Software/RTC-programed-to-the-wrong-time-by-PE-LDD/m-p/328751#M2499</guid>
      <dc:creator>randenewberry</dc:creator>
      <dc:date>2015-03-18T21:23:13Z</dc:date>
    </item>
    <item>
      <title>Re: RTC programed to the wrong time by PE_LDD</title>
      <link>https://community.nxp.com/t5/Processor-Expert-Software/RTC-programed-to-the-wrong-time-by-PE-LDD/m-p/328752#M2500</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rande&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know the PE generated code but I expect that you can simply add a check of the validity of the timer and abort any initialistion (which should only be done when it is has not yet been configured)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;if ((RTC_SR &amp;amp; RTC_SR_TIF) != 0) {&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; return; // RTC is alread operating so ignore&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;}&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note however that you will still need to ensure that the clock gate is enabled to the RTC after each reset (and to be able to check its validity) so the code will in fact look more like (similar to the uTasker time management solution):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;POWER_UP(6, SIM_SCGC6_RTC);&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;if ((RTC_SR &amp;amp; RTC_SR_TIF) != 0) {&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; return; // RTC is alread operating so ignore&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;}&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;// Continue with the configuration..&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kinetis: &lt;A href="http://www.utasker.com/kinetis.html" title="http://www.utasker.com/kinetis.html"&gt;µTasker Kinetis support&lt;/A&gt;&lt;/P&gt;&lt;P&gt;K22: &lt;A href="http://www.utasker.com/kinetis/FRDM-K22F.html" title="http://www.utasker.com/kinetis/FRDM-K22F.html"&gt;µTasker Kinetis FRDM-K22F support&lt;/A&gt; / &lt;A href="http://www.utasker.com/kinetis/TWR-K22F120M.html" title="http://www.utasker.com/kinetis/TWR-K22F120M.html"&gt;µTasker Kinetis TWR-K22F120M support&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Time Management: &lt;A href="http://www.utasker.com/docs/uTasker/uTasker_Time.pdf" title="http://www.utasker.com/docs/uTasker/uTasker_Time.pdf"&gt;http://www.utasker.com/docs/uTasker/uTasker_Time.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;For the complete "out-of-the-box" Kinetis experience and faster time to market&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2015 23:53:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Processor-Expert-Software/RTC-programed-to-the-wrong-time-by-PE-LDD/m-p/328752#M2500</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2015-03-18T23:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: RTC programed to the wrong time by PE_LDD</title>
      <link>https://community.nxp.com/t5/Processor-Expert-Software/RTC-programed-to-the-wrong-time-by-PE-LDD/m-p/328753#M2501</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Mark for the reply. The problem is with PE, and we found a way &lt;/P&gt;&lt;P&gt;to make it work.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rande Newberry&lt;/P&gt;&lt;P&gt;H-ITT, LLC, a Hyper-Interactive Teaching Technology Company&lt;/P&gt;&lt;P&gt;420 Shearer Blvd.-Cocoa, FL, 32922&lt;/P&gt;&lt;P&gt;PH: 888-322-0089&lt;/P&gt;&lt;P&gt;rande@h-itt.com&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Mar 2015 12:56:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Processor-Expert-Software/RTC-programed-to-the-wrong-time-by-PE-LDD/m-p/328753#M2501</guid>
      <dc:creator>randenewberry</dc:creator>
      <dc:date>2015-03-24T12:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: RTC programed to the wrong time by PE_LDD</title>
      <link>https://community.nxp.com/t5/Processor-Expert-Software/RTC-programed-to-the-wrong-time-by-PE-LDD/m-p/328754#M2502</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 have provided answer on the same previous question, see &lt;A href="https://community.nxp.com/message/498406"&gt;Re: rtc resets at powerup&lt;/A&gt;. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Marek Neuzil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Mar 2015 12:42:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Processor-Expert-Software/RTC-programed-to-the-wrong-time-by-PE-LDD/m-p/328754#M2502</guid>
      <dc:creator>marek_neuzil</dc:creator>
      <dc:date>2015-03-26T12:42:08Z</dc:date>
    </item>
  </channel>
</rss>

