<?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>Kinetis MicrocontrollersのトピックRecover FRDM-K64F</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Recover-FRDM-K64F/m-p/1386349#M62071</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I get a new&amp;nbsp;FRDM-K64F board and I follow the instrcution on&amp;nbsp;&lt;A href="https://www.nxp.com/document/guide/get-started-with-the-frdm-k64f:NGS-FRDM-K64F" target="_blank"&gt;https://www.nxp.com/document/guide/get-started-with-the-frdm-k64f:NGS-FRDM-K64F&lt;/A&gt;&amp;nbsp;to update firmware but failed.&lt;/P&gt;
&lt;P&gt;In step 6, the LED "SDA" blink and&amp;nbsp;&lt;SPAN&gt;the board enumerates as a drive named "BOOTLOADER". I drag and drop 0244_k20dx_bl_0x5000.bin to that drive. The LED blink faster but there is no drive named MAINTENANCE re-enumerate as described in step 8.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;What should I do to recover it? Thank you.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;BR,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Debin&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 14 Dec 2021 10:07:30 GMT</pubDate>
    <dc:creator>Dong2021</dc:creator>
    <dc:date>2021-12-14T10:07:30Z</dc:date>
    <item>
      <title>Recover FRDM-K64F</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Recover-FRDM-K64F/m-p/1386349#M62071</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I get a new&amp;nbsp;FRDM-K64F board and I follow the instrcution on&amp;nbsp;&lt;A href="https://www.nxp.com/document/guide/get-started-with-the-frdm-k64f:NGS-FRDM-K64F" target="_blank"&gt;https://www.nxp.com/document/guide/get-started-with-the-frdm-k64f:NGS-FRDM-K64F&lt;/A&gt;&amp;nbsp;to update firmware but failed.&lt;/P&gt;
&lt;P&gt;In step 6, the LED "SDA" blink and&amp;nbsp;&lt;SPAN&gt;the board enumerates as a drive named "BOOTLOADER". I drag and drop 0244_k20dx_bl_0x5000.bin to that drive. The LED blink faster but there is no drive named MAINTENANCE re-enumerate as described in step 8.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;What should I do to recover it? Thank you.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;BR,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Debin&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Dec 2021 10:07:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Recover-FRDM-K64F/m-p/1386349#M62071</guid>
      <dc:creator>Dong2021</dc:creator>
      <dc:date>2021-12-14T10:07:30Z</dc:date>
    </item>
    <item>
      <title>Re: Recover FRDM-K64F</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Recover-FRDM-K64F/m-p/1386394#M62072</link>
      <description>&lt;P&gt;FRDM boards get shipped with bootloaders which are not Windows 8 or 10 compatible.So you need to update the bootloader.&lt;/P&gt;&lt;P&gt;If you have a Windows 7 machine at hand, then it is best if you use that. I wrote several articles on that topic, depending on your host environment, for example:&lt;/P&gt;&lt;P&gt;&lt;A href="https://mcuoneclipse.com/2016/08/01/bricking_and_recovering_opensda_boards_in_windows_8_and_10/" target="_blank"&gt;https://mcuoneclipse.com/2016/08/01/bricking_and_recovering_opensda_boards_in_windows_8_and_10/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You might try to disable the Windows search service, see:&lt;/P&gt;&lt;P&gt;&lt;A href="https://mcuoneclipse.com/2018/04/10/recovering-opensda-boards-with-windows-10/" target="_blank"&gt;https://mcuoneclipse.com/2018/04/10/recovering-opensda-boards-with-windows-10/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The good news with the K64 is that the K20 on it is not secured/protected, so you can load/program it with a J-Link or other debug probe. What I have been using successfully is reprogramming it in my classes with the patched bootloader described here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://mcuoneclipse.com/2017/10/29/adding-a-delay-to-the-arm-daplink-bootloader/" target="_blank"&gt;https://mcuoneclipse.com/2017/10/29/adding-a-delay-to-the-arm-daplink-bootloader/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This one has not failed in a single case for several years, and have been used in hundreds of cases with students in my labs :-).&lt;/P&gt;&lt;P&gt;I hope this helps,&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Dec 2021 10:51:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Recover-FRDM-K64F/m-p/1386394#M62072</guid>
      <dc:creator>ErichStyger</dc:creator>
      <dc:date>2021-12-14T10:51:37Z</dc:date>
    </item>
  </channel>
</rss>

