<?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のトピックMCU Boot</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/MCU-Boot/m-p/1375584#M61922</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm having an issue while trying to use the NXP MCU Boot with a MK66FX1.&lt;/P&gt;&lt;P&gt;I used the MK66FN2 SDK to build the bootloader (from what I understood, it should be fully compatible as memory regions are detected automatically by the bootloader).&lt;/P&gt;&lt;P&gt;I can use the bootloader to flash the application using both blhost and KinetisFlashTool.&lt;/P&gt;&lt;P&gt;I can flash the application image as many times as I want, provided that the application never actually boots. After the application boots and then going back to booloader, I get the following on blhost when trying to update the application:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;Inject command 'flash-image'&lt;BR /&gt;Successful generic response to command 'flash-erase-region'&lt;BR /&gt;Wrote 51536 bytes to address 0xa000&lt;BR /&gt;Successful generic response to command 'write-memory'&lt;BR /&gt;(1/1) 1%GetOverlappedResult failed with error 31: A device attached to the system is not functioning.&lt;BR /&gt;Data phase write aborted by status 0x1 Failure.&lt;BR /&gt;Response status = 10004 (0x2714) No response packet from target device.&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I also tried without the erase command, and the new firmware gets uploaded but not written to flash, but only if I never do an erase. After any erase I can't upload anything, getting the error above.&lt;/P&gt;&lt;P&gt;I checked the hex file for the application and all the necessary reserved addresses are correctly (as far as I could tell) created, mainly the BCA, which is all 0xFF. The Flash Configuration parameters are set to 0xFE FF.&lt;/P&gt;&lt;P&gt;My application is running in HSRUN and the bootloader is running in RUN mode.&lt;/P&gt;&lt;P&gt;I imagine that something on the application is changing some configuration and blocking the bootloader from writing to flash, although it can erase the flash.&lt;/P&gt;&lt;P&gt;After the application blocked the access, I downloaded the bootloader portion of memory from the chip with a segger debugger, erased the chip and then reflashed the downloaded memory portion and the bootloader returned to working conditions. So the application is not corrupting the bootloader.&lt;/P&gt;&lt;P&gt;Is there any place where I can look to find the issue?&lt;/P&gt;&lt;P&gt;Any help would be appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Nov 2021 11:14:25 GMT</pubDate>
    <dc:creator>JoaoQueiros</dc:creator>
    <dc:date>2021-11-23T11:14:25Z</dc:date>
    <item>
      <title>MCU Boot</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/MCU-Boot/m-p/1375584#M61922</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm having an issue while trying to use the NXP MCU Boot with a MK66FX1.&lt;/P&gt;&lt;P&gt;I used the MK66FN2 SDK to build the bootloader (from what I understood, it should be fully compatible as memory regions are detected automatically by the bootloader).&lt;/P&gt;&lt;P&gt;I can use the bootloader to flash the application using both blhost and KinetisFlashTool.&lt;/P&gt;&lt;P&gt;I can flash the application image as many times as I want, provided that the application never actually boots. After the application boots and then going back to booloader, I get the following on blhost when trying to update the application:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;Inject command 'flash-image'&lt;BR /&gt;Successful generic response to command 'flash-erase-region'&lt;BR /&gt;Wrote 51536 bytes to address 0xa000&lt;BR /&gt;Successful generic response to command 'write-memory'&lt;BR /&gt;(1/1) 1%GetOverlappedResult failed with error 31: A device attached to the system is not functioning.&lt;BR /&gt;Data phase write aborted by status 0x1 Failure.&lt;BR /&gt;Response status = 10004 (0x2714) No response packet from target device.&amp;nbsp;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I also tried without the erase command, and the new firmware gets uploaded but not written to flash, but only if I never do an erase. After any erase I can't upload anything, getting the error above.&lt;/P&gt;&lt;P&gt;I checked the hex file for the application and all the necessary reserved addresses are correctly (as far as I could tell) created, mainly the BCA, which is all 0xFF. The Flash Configuration parameters are set to 0xFE FF.&lt;/P&gt;&lt;P&gt;My application is running in HSRUN and the bootloader is running in RUN mode.&lt;/P&gt;&lt;P&gt;I imagine that something on the application is changing some configuration and blocking the bootloader from writing to flash, although it can erase the flash.&lt;/P&gt;&lt;P&gt;After the application blocked the access, I downloaded the bootloader portion of memory from the chip with a segger debugger, erased the chip and then reflashed the downloaded memory portion and the bootloader returned to working conditions. So the application is not corrupting the bootloader.&lt;/P&gt;&lt;P&gt;Is there any place where I can look to find the issue?&lt;/P&gt;&lt;P&gt;Any help would be appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Nov 2021 11:14:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/MCU-Boot/m-p/1375584#M61922</guid>
      <dc:creator>JoaoQueiros</dc:creator>
      <dc:date>2021-11-23T11:14:25Z</dc:date>
    </item>
    <item>
      <title>Re: MCU Boot</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/MCU-Boot/m-p/1375606#M61923</link>
      <description>&lt;P&gt;Dont understand it fully, but disabling BL_FEATURE_ENABLE_FLASH_PROGRAM_SECTION&amp;nbsp; on the bootloader fixed the issue.&lt;/P&gt;&lt;P&gt;If anyone has any insights as to why this needs to be off, I would like also to know.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Nov 2021 11:55:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/MCU-Boot/m-p/1375606#M61923</guid>
      <dc:creator>JoaoQueiros</dc:creator>
      <dc:date>2021-11-23T11:55:34Z</dc:date>
    </item>
  </channel>
</rss>

