<?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>LPC Microcontrollers中的主题 Re: Fail bootloader LPC1857</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1646113#M52439</link>
    <description>&lt;P&gt;Yes, you should be able to erase the device and re-flash it, as Alice_Yang suggested.&lt;/P&gt;&lt;P&gt;However, I would also check the project / linker settings of your firmware, especially the version that "killed" the bootloader.&lt;BR /&gt;Perhaps you accidentally overwrote the bootloader, or some critical parts of it.&lt;BR /&gt;Or parts of the application are located in the same sector(s) as bootloader code/data, which caused it to erase this sector. This should be apparent in the map file, and even in the *.HEX / *.S19 file.&lt;/P&gt;&lt;P&gt;My company uses custom bootloaders for all its ECU devices.&lt;BR /&gt;This BL resides in a separate sector the application never touches, and the BL contains code that checks the address of every *.S19 record it receives for flashing.&lt;/P&gt;</description>
    <pubDate>Mon, 08 May 2023 05:17:21 GMT</pubDate>
    <dc:creator>frank_m</dc:creator>
    <dc:date>2023-05-08T05:17:21Z</dc:date>
    <item>
      <title>Fail bootloader LPC1857</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1643685#M52374</link>
      <description>&lt;P&gt;Dear friends,&lt;/P&gt;&lt;P&gt;I'm using a STM32F072 Discovery Kit board to write a firmware in .hex format on my project's board whose microcontroller is the LPC1857. After recording a few times (indefinite number of times) the microcontroller enters a condition in which it is no longer possible to update its firmware. The microcontroller continues to work with the last firmware written, but it does not allow new firmware to be written. Has any friend gone through a similar situation? Could you please suggest me a way out of this problem?&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2023 14:42:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1643685#M52374</guid>
      <dc:creator>rubensjunior</dc:creator>
      <dc:date>2023-05-03T14:42:56Z</dc:date>
    </item>
    <item>
      <title>Re: Fail bootloader LPC1857</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1644420#M52387</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/162807"&gt;@rubensjunior&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please check whether the "second bootloader "( the code communicate with&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;STM32F072&amp;nbsp;&lt;/SPAN&gt; ) still exist in lpc1857, and whether meet the condition about update firmware.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Alice&lt;/P&gt;</description>
      <pubDate>Thu, 04 May 2023 08:01:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1644420#M52387</guid>
      <dc:creator>Alice_Yang</dc:creator>
      <dc:date>2023-05-04T08:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: Fail bootloader LPC1857</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1644452#M52389</link>
      <description>&lt;P&gt;&lt;EM&gt;&amp;gt; I'm using a STM32F072 Discovery Kit board to write a firmware in .hex format on my project's board whose microcontroller is the LPC1857.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I suppose the "STM32" part is not relevant here, and only works as "comunication device".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;gt; After recording a few times (indefinite number of times) the microcontroller enters a condition in which it is no longer possible to update its firmware. The microcontroller continues to work with the last firmware written, but it does not allow new firmware to be written.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You might have activated the CRP feature, perhaps by accident.&lt;BR /&gt;I would check the LPC1857 datasheet in this regard, and compare with both the map file and the .HEX file if this is the case.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 May 2023 08:17:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1644452#M52389</guid>
      <dc:creator>frank_m</dc:creator>
      <dc:date>2023-05-04T08:17:46Z</dc:date>
    </item>
    <item>
      <title>Re: Fail bootloader LPC1857</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1645698#M52427</link>
      <description>&lt;P&gt;Dears &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/137574"&gt;@frank_m&lt;/a&gt;&amp;nbsp; and &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/27788"&gt;@Alice_Yang&lt;/a&gt;&amp;nbsp;, I checked that CRP is not enabled. Is there any way for me to erase the firmware that is recorded on this microcontroller and start the recording process again?&lt;/P&gt;</description>
      <pubDate>Fri, 05 May 2023 18:52:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1645698#M52427</guid>
      <dc:creator>rubensjunior</dc:creator>
      <dc:date>2023-05-05T18:52:15Z</dc:date>
    </item>
    <item>
      <title>Re: Fail bootloader LPC1857</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1645830#M52431</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/162807"&gt;@rubensjunior&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Enter ISP mode, then use Flash Magic full erase you chip, about enter ISP, you can refer to user manual for lpc1857 or below thread:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools-/lpcxpresso845-max-board-for-lpc84x-mcu-family:OM13097" target="_blank"&gt;https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools-/lpcxpresso845-max-board-for-lpc84x-mcu-family:OM13097&lt;/A&gt;&amp;nbsp; &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Alice&lt;/P&gt;</description>
      <pubDate>Sat, 06 May 2023 02:46:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1645830#M52431</guid>
      <dc:creator>Alice_Yang</dc:creator>
      <dc:date>2023-05-06T02:46:06Z</dc:date>
    </item>
    <item>
      <title>Re: Fail bootloader LPC1857</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1646113#M52439</link>
      <description>&lt;P&gt;Yes, you should be able to erase the device and re-flash it, as Alice_Yang suggested.&lt;/P&gt;&lt;P&gt;However, I would also check the project / linker settings of your firmware, especially the version that "killed" the bootloader.&lt;BR /&gt;Perhaps you accidentally overwrote the bootloader, or some critical parts of it.&lt;BR /&gt;Or parts of the application are located in the same sector(s) as bootloader code/data, which caused it to erase this sector. This should be apparent in the map file, and even in the *.HEX / *.S19 file.&lt;/P&gt;&lt;P&gt;My company uses custom bootloaders for all its ECU devices.&lt;BR /&gt;This BL resides in a separate sector the application never touches, and the BL contains code that checks the address of every *.S19 record it receives for flashing.&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2023 05:17:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Fail-bootloader-LPC1857/m-p/1646113#M52439</guid>
      <dc:creator>frank_m</dc:creator>
      <dc:date>2023-05-08T05:17:21Z</dc:date>
    </item>
  </channel>
</rss>

