<?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: clarify VLLS[2,3] wakeup through reset on cortex m0+ in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/clarify-VLLS-2-3-wakeup-through-reset-on-cortex-m0/m-p/1523726#M64058</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;As for design goes, when a RESET is issued, the Program Counter (or PC) goes to a reset state, which normally is 0x0 (or the origin). This is by design and, to my knowledge, this is core related and you cannot modify this reset value.&lt;/P&gt;
&lt;P&gt;What you could do is send from 0x0 to whatever address or table you need. If you are working with a system with built-in bootloader, just verify the flow of the program, some interrupts cannot be modified by user as they are defined by design and are platform related.&lt;/P&gt;
&lt;P&gt;Let us know if this helps you or not.&lt;/P&gt;</description>
    <pubDate>Fri, 16 Sep 2022 16:54:25 GMT</pubDate>
    <dc:creator>Daniel-Aguirre</dc:creator>
    <dc:date>2022-09-16T16:54:25Z</dc:date>
    <item>
      <title>clarify VLLS[2,3] wakeup through reset on cortex m0+</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/clarify-VLLS-2-3-wakeup-through-reset-on-cortex-m0/m-p/1520268#M63996</link>
      <description>&lt;P&gt;when i wakeup from VLLS[2,3] mode, documentation says i wakeup through "reset"; by contract LLSx the wakeup is through the "WFI" instruction....&lt;/P&gt;&lt;P&gt;in my cortex m0+ application, i've actually MOVED SCB-&amp;gt;VTOR to an address other than 0x00000000 (for reasons beyond the scope of this question)....&lt;/P&gt;&lt;P&gt;it appears that (despite moving the VTOR) the "reset" wakeup goes back through the original vector at address 0x00000000....&amp;nbsp; is that by design????&amp;nbsp; or is there someway to have the wakeup "reset" go through the vectors currently referenced by the VTOR register????&lt;/P&gt;</description>
      <pubDate>Sun, 11 Sep 2022 22:40:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/clarify-VLLS-2-3-wakeup-through-reset-on-cortex-m0/m-p/1520268#M63996</guid>
      <dc:creator>biosbob</dc:creator>
      <dc:date>2022-09-11T22:40:49Z</dc:date>
    </item>
    <item>
      <title>Re: clarify VLLS[2,3] wakeup through reset on cortex m0+</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/clarify-VLLS-2-3-wakeup-through-reset-on-cortex-m0/m-p/1523726#M64058</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;As for design goes, when a RESET is issued, the Program Counter (or PC) goes to a reset state, which normally is 0x0 (or the origin). This is by design and, to my knowledge, this is core related and you cannot modify this reset value.&lt;/P&gt;
&lt;P&gt;What you could do is send from 0x0 to whatever address or table you need. If you are working with a system with built-in bootloader, just verify the flow of the program, some interrupts cannot be modified by user as they are defined by design and are platform related.&lt;/P&gt;
&lt;P&gt;Let us know if this helps you or not.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 16:54:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/clarify-VLLS-2-3-wakeup-through-reset-on-cortex-m0/m-p/1523726#M64058</guid>
      <dc:creator>Daniel-Aguirre</dc:creator>
      <dc:date>2022-09-16T16:54:25Z</dc:date>
    </item>
    <item>
      <title>Re: clarify VLLS[2,3] wakeup through reset on cortex m0+</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/clarify-VLLS-2-3-wakeup-through-reset-on-cortex-m0/m-p/1523730#M64059</link>
      <description>&lt;P&gt;in my case, i do have my own bootloader at 0x0....&amp;nbsp; but care has to be taken when writing your own bootloader to handle a "wakeup reset" and not (for example) initialize memory!!!!&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 17:04:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/clarify-VLLS-2-3-wakeup-through-reset-on-cortex-m0/m-p/1523730#M64059</guid>
      <dc:creator>biosbob</dc:creator>
      <dc:date>2022-09-16T17:04:26Z</dc:date>
    </item>
  </channel>
</rss>

