<?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: FRDM K64 flashing Problem in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-K64-flashing-Problem/m-p/748406#M45547</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Deepak,&lt;/P&gt;&lt;P&gt;Please update the P&amp;amp;E Micro v118 &lt;A href="https://www.nxp.com/support/developer-resources/run-time-software/kinetis-developer-resources/ides-for-kinetis-mcus/opensda-serial-and-debug-adapter:OPENSDA#FRDM-K64F"&gt;firmware application&lt;/A&gt; for on board OpenSDA debugger.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="PE Micro v118 firmware application.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/34748iBB0DC63D915E73F1/image-size/large?v=v2&amp;amp;px=999" role="button" title="PE Micro v118 firmware application.jpg" alt="PE Micro v118 firmware application.jpg" /&gt;&lt;/span&gt;&lt;BR /&gt;And then use the &lt;A href="http://www.pemicro.com/downloads/download_file.cfm?download_id=393"&gt;Kinetis_Recovery_Utility&lt;/A&gt; halt K64. For more detail, please refer: &lt;A href="https://mcuoneclipse.com/2013/06/16/bricking-and-recovering-frdm-kl25z-boards-reset-swd-clock-and-low-power/"&gt;Bricking and Recovering FRDM-KL25Z Boards: Reset, SWD Clock and Low Power&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pe-recovery-utility.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/34585iBDB85338ED857FDF/image-size/large?v=v2&amp;amp;px=999" role="button" title="pe-recovery-utility.png" alt="pe-recovery-utility.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Hope that help! Have a nice day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Robin&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 03 Jan 2018 09:05:59 GMT</pubDate>
    <dc:creator>Robin_Shen</dc:creator>
    <dc:date>2018-01-03T09:05:59Z</dc:date>
    <item>
      <title>FRDM K64 flashing Problem</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-K64-flashing-Problem/m-p/748405#M45546</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;I am using FRDM K64 Board for flashing example programs, From past few days am working on freertos examples, it was working fine. Now am getting below error&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tue Dec 26, 2017 17:55:18: IAR Embedded Workbench 7.80.4 (armproc.dll) &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\config\debugger\NXP\Kxx.dmac &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\config\debugger\NXP\K6x_Trace.dmac &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: Loading the CMSIS-DAP driver &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: Probe: CMSIS-DAP probe SW module ver 1.12 &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: Probe: CMSIS-DAP S/N '0240022352ee6e4caf3293f4' mapped to a number 00004. &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: EARM v.4.14 &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: Emulation layer version 4.14 &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: Notification to core-connect hookup. &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: MDM-AP detected &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: CPU status FAILED &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: MDM-AP detected &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: MDM-AP detected &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: LowLevelReset(script, delay 200) &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: Calling reset script: ResetAndDisableWatchdog &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: CMD_INTERPRETER: failed &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\config\debugger\NXP\Kxx.dmac(28,13): Error: Operation error. &amp;nbsp;&lt;BR /&gt;Tue Dec 26, 2017 17:55:18: Error while calling macro ResetAndDisableWatchdog &lt;BR /&gt;Tue Dec 26, 2017 17:55:18: MDM-AP detected &lt;BR /&gt;Tue Dec 26, 2017 17:55:19: MDM-AP detected &lt;BR /&gt;Tue Dec 26, 2017 17:55:19: MDM-AP detected &lt;BR /&gt;Tue Dec 26, 2017 17:55:19: MDM-AP detected &lt;BR /&gt;Tue Dec 26, 2017 17:55:20: MDM-AP detected &lt;BR /&gt;Tue Dec 26, 2017 17:55:20: MDM-AP detected &lt;BR /&gt;Tue Dec 26, 2017 17:55:24: Fatal error: Failed to connect to CPU&amp;nbsp;&amp;nbsp; Session aborted! &lt;BR /&gt;Tue Dec 26, 2017 17:55:25: IAR Embedded Workbench 7.80.4 (armproc.dll) &lt;BR /&gt;Tue Dec 26, 2017 17:55:27: Loading the CMSIS-DAP driver &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did not change any configuration in IAR settings. Please Help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Dec 2017 12:24:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-K64-flashing-Problem/m-p/748405#M45546</guid>
      <dc:creator>deepaks</dc:creator>
      <dc:date>2017-12-26T12:24:43Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM K64 flashing Problem</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-K64-flashing-Problem/m-p/748406#M45547</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Deepak,&lt;/P&gt;&lt;P&gt;Please update the P&amp;amp;E Micro v118 &lt;A href="https://www.nxp.com/support/developer-resources/run-time-software/kinetis-developer-resources/ides-for-kinetis-mcus/opensda-serial-and-debug-adapter:OPENSDA#FRDM-K64F"&gt;firmware application&lt;/A&gt; for on board OpenSDA debugger.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="PE Micro v118 firmware application.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/34748iBB0DC63D915E73F1/image-size/large?v=v2&amp;amp;px=999" role="button" title="PE Micro v118 firmware application.jpg" alt="PE Micro v118 firmware application.jpg" /&gt;&lt;/span&gt;&lt;BR /&gt;And then use the &lt;A href="http://www.pemicro.com/downloads/download_file.cfm?download_id=393"&gt;Kinetis_Recovery_Utility&lt;/A&gt; halt K64. For more detail, please refer: &lt;A href="https://mcuoneclipse.com/2013/06/16/bricking-and-recovering-frdm-kl25z-boards-reset-swd-clock-and-low-power/"&gt;Bricking and Recovering FRDM-KL25Z Boards: Reset, SWD Clock and Low Power&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pe-recovery-utility.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/34585iBDB85338ED857FDF/image-size/large?v=v2&amp;amp;px=999" role="button" title="pe-recovery-utility.png" alt="pe-recovery-utility.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Hope that help! Have a nice day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Robin&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jan 2018 09:05:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-K64-flashing-Problem/m-p/748406#M45547</guid>
      <dc:creator>Robin_Shen</dc:creator>
      <dc:date>2018-01-03T09:05:59Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM K64 flashing Problem</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-K64-flashing-Problem/m-p/748407#M45548</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Deepak and Robin, sorry for hijacking but I've run into similar problems with my FRDM-K64F.&amp;nbsp; I plugged it into my Windows 10 laptop and managed to corrupt it in fairly short order, then discovered the problems with Windows 10.&amp;nbsp; I have followed the instructions Robin provided using a Windows 7 computer, but I'm a little confused.&amp;nbsp; I seem to have updated the bootloader with the Daplink bootloader, because now if I plug it in with the reset button pressed, it shows up as a drive labeled "MAINTENANCE" instead of "BOOTLOADER", and according to the text file it is version 0244.&amp;nbsp; I downloaded the P&amp;amp;E drivers, and if I install "DEBUG-FRDM-K64F_Pemicrov108a_for_OpenSDA_v2.0.bin", it shows up as a Pemicro OpenSDA debugger under Jungo devices in Device Manager, which allows me to program and debug the K64.&amp;nbsp; However, it seems that to use it as a mass storage device AND debugger, I need the .SDA file "MSD-DEBUG-FRDM-K64F_Pemicro_v114.SDA".&amp;nbsp; If I start it in bootloader mode and copy that file into "MAINTENANCE", nothing happens.&amp;nbsp; If I unplug it and reconnect it normally, I don't get a mass storage device.&amp;nbsp; Am I missing something?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jan 2018 14:32:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-K64-flashing-Problem/m-p/748407#M45548</guid>
      <dc:creator>davidsherman</dc:creator>
      <dc:date>2018-01-03T14:32:50Z</dc:date>
    </item>
  </channel>
</rss>

