<?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: COP trigger S12XEP100 reset, can RAM keep the data in S12 / MagniV Microcontrollers</title>
    <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951418#M16653</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ray,&lt;BR /&gt;Yes, RAM is not affected by COP reset.&lt;/P&gt;&lt;P&gt;However, _Startup() code initialize/erase RAM by default prior main() function execution.&lt;/P&gt;&lt;P&gt;If you would like to skip this RAM initialization for specific part of RAM, please update your prm linker file and use NO_INIT qualifier. For example:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SEGMENTS&lt;/P&gt;&lt;P&gt;…&lt;/P&gt;&lt;P&gt;/* non-paged RAM */&lt;/P&gt;&lt;P&gt;//&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RAM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = READ_WRITE&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x2000 TO&amp;nbsp;&amp;nbsp; 0x3FFF;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RAM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = READ_WRITE&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x2000 TO&amp;nbsp;&amp;nbsp; 0x3EFF;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RAM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = READ_WRITE&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x3F00 TO&amp;nbsp;&amp;nbsp; 0x3FFF NO_INIT;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;/*not affected by _Startup() code*/&lt;/P&gt;&lt;P&gt;…&lt;/P&gt;&lt;P&gt;END&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more details about linker file, please check&amp;nbsp;Build_Tools_Utilities.pdf document in CW Help folder.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I hope it helps you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Aug 2019 14:19:23 GMT</pubDate>
    <dc:creator>RadekS</dc:creator>
    <dc:date>2019-08-08T14:19:23Z</dc:date>
    <item>
      <title>COP trigger S12XEP100 reset, can RAM keep the data</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951416#M16651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dears,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If COP trigger S12XEP100 reset, can RAM keep the data stable?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BRs,&lt;/P&gt;&lt;P&gt;Ray&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Aug 2019 13:33:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951416#M16651</guid>
      <dc:creator>dannydeng</dc:creator>
      <dc:date>2019-08-05T13:33:37Z</dc:date>
    </item>
    <item>
      <title>Re: COP trigger S12XEP100 reset, can RAM keep the data</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951417#M16652</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;RAM content is not influenced by COP reset.&lt;/P&gt;&lt;P&gt;What you have to keep in mind is where you will continue leaving the COP service routine and what you are doing in this routine. &lt;/P&gt;&lt;P&gt;Some more in the main.c of the attached project. (Created in a past in the CodeWarrior v.4.7)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best regards,&lt;/P&gt;&lt;P&gt;Ladislav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Aug 2019 10:41:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951417#M16652</guid>
      <dc:creator>lama</dc:creator>
      <dc:date>2019-08-08T10:41:46Z</dc:date>
    </item>
    <item>
      <title>Re: COP trigger S12XEP100 reset, can RAM keep the data</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951418#M16653</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ray,&lt;BR /&gt;Yes, RAM is not affected by COP reset.&lt;/P&gt;&lt;P&gt;However, _Startup() code initialize/erase RAM by default prior main() function execution.&lt;/P&gt;&lt;P&gt;If you would like to skip this RAM initialization for specific part of RAM, please update your prm linker file and use NO_INIT qualifier. For example:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SEGMENTS&lt;/P&gt;&lt;P&gt;…&lt;/P&gt;&lt;P&gt;/* non-paged RAM */&lt;/P&gt;&lt;P&gt;//&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RAM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = READ_WRITE&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x2000 TO&amp;nbsp;&amp;nbsp; 0x3FFF;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RAM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = READ_WRITE&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x2000 TO&amp;nbsp;&amp;nbsp; 0x3EFF;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RAM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = READ_WRITE&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x3F00 TO&amp;nbsp;&amp;nbsp; 0x3FFF NO_INIT;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;/*not affected by _Startup() code*/&lt;/P&gt;&lt;P&gt;…&lt;/P&gt;&lt;P&gt;END&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more details about linker file, please check&amp;nbsp;Build_Tools_Utilities.pdf document in CW Help folder.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I hope it helps you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Aug 2019 14:19:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951418#M16653</guid>
      <dc:creator>RadekS</dc:creator>
      <dc:date>2019-08-08T14:19:23Z</dc:date>
    </item>
    <item>
      <title>Re: COP trigger S12XEP100 reset, can RAM keep the data</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951419#M16654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes Radek is right.&lt;/P&gt;&lt;P&gt;It the same what I wrote: "What you have to keep in mind is where you will continue leaving the COP service routine and what you are doing in this routine. "&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You do not have to continue with _Startup function after COP reset. You can perform any initialization you want and continue where you want. If you are experienced user and you know how to init the MCU you do not need _Startup function generated by CW automatically.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regrads,&lt;/P&gt;&lt;P&gt;Ladislav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Aug 2019 06:23:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951419#M16654</guid>
      <dc:creator>lama</dc:creator>
      <dc:date>2019-08-09T06:23:28Z</dc:date>
    </item>
    <item>
      <title>Re: COP trigger S12XEP100 reset, can RAM keep the data</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951420#M16655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Lama,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have any source code sample for this idea, we do not promote S12XEP100 for long time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BRs,&lt;/P&gt;&lt;P&gt;Ray&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Aug 2019 14:20:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951420#M16655</guid>
      <dc:creator>dannydeng</dc:creator>
      <dc:date>2019-08-12T14:20:39Z</dc:date>
    </item>
    <item>
      <title>Re: COP trigger S12XEP100 reset, can RAM keep the data</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951421#M16656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-bottom: .0001pt;"&gt;If you mean not to use _Startup routine then….&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;In the originally attached example you have function interrupt 2 void WatchDogIsr(void)&lt;/P&gt;&lt;P&gt;I’ll simplify it a little bit.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;//********************************************************************&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;#pragma CODE_SEG NON_BANKED&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;interrupt 2 void WatchDogIsr(void)&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;{&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;// any local variable created in this function which is not static &amp;nbsp;&amp;nbsp;// causes error because stack is not initialized after reset. Use&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;// global variables which exists everytime on defined addresses.&amp;nbsp;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;// Be aware that all registers are set to the RESET status.&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;// The RAM remains unchanged.&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&amp;nbsp;&amp;nbsp; INIT_SP_FROM_STARTUP_DESC();&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&amp;nbsp;&amp;nbsp; asm JMP FunctionForMyNewStart;&amp;nbsp; // the best is to use near function&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;}&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;#pragma CODE_SEG DEFAULT&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;//********************************************************************&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;#pragma CODE_SEG NON_BANKED&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;void FunctionForMyNewStart(void)&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;{&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&amp;nbsp; // I have rest status of registers and Stack set to initial value&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&amp;nbsp; // Everything is up to me now&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&amp;nbsp; // jump/call/do what you want&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;}&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;#pragma CODE_SEG DEFAULT&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;//********************************************************************&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;Best regards,&lt;/P&gt;&lt;P style="margin-bottom: .0001pt;"&gt;Ladislav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Aug 2019 07:56:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/COP-trigger-S12XEP100-reset-can-RAM-keep-the-data/m-p/951421#M16656</guid>
      <dc:creator>lama</dc:creator>
      <dc:date>2019-08-13T07:56:15Z</dc:date>
    </item>
  </channel>
</rss>

