<?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のトピックKinetis K60 FTFL Erase Block</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K60-FTFL-Erase-Block/m-p/441120#M25839</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 have a product that includes a firmware upgrade, when running in the field the upgrade will occasionally fail (about 5% of the time), and completely brick the device. I can't see anything obviously wrong so I am going over all the code with a fine tooth comb trying to find what the problem is...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found a strange issue with the erasing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When trying to do a mass erase in preparation for the firmware write, for some reason when I run the erase flash block command at address 0x40000 it fails with MGSTAT0 error (i.e. verify failed), but if I erase the block sector-by-sector and manually verify then it is erased and doesn't report any errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I then read out the memory using JTAG Commander following a block erase, the binary file shows the upper block to be correctly erased.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anybody have any idea why it is reporting a fail when it is actually working?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The erase all blocks command also fails with a verify error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Things I have checked:&lt;/P&gt;&lt;P&gt;* All the flash protection registers are 0xFF&lt;/P&gt;&lt;P&gt;* The flash configuration is set to 0xFFFFFFFE&lt;/P&gt;&lt;P&gt;* Watchdog is disabled&lt;/P&gt;&lt;P&gt;* Interrupts are disabled&lt;/P&gt;&lt;P&gt;* The code is running in RAM&lt;/P&gt;&lt;P&gt;* fails whether or not debugger is attached&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using a K60N512VLQ10 rev 4N22D&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;James&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 Jul 2015 17:05:56 GMT</pubDate>
    <dc:creator>James8</dc:creator>
    <dc:date>2015-07-23T17:05:56Z</dc:date>
    <item>
      <title>Kinetis K60 FTFL Erase Block</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K60-FTFL-Erase-Block/m-p/441120#M25839</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 have a product that includes a firmware upgrade, when running in the field the upgrade will occasionally fail (about 5% of the time), and completely brick the device. I can't see anything obviously wrong so I am going over all the code with a fine tooth comb trying to find what the problem is...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found a strange issue with the erasing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When trying to do a mass erase in preparation for the firmware write, for some reason when I run the erase flash block command at address 0x40000 it fails with MGSTAT0 error (i.e. verify failed), but if I erase the block sector-by-sector and manually verify then it is erased and doesn't report any errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I then read out the memory using JTAG Commander following a block erase, the binary file shows the upper block to be correctly erased.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anybody have any idea why it is reporting a fail when it is actually working?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The erase all blocks command also fails with a verify error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Things I have checked:&lt;/P&gt;&lt;P&gt;* All the flash protection registers are 0xFF&lt;/P&gt;&lt;P&gt;* The flash configuration is set to 0xFFFFFFFE&lt;/P&gt;&lt;P&gt;* Watchdog is disabled&lt;/P&gt;&lt;P&gt;* Interrupts are disabled&lt;/P&gt;&lt;P&gt;* The code is running in RAM&lt;/P&gt;&lt;P&gt;* fails whether or not debugger is attached&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using a K60N512VLQ10 rev 4N22D&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;James&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jul 2015 17:05:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K60-FTFL-Erase-Block/m-p/441120#M25839</guid>
      <dc:creator>James8</dc:creator>
      <dc:date>2015-07-23T17:05:56Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis K60 FTFL Erase Block</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K60-FTFL-Erase-Block/m-p/441121#M25840</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi James,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We don't find any record or errata info about your mentioned issue.&lt;/P&gt;&lt;P&gt;I also checked Kinetis_100MHz validation project record without similar failure report.&lt;/P&gt;&lt;P&gt;How many chips on your site with the same behavior?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Ma Hui&lt;/P&gt;&lt;P&gt;&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>Mon, 27 Jul 2015 05:36:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K60-FTFL-Erase-Block/m-p/441121#M25840</guid>
      <dc:creator>Hui_Ma</dc:creator>
      <dc:date>2015-07-27T05:36:52Z</dc:date>
    </item>
  </channel>
</rss>

