<?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>CodeWarrior Development ToolsのトピックRe: Processor Expert and VLLSx</title>
    <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Processor-Expert-and-VLLSx/m-p/314660#M917</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So, turns out to fairly simple.&amp;nbsp; The docs are good, but don't take CW into account.&amp;nbsp; __init_hardware() is mostly correct, but it needs to have the ACKISO check added.&amp;nbsp; Turns out this can be done from the CPU Component Inspector:&amp;nbsp; Build Options --&amp;gt; User Initialization --&amp;gt; User code before PE Initialization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now there's the problem of having the same pin put the processor back into VLLS1.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Jul 2014 14:19:42 GMT</pubDate>
    <dc:creator>marknordstrand</dc:creator>
    <dc:date>2014-07-07T14:19:42Z</dc:date>
    <item>
      <title>Processor Expert and VLLSx</title>
      <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Processor-Expert-and-VLLSx/m-p/314659#M916</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm trying to exit out of VLLS1 on a mk20dn512VLQ10.&amp;nbsp; Code was generated with CW 10.4.&amp;nbsp; If the MCG is set up for FEI, the pin for LLWU works as expected.&amp;nbsp; Switching the MCG to PEE and nothing happens.&amp;nbsp; From the ref. manual and the Kinetis Low Power Modes manual, I understand the MCG should already be in FEI, so I can see why this is working with little effort.&amp;nbsp; I did see there is a __init_hardware() in Sources/Cpu.c which looks like it handles the transitions from FEI to PEE.&amp;nbsp; Tried calling that directly and copying and modifying it to no avail (and setting the ACKISO bit afterwards).&amp;nbsp; What besides the code in __init_hardware() should be done to get out of VLLS1?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Jul 2014 19:13:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Processor-Expert-and-VLLSx/m-p/314659#M916</guid>
      <dc:creator>marknordstrand</dc:creator>
      <dc:date>2014-07-01T19:13:38Z</dc:date>
    </item>
    <item>
      <title>Re: Processor Expert and VLLSx</title>
      <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Processor-Expert-and-VLLSx/m-p/314660#M917</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So, turns out to fairly simple.&amp;nbsp; The docs are good, but don't take CW into account.&amp;nbsp; __init_hardware() is mostly correct, but it needs to have the ACKISO check added.&amp;nbsp; Turns out this can be done from the CPU Component Inspector:&amp;nbsp; Build Options --&amp;gt; User Initialization --&amp;gt; User code before PE Initialization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now there's the problem of having the same pin put the processor back into VLLS1.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jul 2014 14:19:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Processor-Expert-and-VLLSx/m-p/314660#M917</guid>
      <dc:creator>marknordstrand</dc:creator>
      <dc:date>2014-07-07T14:19:42Z</dc:date>
    </item>
  </channel>
</rss>

