"Target error from Commit Flash Write" error when debugging the project on MIMXRT685

[JimHuang_1]

When I try to debug the project on MIMXRT685, I got the Wire ACK Fault in DAP access within the error from the title. Can someone suggest their already working solution?
MCUXpresso IDE verison :v11.6.1

[TwoHorseFeng]

Hi Kerryzhou,

When I try to debug the example of hello world on MIMXRT685-AUD-EVK, I also have the same issue. The error debug message is "Wire ACK Fault in DAP access" from debug message of the MCUXpresso IDE tool. My MIMXRT685-AUD-EVK are brand new. Is it hardware issue? Could you suggest us the working solution?

Flash variant 'JEDEC_FlexSPI_Device' detected (64MB = 1024*64K at 0x8000000)

Closing flash driver MIMXRT600_FlexSPI_B_MXIC_OPI.cfx

Connected: was_reset=true. was_stopped=false

Awaiting telnet connection to port 3330 ...

GDB nonstop mode enabled

Opening flash driver MIMXRT600_FlexSPI_B_MXIC_OPI.cfx (already resident)

VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.

Using SOFT reset to run the flash driver

Flash variant 'JEDEC_FlexSPI_Device' detected (64MB = 1024*64K at 0x8000000)

Writing 26732 bytes to address 0x08000000 in Flash

08004000 done 61% (16384 out of 26732)

08008000 done 100% (32768 out of 26732)

Sectors written: 1, unchanged: 0, total: 1

Erased/Wrote sector 0-0 with 26732 bytes in 642msec

Closing flash driver MIMXRT600_FlexSPI_B_MXIC_OPI.cfx

Flash Write Done

Flash Program Summary: 26732 bytes in 0.64 seconds (40.66 KB/sec)

Starting execution using system reset and halt target with a stall address

Retask read watchpoint 1 at 0x50002034 to use for boot ROM stall

processor is in non-secure mode

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.8.1_1197\ide\plugins\com.nxp.mcuxpresso.tools.bin.win32_11.8.1.202310241620\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

Thanks

HY

[kerryzhou · Accepted solution]

Hi @JimHuang_1 ,

   Your issues is mainly caused by the invlalid code downloaded to the board flash, then the RT685 meet the boot issues, it will also cause the debugger connection issues.

   Normally, to this issue, we can resolved it by do the external flash masserase.

  You can let your board enter the ISP mode, then use the debugger do the mass erase, or use the tools like the MCUBootutiltiy or the SPT tool do the mass erase.

   Please try it on your side.

If you still have questions about it, please kindly let me know.

Best Regards,

Kerry

[JimHuang_1]

Hi Kerryzhou

I try to enter ISP mode set ISP[0-2](HIGH、HIGH 、LOW)，and do chip erase down with MCUBootUtility tool.
and then retry debugger project on MIMXRT685-evk.have the same issue.
Is there any setting error?

Best Regards

Jim

[kerryzhou]

Hi @JimHuang_1 ,

  What's the board you are using? Custom board or the NXP EVK?

  If it is the custom board, you need to check your external flash, it may also related to the flashloader unmatch to your board.

  Or you can test the RAM code, I mean, set the code to the internal RAM,then use debugger to test it, whether you can enter the debug mode or not? At least, this will help you to check the debugger interface have issues or not, it may related to the hardware now.

Best Regards,

Kerry

[JimHuang_1]

Hi Kerryzhou

I use MIMXRT685-EVK.I will check my hardware thanks.

[kerryzhou]

Hi @JimHuang_1 ,

  OK, any updated information after your checking, just kindly let me know.

Best Regards,

Kerry

[JimHuang_1]

Hi Kerryzhou

Can compile after repairing the board.

Thanks.