Target error from Commit Flash write: Ep(04).

[yudeshui]

我的板子型号是MIMXRT685-EVK，我下载的SDK是SDK_2_16_000_EVK-MIMXRT685.zip。

步骤：build -> debug

提示如下：

MCUXpresso IDE RedlinkMulti Driver v11.10 (Jul 2 2024 19:33:51 - crt_emu_cm_redlink build 741)

Found chip XML file in C:/Users/carson.yu/Documents/MCUXpressoIDE_11.10.0_3148/workspace/evkmimxrt685_sctimer_pwm_with_dutycyle_change/Debug\MIMXRT685S.xml

Reconnected to existing LinkServer process.

Probe Firmware: LPC-LINK2 CMSIS-DAP V5.460 (NXP Semiconductors)

Serial Number: DSA3CQMQ

VID:PID: 1FC9:0090

USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#8&773e416&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

Using memory from core 0 after searching for a good core

processor is in secure mode

debug interface type = CoreSight DP (DAP DP ID 6BA02477) over SWD TAP 0

processor type = Cortex-M33 (CPU ID 00000D21) on DAP AP 0

number of h/w breakpoints = 8

number of flash patches = 0

number of h/w watchpoints = 4

Probe(0): Connected&Reset. DpID: 6BA02477. CpuID: 00000D21. Info: <None>

Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.

Content of CoreSight Debug ROM(s):

RBASE E00FE000: CID B105100D PID 0000095000 ROM (type 0x1)

ROM 1 E00FF000: CID B105100D PID 04000BB4C9 ROM (type 0x1)

ROM 2 E000E000: CID B105900D PID 04000BBD21 CSt ARM ARMv8-M type 0x0 Misc - Undefined

ROM 2 E0001000: CID B105900D PID 04000BBD21 CSt ARM DWTv2 type 0x0 Misc - Undefined

ROM 2 E0002000: CID B105900D PID 04000BBD21 CSt ARM FPBv2 type 0x0 Misc - Undefined

ROM 2 E0000000: CID B105900D PID 04000BBD21 CSt ARM ITMv2 type 0x43 Trace Source - Bus

ROM 2 E0041000: CID B105900D PID 04002BBD21 CSt ARM ETMv4.0 type 0x13 Trace Source - Core

ROM 2 E0042000: CID B105900D PID 04000BBD21 CSt ARM CTIv2 type 0x14 Debug Control - Trigger, e.g. ECT

ROM 1 E0040000: CID B105900D PID 04000BBD21 CSt type 0x11 Trace Sink - TPIU

NXP: MIMXRT685S

DAP stride is 1024 bytes (256 words)

Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT600_FlexSPI_B_MXIC_OPI.cfx

Image 'MIMXRT600_FlexSPI_B_MXIC_OPI Jul 2 2024 18:29:23'

Opening flash driver MIMXRT600_FlexSPI_B_MXIC_OPI.cfx

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)

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 35604 bytes to address 0x08000000 in Flash

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

Erased/Wrote sector 0-0 with 35604 bytes in 41msec

Closing flash driver MIMXRT600_FlexSPI_B_MXIC_OPI.cfx

Flash Write Done

Flash Program Summary: 35604 bytes in 0.04 seconds (848.04 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 (D:\nxp\LinkServer_1.6.133\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

执行过 mass erase, 没什么用，跪求助跪求指教

[Gavin_Jia · Accepted solution]

Hi @yudeshui ，

Thanks for your interest in NXP MIMXRT series!

From the log you provided, it seems that the DAP firmware of the on-board debugger is being used. It's possible that this is due to an issue with the onboard debugger firmware, I suggest you try updating the onboard debugger to the JLink firmware first.

You need to install this software first: LinkServer for Microcontrollers | NXP Semiconductors

Then：

1. power down the board.Install the JP1 jumper cap;
2. Run the following script: program_JLINK.cmd      at this path: C:\nxp\LinkServer_1.6.133\LPCScrypt\scripts
3. Power down; remove the JP1 jumper cap; power back up;

Best regards,
Gavin