Hello @emfact,
Could you please try the following suggestions? 1. Please double check that you stop previous debugging session instance before trying to run a new one. 2. Delete the .launch of the project and try to debug again. 3. Try out another example like a Hello World to see if the problem continues.
If the problem persists, could you please share your project?
Best regards, Raul.
Dear
I had tried all 3 options you have mentioned but no luck.
Following GDB protocol problem is seen in console .
I am sharing console details
Flash Write Done
Flash Program Summary: 22824 bytes in 0.06 seconds (348.27 KB/sec)
Starting execution using system reset and halt target with a stall address
Retask read watchpoint 1 at 0x50000040 to use for boot ROM stall
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
Warning - processor did not halt - gave up waiting
flash - system reset failed - Ep(04). Cannot halt processor.
Target error from Commit Flash write: Ep(04). Cannot halt processor.
GDB stub (C:\nxp\MCUXpressoIDE_11.6.1_8255\ide\plugins\com.nxp.mcuxpresso.tools.bin.win32_11.6.1.202210030617\binaries\crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
Hello @emfact,
Could you please tell us what board are you using? Is it a custom board or is it a NXP development board?
At the meantime, could you please try performing a mass erase to the flash memory using the GUI Flash Tool before debugging?
Finally, could you try updating the firmware of the MCU-Link Pro? For this, please refer to the following links: Getting Started with the MCU-Link Pro and MCU-Link Pro User Manual.
Best regards, Raul.