MCU Link Pro does not detect the target

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MCU Link Pro does not detect the target

1,183 Views
prvermas
Contributor I

Dear All,

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,

System configuration:
IDE: MCUXpresso v11.5.0
Target : iMXRT1021 based board with JTAG connector
Flash Tool: MCUXpresso IDE LinkServer ( inc CMSIS-DAP) probe (MCU Link pro)

Problem statement: 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.

Jtag connection is standard 10 pin(2x5) connector, with JTAG_TMS(2) & JTAG_TRSTB(10) both pulled high to 3V

The logs are as below

"Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.5 (Dec 16 2021 12:38:31 - crt_emu_cm_redlink.exe build 2)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in C:/nxp/mqx_v5_rt1020_mcux_rel2/mqx/examples/hello/build/mcux/hello_imxrt1020_evk/Debug\MIMXRT1021xxxxx.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
============= SCRIPT: RT1020_connect.scp =============
RT1020 Connect Script
DpID = 0BD11477
Error: Wire Ack Wait Fault
Error: Wire Ack Wait Fault
Disabling MPU
Error: Wire Ack Wait Fault
Error: Wire Ack Wait Fault
Configure FlexRAM for 128KB OC RAM, 64KB I-TCM, 64KB D-TCM
Error: Wire Ack Wait Fault
Error: Wire Ack Wait Fault
Error: Wire Ack Wait Fault
Finished
============= END SCRIPT =============================
Probe Firmware: MCU-LINK Pro (r0CF) CMSIS-DAP V2.241 (NXP Semiconductors)
Serial Number: 2VMQIP5OBIUHA
VID:PID: 1FC9:0143
USB Path: \\?\hid#vid_1fc9&pid_0143&mi_00#7&1dd5a631&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
connection failed - Em(01). Cannot find MEM-AP selected by core index (check target power).. Retrying
Failed on connect: Em(01). Cannot find MEM-AP selected by core index (check target power)
Connected&Reset. Was: NotConnected. DpID: 0BD11477. CpuID: 00000000. Info: <None>
Last stub error 0: OK
Last sticky error: 0x0 AIndex: 0
No debug bus (MemAp) selected
DAP Speed test unexecuted or failed
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1"

0 Kudos
Reply
1 Reply

1,164 Views
EdwinHz
NXP TechSupport
NXP TechSupport

Hi @prvermas,

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: https://mcuoneclipse.com/2019/01/02/regaining-debug-access-of-nxp-i-mx-rt1064-evk-executing-wfi/

 

BR,

Edwin.

0 Kudos
Reply