<?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のトピックLPC43S57: Hardfault in internal NXP bootloader</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC43S57-Hardfault-in-internal-NXP-bootloader/m-p/831746#M33208</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are running into an issue with our generated application. Some information about this application:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Running from external SPIFI flash&lt;/LI&gt;&lt;LI&gt;Vector table located at 0x14000000&lt;/LI&gt;&lt;LI&gt;Build with IAR (version 8.30) in Release mode (optimisation high)&lt;/LI&gt;&lt;LI&gt;Startup code based on LPCOpen&amp;nbsp;3.02 (keil/iar mcb4357), using file&amp;nbsp;iar_startup_lpc18xx43xx.s&lt;/LI&gt;&lt;LI&gt;CPU ID:&amp;nbsp;0x410FC241&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Most of the time this works correctly, but once in a while the build does not start at all: the reset vector in our application is not even executed (this can be reproduced: when building the same code again this also happens, even when building on another machine). When we stop the processor using JTAG we see that the PC is pointing at 0x10400042. This address is within the internal NXP chip-bootloader. The vector table of this chip bootloader application (located at 0x10400000) shows that this is the Hardfault handler. The debugger reports:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exception occured at PC = 0x10400194, LR = 0x1040b1ab&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why would the internal bootloader generate a hard-fault? What checks are done in the bootloader, which could result in a hard-fault? Is there a way to extract more information from the internal bootloader on what the cause of the problem might be?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Below is the vector table from our application in SREC format:&lt;/P&gt;&lt;P&gt;S3151400000030500010590200140D700014F76A0014D1&lt;BR /&gt;S3151400001001840014EF6A0014FF6A00148478FD77D3&lt;BR /&gt;S31514000020000000000000000000000000ED83001432&lt;BR /&gt;S31514000030F183001400000000F5830014F983001402&lt;BR /&gt;S3151400004009840014098400140984001400000000B3&lt;BR /&gt;S315140000500984001409840014098400140984001402&lt;BR /&gt;S31514000060098400140984001409840014C529001491&lt;BR /&gt;S3151400007009840014098400140984001409840014E2&lt;BR /&gt;S3151400008009840014098400140984001409840014D2&lt;BR /&gt;S3151400009009840014098400140984001409840014C2&lt;BR /&gt;S315140000A009840014098400140984001409840014B2&lt;BR /&gt;S315140000B009840014098400140984001409840014A2&lt;BR /&gt;S315140000C00984001409840014098400140984001492&lt;BR /&gt;S315140000D00984001409840014098400140984001482&lt;BR /&gt;S315140000E00984001409840014098400140984001472&lt;BR /&gt;S315140000F00000000009840014098400140984001403&lt;BR /&gt;S3151400010000000000DD510014098400140984001451&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited:&lt;/P&gt;&lt;P&gt;The exact message in the Debug window from IAR:&lt;/P&gt;&lt;P&gt;Tue Dec 04, 2018 14:13:14: HardFault exception. &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: The processor has escalated a configurable-priority exception to HardFault. &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: A precise data access error has occurred (CFSR.PRECISERR, BFAR) at data address 0x10008000. &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: Exception occured at PC = 0x10400194, LR = 0x1040b1ab &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: See the call stack for more information. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Johan Borkhuis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Dec 2018 08:50:49 GMT</pubDate>
    <dc:creator>johanborkhuis</dc:creator>
    <dc:date>2018-12-04T08:50:49Z</dc:date>
    <item>
      <title>LPC43S57: Hardfault in internal NXP bootloader</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC43S57-Hardfault-in-internal-NXP-bootloader/m-p/831746#M33208</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are running into an issue with our generated application. Some information about this application:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Running from external SPIFI flash&lt;/LI&gt;&lt;LI&gt;Vector table located at 0x14000000&lt;/LI&gt;&lt;LI&gt;Build with IAR (version 8.30) in Release mode (optimisation high)&lt;/LI&gt;&lt;LI&gt;Startup code based on LPCOpen&amp;nbsp;3.02 (keil/iar mcb4357), using file&amp;nbsp;iar_startup_lpc18xx43xx.s&lt;/LI&gt;&lt;LI&gt;CPU ID:&amp;nbsp;0x410FC241&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Most of the time this works correctly, but once in a while the build does not start at all: the reset vector in our application is not even executed (this can be reproduced: when building the same code again this also happens, even when building on another machine). When we stop the processor using JTAG we see that the PC is pointing at 0x10400042. This address is within the internal NXP chip-bootloader. The vector table of this chip bootloader application (located at 0x10400000) shows that this is the Hardfault handler. The debugger reports:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exception occured at PC = 0x10400194, LR = 0x1040b1ab&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why would the internal bootloader generate a hard-fault? What checks are done in the bootloader, which could result in a hard-fault? Is there a way to extract more information from the internal bootloader on what the cause of the problem might be?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Below is the vector table from our application in SREC format:&lt;/P&gt;&lt;P&gt;S3151400000030500010590200140D700014F76A0014D1&lt;BR /&gt;S3151400001001840014EF6A0014FF6A00148478FD77D3&lt;BR /&gt;S31514000020000000000000000000000000ED83001432&lt;BR /&gt;S31514000030F183001400000000F5830014F983001402&lt;BR /&gt;S3151400004009840014098400140984001400000000B3&lt;BR /&gt;S315140000500984001409840014098400140984001402&lt;BR /&gt;S31514000060098400140984001409840014C529001491&lt;BR /&gt;S3151400007009840014098400140984001409840014E2&lt;BR /&gt;S3151400008009840014098400140984001409840014D2&lt;BR /&gt;S3151400009009840014098400140984001409840014C2&lt;BR /&gt;S315140000A009840014098400140984001409840014B2&lt;BR /&gt;S315140000B009840014098400140984001409840014A2&lt;BR /&gt;S315140000C00984001409840014098400140984001492&lt;BR /&gt;S315140000D00984001409840014098400140984001482&lt;BR /&gt;S315140000E00984001409840014098400140984001472&lt;BR /&gt;S315140000F00000000009840014098400140984001403&lt;BR /&gt;S3151400010000000000DD510014098400140984001451&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited:&lt;/P&gt;&lt;P&gt;The exact message in the Debug window from IAR:&lt;/P&gt;&lt;P&gt;Tue Dec 04, 2018 14:13:14: HardFault exception. &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: The processor has escalated a configurable-priority exception to HardFault. &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: A precise data access error has occurred (CFSR.PRECISERR, BFAR) at data address 0x10008000. &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: Exception occured at PC = 0x10400194, LR = 0x1040b1ab &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: &lt;BR /&gt;Tue Dec 04, 2018 14:13:14: See the call stack for more information. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Johan Borkhuis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Dec 2018 08:50:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC43S57-Hardfault-in-internal-NXP-bootloader/m-p/831746#M33208</guid>
      <dc:creator>johanborkhuis</dc:creator>
      <dc:date>2018-12-04T08:50:49Z</dc:date>
    </item>
    <item>
      <title>Re: LPC43S57: Hardfault in internal NXP bootloader</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC43S57-Hardfault-in-internal-NXP-bootloader/m-p/831747#M33209</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Johan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you share a simple example project so I can reproduce the behavior on my side?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;BR /&gt;Carlos Mendoza&lt;BR /&gt;Technical Support Engineer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Dec 2018 22:54:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC43S57-Hardfault-in-internal-NXP-bootloader/m-p/831747#M33209</guid>
      <dc:creator>Carlos_Mendoza</dc:creator>
      <dc:date>2018-12-18T22:54:38Z</dc:date>
    </item>
    <item>
      <title>Re: LPC43S57: Hardfault in internal NXP bootloader</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC43S57-Hardfault-in-internal-NXP-bootloader/m-p/831748#M33210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Carlos,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your reply. I just sent you a private message on this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Johan Borkhuis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Dec 2018 07:26:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC43S57-Hardfault-in-internal-NXP-bootloader/m-p/831748#M33210</guid>
      <dc:creator>johanborkhuis</dc:creator>
      <dc:date>2018-12-19T07:26:22Z</dc:date>
    </item>
  </channel>
</rss>

