<?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>i.MX ProcessorsのトピックRe: MCU Link Pro does not detect the target</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/MCU-Link-Pro-does-not-detect-the-target/m-p/1617131#M202871</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/7640"&gt;@prvermas&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Please look into the following block post by Erich Styger, I'm sure it will prove useful for your inquiry on recovering debug access for your i.MX RT:&amp;nbsp;&lt;A href="https://mcuoneclipse.com/2019/01/02/regaining-debug-access-of-nxp-i-mx-rt1064-evk-executing-wfi/" target="_blank"&gt;https://mcuoneclipse.com/2019/01/02/regaining-debug-access-of-nxp-i-mx-rt1064-evk-executing-wfi/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Edwin.&lt;/P&gt;</description>
    <pubDate>Thu, 16 Mar 2023 21:53:55 GMT</pubDate>
    <dc:creator>EdwinHz</dc:creator>
    <dc:date>2023-03-16T21:53:55Z</dc:date>
    <item>
      <title>MCU Link Pro does not detect the target</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MCU-Link-Pro-does-not-detect-the-target/m-p/1616856#M202850</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;I need help in trouble shooting an issue regarding the interface of MCU Link pro probe to a target development board based on iMXRT1021 processor,&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;System configuration:&lt;/STRONG&gt;&lt;BR /&gt;IDE: MCUXpresso v11.5.0&lt;BR /&gt;Target : iMXRT1021 based board with JTAG connector&lt;BR /&gt;Flash Tool: MCUXpresso IDE LinkServer ( inc CMSIS-DAP) probe (MCU Link pro)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Problem statement:&lt;/STRONG&gt;&amp;nbsp;When trying to load the firmware (.axf) the gui gives an error that target not detected. Tried with both internal power (MCU LINK Pro) as well as external board power supply.&lt;/P&gt;&lt;P&gt;Jtag connection is standard 10 pin(2x5) connector, with JTAG_TMS(2) &amp;amp; JTAG_TRSTB(10) both pulled high to 3V&lt;/P&gt;&lt;P&gt;The logs are as below&lt;/P&gt;&lt;P&gt;"&lt;EM&gt;Checking MCU info...&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Scanning for targets...&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Executing flash action...&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;MCUXpresso IDE RedlinkMulti Driver v11.5 (Dec 16 2021 12:38:31 - crt_emu_cm_redlink.exe build 2)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;( 0) Reading remote configuration&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Wc(03). No cache support.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Found chip XML file in C:/nxp/mqx_v5_rt1020_mcux_rel2/mqx/examples/hello/build/mcux/hello_imxrt1020_evk/Debug\MIMXRT1021xxxxx.xml&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;( 5) Remote configuration complete&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Reconnected to existing LinkServer process.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;============= SCRIPT: RT1020_connect.scp =============&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;RT1020 Connect Script&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DpID = 0BD11477&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Error: Wire Ack Wait Fault&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Error: Wire Ack Wait Fault&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Disabling MPU&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Error: Wire Ack Wait Fault&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Error: Wire Ack Wait Fault&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Configure FlexRAM for 128KB OC RAM, 64KB I-TCM, 64KB D-TCM&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Error: Wire Ack Wait Fault&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Error: Wire Ack Wait Fault&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Error: Wire Ack Wait Fault&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Finished&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;============= END SCRIPT =============================&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Probe Firmware: MCU-LINK Pro (r0CF) CMSIS-DAP V2.241 (NXP Semiconductors)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Serial Number: 2VMQIP5OBIUHA&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;VID:PID: 1FC9:0143&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;USB Path: \\?\hid#vid_1fc9&amp;amp;pid_0143&amp;amp;mi_00#7&amp;amp;1dd5a631&amp;amp;0&amp;amp;0000#{4d1e55b2-f16f-11cf-88cb-001111000030}&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;connection failed - Em(01). Cannot find MEM-AP selected by core index (check target power).. Retrying&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Failed on connect: Em(01). Cannot find MEM-AP selected by core index (check target power)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Connected&amp;amp;Reset. Was: NotConnected. DpID: 0BD11477. CpuID: 00000000. Info: &amp;lt;None&amp;gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Last stub error 0: OK&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Last sticky error: 0x0 AIndex: 0&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;No debug bus (MemAp) selected&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;DAP Speed test unexecuted or failed&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;(100) Target Connection Failed&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Unable to perform operation!&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Command failed with exit code 1&lt;/EM&gt;"&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2023 13:09:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MCU-Link-Pro-does-not-detect-the-target/m-p/1616856#M202850</guid>
      <dc:creator>prvermas</dc:creator>
      <dc:date>2023-03-16T13:09:16Z</dc:date>
    </item>
    <item>
      <title>Re: MCU Link Pro does not detect the target</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MCU-Link-Pro-does-not-detect-the-target/m-p/1617131#M202871</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/7640"&gt;@prvermas&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Please look into the following block post by Erich Styger, I'm sure it will prove useful for your inquiry on recovering debug access for your i.MX RT:&amp;nbsp;&lt;A href="https://mcuoneclipse.com/2019/01/02/regaining-debug-access-of-nxp-i-mx-rt1064-evk-executing-wfi/" target="_blank"&gt;https://mcuoneclipse.com/2019/01/02/regaining-debug-access-of-nxp-i-mx-rt1064-evk-executing-wfi/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Edwin.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2023 21:53:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MCU-Link-Pro-does-not-detect-the-target/m-p/1617131#M202871</guid>
      <dc:creator>EdwinHz</dc:creator>
      <dc:date>2023-03-16T21:53:55Z</dc:date>
    </item>
  </channel>
</rss>

