<?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のトピックRe: Hardware failure after operations with FRDM-64F program memory flash</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Hardware-failure-after-operations-with-FRDM-64F-program-memory/m-p/478544#M29223</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Juandres M. Lazaro ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now please test one simple project , check whether it can debug well .&lt;/P&gt;&lt;P&gt;If it also not not download and debug , please update the bootloader of your board refer to the&lt;/P&gt;&lt;P&gt;"FRDM-K64F Freedom Development Platform -Quick Start Guide.pdf" .&lt;/P&gt;&lt;P&gt;I see you use the OpenOCD debug mode,&amp;nbsp; you need drag and past&amp;nbsp; the drive again to the bootloader;&lt;/P&gt;&lt;P&gt;or you can also use the segger jlink debug mode , you need&amp;nbsp; drag and past the "JLink_OpenSDA_V2.bin" to the bootloader .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps&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;P&gt;Have a great day,&lt;BR /&gt;Alice Yang&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Dec 2015 04:29:56 GMT</pubDate>
    <dc:creator>Alice_Yang</dc:creator>
    <dc:date>2015-12-17T04:29:56Z</dc:date>
    <item>
      <title>Hardware failure after operations with FRDM-64F program memory flash</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Hardware-failure-after-operations-with-FRDM-64F-program-memory/m-p/478542#M29221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am performing read and write operations in the flash of my FRDM-64F. Using the fsl_flash KSDK 1.2.&lt;/P&gt;&lt;P&gt;I created the memory areas:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_0.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/1393i51D2DBB7A4697BB7/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_0.png" alt="pastedImage_0.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;In execution of the erase flash operation. The FRDM-64F does not work anymore. Lost communication and does not accept the writing of new hardware:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/1425i588760012895B10C/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The &lt;SPAN style="line-height: 1.5;"&gt;RESET L&lt;/SPAN&gt;&lt;SPAN style="line-height: 1.5;"&gt;ED is slightly access (apparently oscillating) and when you press the reset button it lights normally:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.5;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="2015-12-11 18.03.12.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/1473i2073AB8FC581EEC6/image-size/large?v=v2&amp;amp;px=999" role="button" title="2015-12-11 18.03.12.jpg" alt="2015-12-11 18.03.12.jpg" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="2015-12-11 18.03.59.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/23169i05571164CBD71B2E/image-size/large?v=v2&amp;amp;px=999" role="button" title="2015-12-11 18.03.59.jpg" alt="2015-12-11 18.03.59.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The event happened during debbug program in this passage:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; background: #e8f2fe; font-size: 10pt; font-family: Consolas, serif;"&gt;result = flash_app_EraseSector (flash_app_destAdrss(1,&amp;amp;flash1_InitConfigAlarme),1,&amp;amp;flash1_InitConfigAlarme);&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The function is:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #005032; font-size: 10pt; font-family: Consolas, serif;"&gt;uint32_t&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; &lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt;&lt;STRONG style="background: #d4d4d4;"&gt;flash_app_EraseSector&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; (&lt;/SPAN&gt;&lt;SPAN style="color: #005032; font-size: 10pt; font-family: Consolas, serif;"&gt;uint32_t&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; destAdrss, &lt;/SPAN&gt;&lt;SPAN style="color: #7f0055; font-size: 10pt; font-family: Consolas, serif;"&gt;&lt;STRONG&gt;unsigned&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; &lt;/SPAN&gt;&lt;SPAN style="color: #7f0055; font-size: 10pt; font-family: Consolas, serif;"&gt;&lt;STRONG&gt;char&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; qtdeSetor, &lt;/SPAN&gt;&lt;SPAN style="color: #005032; font-size: 10pt; font-family: Consolas, serif;"&gt;FLASH_SSD_CONFIG&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; *FlashBlk){&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; &lt;/SPAN&gt;&lt;SPAN style="color: #005032; font-size: 10pt; font-family: Consolas, serif;"&gt;uint32_t&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; result;&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; &lt;/SPAN&gt;&lt;SPAN style="color: #7f0055; font-size: 10pt; font-family: Consolas, serif;"&gt;&lt;STRONG&gt;if&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt;(!qtdeSetor) qtdeSetor = 1; &lt;/SPAN&gt;&lt;SPAN style="color: #3f7f5f; font-size: 10pt; font-family: Consolas, serif;"&gt;// Se for 0 ou não existir, assume 1.&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; INT_SYS_DisableIRQGlobal();&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; &lt;/SPAN&gt;&lt;SPAN style="color: #3f7f5f; font-size: 10pt; font-family: Consolas, serif;"&gt;//result = FlashEraseSector(&amp;amp;flash1_InitConfig0, destAdrss, qtdeSetor * FTFx_PSECTOR_SIZE, g_FlashLaunchCommand);&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; result = FlashEraseSector(FlashBlk, destAdrss, qtdeSetor * FTFx_PSECTOR_SIZE, g_FlashLaunchCommand);&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; INT_SYS_EnableIRQGlobal();&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; &lt;/SPAN&gt;&lt;SPAN style="color: #7f0055; font-size: 10pt; font-family: Consolas, serif;"&gt;&lt;STRONG&gt;return&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt; result;&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style="color: #000000; font-size: 10pt; font-family: Consolas, serif;"&gt;}&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What happened?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to get back to normal?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you and I hope me someone help me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Juandres M. Lazaro&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Dec 2015 20:26:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Hardware-failure-after-operations-with-FRDM-64F-program-memory/m-p/478542#M29221</guid>
      <dc:creator>juandreslazaro</dc:creator>
      <dc:date>2015-12-11T20:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware failure after operations with FRDM-64F program memory flash</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Hardware-failure-after-operations-with-FRDM-64F-program-memory/m-p/478543#M29222</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know what went wrong bt it is possible to leave the chip in a state where it resets when the debugger is trying to take command of it which results in difficulties.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usually this can be solved by configuring the debugger to immediately erase the chip on connect. In the Flash configuration's Debugger setup selet the "Mass erase on connect" option:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_0.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/22146iA30DA25C67EE4FC7/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_0.png" alt="pastedImage_0.png" /&gt;&lt;/span&gt;&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;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Kinetis: &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.utasker.com/kinetis.html" rel="nofollow"&gt;http://www.utasker.com/kinetis.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;K64: &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.utasker.com/kinetis/FRDM-K64F.html" rel="nofollow"&gt;http://www.utasker.com/kinetis/FRDM-K64F.html&lt;/A&gt;&lt;SPAN&gt; / &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.utasker.com/kinetis/TWR-K64F120M.html" rel="nofollow"&gt;http://www.utasker.com/kinetis/TWR-K64F120M.html&lt;/A&gt;&lt;SPAN&gt; / &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.utasker.com/kinetis/TWR-K65F180M.html" rel="nofollow"&gt;http://www.utasker.com/kinetis/TWR-K65F180M.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Serial Bootloader for K64 (Ethernet, USB, MSD, KBOOT, AN2295, SREC, SD-card, Memory Stick, Virtual COM SREC): &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.utasker.com/forum/index.php?topic=1873.msg6796#msg6796" rel="nofollow"&gt;http://www.utasker.com/forum/index.php?topic=1873.msg6796#msg6796&lt;/A&gt;&lt;SPAN&gt; / &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.utasker.com/docs/uTasker/uTaskerSerialLoader.PDF" rel="nofollow"&gt;http://www.utasker.com/docs/uTasker/uTaskerSerialLoader.PDF&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;For the complete "out-of-the-box" Kinetis experience and faster time to market &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Dec 2015 22:36:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Hardware-failure-after-operations-with-FRDM-64F-program-memory/m-p/478543#M29222</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2015-12-11T22:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware failure after operations with FRDM-64F program memory flash</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Hardware-failure-after-operations-with-FRDM-64F-program-memory/m-p/478544#M29223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Juandres M. Lazaro ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now please test one simple project , check whether it can debug well .&lt;/P&gt;&lt;P&gt;If it also not not download and debug , please update the bootloader of your board refer to the&lt;/P&gt;&lt;P&gt;"FRDM-K64F Freedom Development Platform -Quick Start Guide.pdf" .&lt;/P&gt;&lt;P&gt;I see you use the OpenOCD debug mode,&amp;nbsp; you need drag and past&amp;nbsp; the drive again to the bootloader;&lt;/P&gt;&lt;P&gt;or you can also use the segger jlink debug mode , you need&amp;nbsp; drag and past the "JLink_OpenSDA_V2.bin" to the bootloader .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps&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;P&gt;Have a great day,&lt;BR /&gt;Alice Yang&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Dec 2015 04:29:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Hardware-failure-after-operations-with-FRDM-64F-program-memory/m-p/478544#M29223</guid>
      <dc:creator>Alice_Yang</dc:creator>
      <dc:date>2015-12-17T04:29:56Z</dc:date>
    </item>
  </channel>
</rss>

