<?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: Error in final launch sequence</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/Error-in-final-launch-sequence/m-p/854378#M33976</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I understand, and believe you are right! (Some boards have a hardware problem).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BUT, what about this error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;02: Failed on connect&lt;BR /&gt; 02: Failed on connect&lt;BR /&gt; Target marked as not debuggable.&lt;BR /&gt; Emu(0): Connected. Was: None. DpID: EDB6. Info: HID64HS12&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error in final launch sequence&lt;BR /&gt; Failed to execute MI command:&lt;BR /&gt;-target-select extended-remote | crt_emu_cm3_nxp -msg-port=54784 -g -mi -2 -pLPC1769 -vendor=NXP -vc -e0 -wire=hid -flash-driver=LPC175x_6x_512.cfx&lt;BR /&gt;Error message from debugger back end:&lt;BR /&gt;Remote communication error. Target disconnected.: No error.&lt;BR /&gt; Remote communication error. Target disconnected.: No error.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Jan 2019 15:28:29 GMT</pubDate>
    <dc:creator>hazemselmi</dc:creator>
    <dc:date>2019-01-30T15:28:29Z</dc:date>
    <item>
      <title>Error in final launch sequence</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Error-in-final-launch-sequence/m-p/854374#M33972</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am using LPC1769 board and LPCxpresso IDE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I click debug, it ends with error message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error in final launch sequence&lt;BR /&gt;Error: Error reported by server (redlinkserv.exe):&lt;BR /&gt;Status fail.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;I am using 15 lpc1769 board (for teaching purposes), all of them work fine (using the same code and same USB cable) except 3 boards that give me some problems.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2019 21:04:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Error-in-final-launch-sequence/m-p/854374#M33972</guid>
      <dc:creator>hazemselmi</dc:creator>
      <dc:date>2019-01-22T21:04:34Z</dc:date>
    </item>
    <item>
      <title>Re: Error in final launch sequence</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Error-in-final-launch-sequence/m-p/854375#M33973</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See&amp;nbsp;&lt;A _jive_internal="true" href="https://community.nxp.com/message/630748"&gt;Regaining debug access to target MCU&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and regards,&lt;/P&gt;&lt;P&gt;MCUXpresso Support&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2019 21:39:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Error-in-final-launch-sequence/m-p/854375#M33973</guid>
      <dc:creator>lpcxpresso_supp</dc:creator>
      <dc:date>2019-01-22T21:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: Error in final launch sequence</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Error-in-final-launch-sequence/m-p/854376#M33974</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply.&lt;/P&gt;&lt;P&gt;This worked for two boards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However few still have some problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The error is:&lt;/P&gt;&lt;P&gt;Error in final launch sequence&lt;BR /&gt;Error: Error reported by server (redlinkserv.exe):&lt;BR /&gt;Status fail&lt;BR /&gt;LinkServer has been terminated and will be restarted.&lt;BR /&gt;Please restart your debug session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(Also I noted that some ICs in lpc-link became extremely hot).&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2019 20:09:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Error-in-final-launch-sequence/m-p/854376#M33974</guid>
      <dc:creator>hazemselmi</dc:creator>
      <dc:date>2019-01-23T20:09:22Z</dc:date>
    </item>
    <item>
      <title>Re: Error in final launch sequence</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Error-in-final-launch-sequence/m-p/854377#M33975</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It sounds like you're using the older NXP LPCXpresso1769 Rev. B boards. The LPCXpresso1769 Rev. D use CMSIS-DAP, and the debug circuit is different. In both cases, power is supplied to the LPC1769 through the debug circuit. If any IC in this circuit is hot to the touch, it suggests a hardware problem. Possibly due to static damage which is common in a classroom environment. Sorry we can't help further.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and regards,&lt;/P&gt;&lt;P&gt;MCUXpresso Support&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2019 22:24:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Error-in-final-launch-sequence/m-p/854377#M33975</guid>
      <dc:creator>lpcxpresso_supp</dc:creator>
      <dc:date>2019-01-23T22:24:25Z</dc:date>
    </item>
    <item>
      <title>Re: Error in final launch sequence</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Error-in-final-launch-sequence/m-p/854378#M33976</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I understand, and believe you are right! (Some boards have a hardware problem).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BUT, what about this error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;02: Failed on connect&lt;BR /&gt; 02: Failed on connect&lt;BR /&gt; Target marked as not debuggable.&lt;BR /&gt; Emu(0): Connected. Was: None. DpID: EDB6. Info: HID64HS12&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error in final launch sequence&lt;BR /&gt; Failed to execute MI command:&lt;BR /&gt;-target-select extended-remote | crt_emu_cm3_nxp -msg-port=54784 -g -mi -2 -pLPC1769 -vendor=NXP -vc -e0 -wire=hid -flash-driver=LPC175x_6x_512.cfx&lt;BR /&gt;Error message from debugger back end:&lt;BR /&gt;Remote communication error. Target disconnected.: No error.&lt;BR /&gt; Remote communication error. Target disconnected.: No error.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2019 15:28:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Error-in-final-launch-sequence/m-p/854378#M33976</guid>
      <dc:creator>hazemselmi</dc:creator>
      <dc:date>2019-01-30T15:28:29Z</dc:date>
    </item>
  </channel>
</rss>

