<?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: KBOOT launching application problems (MK22) in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBOOT-launching-application-problems-MK22/m-p/510051#M32181</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Terry&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have many uTasker serial loader users (including KBOOT mode) who have difficulties with working with MQX (in particular) or KSDS projects (less).&lt;/P&gt;&lt;P&gt;The main issue is that the clock configuration in these environments (sometimes (?) - since it is not alway a problem) assumes that the clock module is in its reset configuration state and fails (hangs) when this is not the case - it is however generally consistent and not random in nature.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The simpest workaround is to ensure that the boot loader clock settings are the same as the application will finally be using and jump past the application clock configration since it is then redundant.&lt;/P&gt;&lt;P&gt;Or a check of the setting can be made (eg. a status check of the clock source/switch settings) and either the clock configuration is executed (when it is seen that it is in the reset state) or else jumped when not.&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;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 Jan 2016 19:16:22 GMT</pubDate>
    <dc:creator>mjbcswitzerland</dc:creator>
    <dc:date>2016-01-22T19:16:22Z</dc:date>
    <item>
      <title>KBOOT launching application problems (MK22)</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBOOT-launching-application-problems-MK22/m-p/510050#M32180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have been struggling getting my application to boot after programming from KBOOT sometimes. I am using KDS3.0 and KSDK1.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My application will sometimes hang at in the startup_MK22F51212.c file at the second&amp;nbsp; while loop:&lt;/P&gt;&lt;PRE __default_attr="c++" __jive_macro_name="code" class="_jivemacro_uid_14534846240204546 jive_macro_code jive_text_macro" data-renderedposition="67.99715423583984_7.997159004211426_1232_155" jivemacro_uid="_14534846240204546"&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; /* Check that the source of the FLL reference clock is the requested one. */&lt;/P&gt;&lt;P&gt;&amp;nbsp; if (((SYSTEM_MCG_C1_VALUE) &amp;amp; MCG_C1_IREFS_MASK) != 0x00U) {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; while((MCG-&amp;gt;S &amp;amp; MCG_S_IREFST_MASK) == 0x00U) {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp; } else {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; while((MCG-&amp;gt;S &amp;amp; MCG_S_IREFST_MASK) != 0x00U) {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would imagine it is caused by the different clocking schemes used by the bootloader and my application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone else encountered this problem? Is there any more documentation which explain the clock settings in the Bootloader Configuration Area (BCA)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my application I use the internal IRC 48MHz clock, PEE, with the PLL output set to 96MHz. The FLL module is disabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Terry Cooke&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jan 2016 17:51:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBOOT-launching-application-problems-MK22/m-p/510050#M32180</guid>
      <dc:creator>thcooke77</dc:creator>
      <dc:date>2016-01-22T17:51:49Z</dc:date>
    </item>
    <item>
      <title>Re: KBOOT launching application problems (MK22)</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBOOT-launching-application-problems-MK22/m-p/510051#M32181</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Terry&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have many uTasker serial loader users (including KBOOT mode) who have difficulties with working with MQX (in particular) or KSDS projects (less).&lt;/P&gt;&lt;P&gt;The main issue is that the clock configuration in these environments (sometimes (?) - since it is not alway a problem) assumes that the clock module is in its reset configuration state and fails (hangs) when this is not the case - it is however generally consistent and not random in nature.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The simpest workaround is to ensure that the boot loader clock settings are the same as the application will finally be using and jump past the application clock configration since it is then redundant.&lt;/P&gt;&lt;P&gt;Or a check of the setting can be made (eg. a status check of the clock source/switch settings) and either the clock configuration is executed (when it is seen that it is in the reset state) or else jumped when not.&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;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jan 2016 19:16:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KBOOT-launching-application-problems-MK22/m-p/510051#M32181</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2016-01-22T19:16:22Z</dc:date>
    </item>
  </channel>
</rss>

