IMXRT1050-EVKB - Error debugging using CMSIS-DAP

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

IMXRT1050-EVKB - Error debugging using CMSIS-DAP

1,605 Views
jens_demey
Contributor I

Trying to download new code in the IMXRT1050-EVKB board using CMSIS-DAP following error is shown:

Error in final launch sequence
Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=50432 -g -mi -4 -pMIMXRT1052xxxxB -vendor=NXP --no-packed -reset= -ProbeHandle=1 -CoreIndex=0 -cache=disable -x E:/Projects/PERSES/Accoustics/Software/RT1050/PERSES_/sai_RT1050EVK/Debug --flash-dir C:/Users/JDM/mcuxpresso/01/.mcuxpressoide_packages_support/MIMXRT1052xxxxB_support/Flash --telnet 3331
Error message from debugger back end:
Remote communication error. Target disconnected.: Success.
Remote communication error. Target disconnected.: Success.

Debug information shown in MCUXpresso 10.2:

MCUXpresso IDE RedlinkMulti Driver v10.2 (May 10 2018 18:10:59 - crt_emu_cm_redlink build 510)
Found chip XML file in E:/Projects/PERSES/Accoustics/Software/RT1050/PERSES_/sai_RT1050EVK/Debug\MIMXRT1052xxxxB.xml
Reconnected to existing link server
Connecting to probe 1 core 0:0 (using server started externally) gave 'OK'
Probe Firmware: DAPLink CMSIS-DAP (ARM)
Serial Number: 0227000041114e45001e300ac2040039df91000097969900
VID:PID: 0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#9&121f15fd&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
probe 1 TAP 0:0 failed to read TAP ID - Nn(05). Wire ACK Fault in DAP access
connection failed - Nn(05). Wire ACK Fault in DAP access.. Retrying
probe 1 TAP 0:0 failed to read TAP ID - Nn(05). Wire ACK Fault in DAP access
Failed on connect: Nn(05). Wire ACK Fault in DAP access
No connection to chip's debug port

How to fix this issue to program the EVK?

FEEDBACK: erasing the Hyperflash memory solves this problem. The hyperflash can be erased using the 'GUI Flash toool' in MCUXpresso

Tags (1)
0 Kudos
2 Replies

1,084 Views
jens_demey
Contributor I

Yes, the problem is solved now.

However, the problem seems to return frequently but always can be solved by erasing the Hyperflash memory

0 Kudos

1,084 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

So, Is your problem solved now?

0 Kudos