Failed on connect: Nn(05). Wire ACK Fault in DAP access.

[want2be]

Hi everyone.

I have a problem with flashing my LPCXpresso 1347, it's suddenly stopped working. I've got a "Wire ACK Fault in DAP access" error. 

Console log:

Executing flash operation 'Program' (Program file into flash: test.axf) - Thu Nov 08 16:19:20 CET 2018
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v10.2 (Jul 25 2018 11:25:37 - crt_emu_cm_redlink.exe build 555)
( 0) Reading remote configuration
Wc(03). No cache support.
( 5) Remote configuration complete
Reconnected to existing link server
Connecting to probe 2 core 0:0 (using server started externally) gave 'OK'
Probe Firmware: LPC-Link Probe v1.3 (NXP - LPC-Link)
Serial Number: WIN64HS12
VID:PID: 1FC9:0009
USB Path:
connection failed - Nn(05). Wire ACK Fault in DAP access.. Retrying
Failed on connect: Em(19). Communications with DAP fails - is probe connected to a target?
Connected&Reset. Was: NotConnected. DpID: 00000000. 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

How can I fix it?

Ragards

[luca_nazzaro]

I have the same problem, pls help.

[lephan]

I have the same problem when changing the RAM layout (increase SRAM DCT and decrease SRAM OC).

I revert the RAM layout to the original setting but still could not flash or debug.

What should I do now?

[lephan]

I found the solution to overcome the issue:

- change the boot Device from Hyper Flash to QSPI Flash and use MCUXpresso IDE to debug (SW could run something, I don't know what it is )

- revert boot Device to Hyper Flash again and now I could flash and debug my code

[ianbenton]

The clue is in the 16th line! "is probe connected to a target?" 

It is most likely a hardware fault. The link is *really* susceptible to interference. Did you connect your 'scope to the 0V supply? is there a switched-mode supply nearby? 

I found that buffering SWCLK made it a lot less so. 

If you are working in an electrically noisy environment, wrap SWCLK/SWDIO/0V around a ferrite toroid, and the same with the USB lead going into the computer.

[derickbengyuh]

I have this same issue on my imxrt1050. My suspicion is that i had flashed a code which configured some jtag pins to be used as gpio. 

After flashing the application i could debug. But upon restet / reflash i got thesame error. I think a workaround would be to use either a hyperflash / QSPI to flash a different code, that would have to erase the faulty code and reconfigure the JTAG ports as default. I expected the Firmware (Bootloader) or the HyperFlash / QSPI to do that. Unfortunately after updating / reinstalling them using the information here 

OpenSDA Serial and Debug Adapter | NXP 

i still could not flash or debug. 

This is the error i get from MCUExpresso 

Unable to connect wire for probe index 1.
Error: Wire Ack Fault - target connected?

Unable to connect wire for probe index 1.
Error: Wire Ack Fault - target connected?

  Error: Wire Ack Fault - target connected?
 
   at com.nxp.mcuxpresso.core.debug.support.linkserver.redlink.client.RedlinkServerClient.checkServerReply(RedlinkServerClient.java:214)
   at com.nxp.mcuxpresso.core.debug.support.linkserver.redlink.client.RedlinkServerClient.wireConnect(RedlinkServerClient.java:1155)
   at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.jtag.AbstractJtagDiscovery.ideConnect(AbstractJtagDiscovery.java:207)
   at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.jtag.AbstractJtagDiscovery.connect(AbstractJtagDiscovery.java:187)
   at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.jtag.AbstractJtagDiscovery.discover(AbstractJtagDiscovery.java:146)
   at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.TargetDiscovery.jtagDiscovery(TargetDiscovery.java:457)
   at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.getEmulatorInfo(LaunchScriptUtils.java:248)
   at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.init(LaunchScriptUtils.java:488)
   at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.<init>(LaunchScriptUtils.java:156)
   at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.<init>(LaunchScriptUtils.java:143)
   at com.nxp.mcuxpresso.core.debug.support.linkserver.services.TargetDiscoveryService.getTargetDiscovery(TargetDiscoveryService.java:138)
   at com.nxp.mcuxpresso.core.debug.support.linkserver.override.LSFinalLaunchSequence$TargetDiscoveryJob.run(LSFinalLaunchSequence.java:110)
   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

I still havent found any solution after googling. I only found similar questions. I think Nxp really have to take a look at this. 

BR

Derick