<?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>topic Re: MIMXRT1050 EVK - DAPLink - debug fails in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/MIMXRT1050-EVK-DAPLink-debug-fails/m-p/742177#M224</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;pls refer to the topic as below:&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" class="link-titled" href="https://community.nxp.com/thread/465595#comment-969444" title="https://community.nxp.com/thread/465595#comment-969444"&gt;https://community.nxp.com/thread/465595#comment-969444&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/message/970138"&gt;https://community.nxp.com/message/970138&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Apr 2018 08:03:38 GMT</pubDate>
    <dc:creator>joanxie</dc:creator>
    <dc:date>2018-04-09T08:03:38Z</dc:date>
    <item>
      <title>MIMXRT1050 EVK - DAPLink - debug fails</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/MIMXRT1050-EVK-DAPLink-debug-fails/m-p/742176#M223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EDIT: The fix was to mass erase the hyperflash image first as described in:&amp;nbsp;&lt;A href="https://mcuoneclipse.com/2017/12/16/mcuxpresso-ide-v10-1-0-with-i-mx-rt1052-crossover-processor/"&gt;https://mcuoneclipse.com/2017/12/16/mcuxpresso-ide-v10-1-0-with-i-mx-rt1052-crossover-processor/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Afterwards, flashing worked like a charm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm following the guide on starting with the MIMX RT 1050 EVK (setting up the project for RT1050EVK from the SDK). The issue that I'm having is with the "Project Debug" step. I can successfully attach a DAPLink/CMSIS-DAP probe that is found by the MCUExpresso IDE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, when launching the debug, I get the following error message:&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;&lt;/P&gt;MCUXpresso RedlinkMulti Driver v10.1 (Dec 19 2017 16:58:35 - crt_emu_cm_redlink build 390)&lt;BR /&gt;Found chip XML file in C:/Users/XXXXXXXX/Documents/MCUXpressoIDE_10.1.1_606/workspace/MIMXRT1052xxxxx_Project_test_mimxrt1050/Debug\MIMXRT1052xxxxx.xml&lt;BR /&gt;Reconnected to existing redlink server (PID 4294967295)&lt;BR /&gt;Connecting to probe 1 core 0 (server PID unknown) gave 'OK'&lt;BR /&gt;Probe Firmware: DAPLink CMSIS-DAP (ARM)&lt;BR /&gt;Serial Number:&amp;nbsp; 0227000041114e450004300dc40300245ab1000097969900&lt;BR /&gt;VID:PID:&amp;nbsp; 0D28:0204&lt;BR /&gt;USB Path: &lt;A&gt;\\?\hid#vid_0d28&amp;amp;pid_0204&amp;amp;mi_03#7&amp;amp;247a767&amp;amp;0&amp;amp;0000#{4d1e55b2-f16f-11cf-88cb-001111000030&lt;/A&gt;}&lt;BR /&gt;connection failed - Ee(FF). Redlink interface error 255... Retrying&lt;BR /&gt;Failed on connect: Ee(FF). Redlink interface error 255.&lt;BR /&gt;Connected&amp;amp;Reset. Was: NotConnected. DpID: 00000000. CpuID: 00000000. Info: &amp;lt;None&amp;gt;&lt;BR /&gt;Last stub error 0: OK&lt;BR /&gt;Last sticky error: 0x0 AIndex: 0&lt;BR /&gt;Debug bus selected: MemAp 0&lt;BR /&gt;DAP Speed test unexecuted or failed&lt;BR /&gt;Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.&lt;BR /&gt;(100) Target Connection Failed&lt;BR /&gt;error closing down debug session - Ee(FF). Redlink interface error 255.&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additionally, I get the following dialog that is a bit surprising. I'm using SDK generated from the MCUexpress SDK builder for MIMXRT1050 and used it as board config during project setup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Board: MIMXRT1050-EVK, REV A&lt;/P&gt;&lt;P&gt;uC: MIMXRT1052DVL6A 0NN04V CTZA1730A&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Luke&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Mar 2018 13:21:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/MIMXRT1050-EVK-DAPLink-debug-fails/m-p/742176#M223</guid>
      <dc:creator>treto</dc:creator>
      <dc:date>2018-03-27T13:21:09Z</dc:date>
    </item>
    <item>
      <title>Re: MIMXRT1050 EVK - DAPLink - debug fails</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/MIMXRT1050-EVK-DAPLink-debug-fails/m-p/742177#M224</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;pls refer to the topic as below:&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" class="link-titled" href="https://community.nxp.com/thread/465595#comment-969444" title="https://community.nxp.com/thread/465595#comment-969444"&gt;https://community.nxp.com/thread/465595#comment-969444&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/message/970138"&gt;https://community.nxp.com/message/970138&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Apr 2018 08:03:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/MIMXRT1050-EVK-DAPLink-debug-fails/m-p/742177#M224</guid>
      <dc:creator>joanxie</dc:creator>
      <dc:date>2018-04-09T08:03:38Z</dc:date>
    </item>
  </channel>
</rss>

