Wire ACK Fault in DAP access

cancel
Showing results for 
Search instead for 
Did you mean: 

Wire ACK Fault in DAP access

3,135 Views
saad_saeed
Contributor III

Hello,

I have just recently installed McuExpresso 10.3.0. Previously I was using McuExpresso 10.0.2. When I downloaded the latest SDK for FRDM K64 and tried to debug a demo example, I got this error.

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

I dont understand what is wrong. Kindly, help me with this.

Thanks,

Saad.

Tags (2)
0 Kudos
10 Replies

2,144 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

Hi Saad,

First, we need identify this issue is only on one project or a common issue for all project.

- please create a NEW project in a NEW workspace, see how the connection works.

- please test your project in a NEW workspace, how does it work?

If both of above can't fix the issue, I suggest you update your K64 firmware.

OpenSDA Serial and Debug Adapter|NXP 


Have a great day,
Jun Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

2,144 Views
saad_saeed
Contributor III

Hello,

I have done what you said to me.

Now I am getting the following error

15: Target error from Commit Flash write
15: Target error from Commit Flash write
Cannot halt processor.
Debugging context: frdmk64f_lwip_tcpecho_bm Debug

0 Kudos

2,144 Views
saad_saeed
Contributor III

Thanks,

The issue has been resolved.:)

0 Kudos

2,144 Views
bjemt
Contributor III

I have the same problem

  • How did you solve the problem in the end?

0 Kudos

2,144 Views
bjemt
Contributor III

I found the problem was that the MCP was locked, It's a simple way of unlocking a MCU in MCUXpresso that I thought I'd share with other novices so they can get going again easily:

 

Unlock Kinetis MCU!!.png

 

Step 1: Open the GUI Flash tool

Step 2: Choose Resurrect locked...

Step 3: Hit Run.

 

In a moment the MCU will be unlocked and ready for more programming action!

2,097 Views
Guntash
Contributor I

Worked for me as well. Thanks man!

0 Kudos

2,144 Views
bjemt
Contributor III

I have the same problem

  • How did you solve the problem in the end?

0 Kudos

2,144 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

Good to know it. You are welcome!


Have a great day,
Jun Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

1,364 Views
CBI
Contributor I

The Problem has not been solved for me... I search a solution !!!

0 Kudos

1,370 Views
CBI
Contributor I

Hi all, 

I am young in this forum
Meanwhile When I perform this 

CBI_0-1614612775982.png

 

I have the following result

CBI_1-1614612812733.png

 

The detail infos in the console:

Executing flash operation 'Resurrect locked Kinetis device' (Resurrect locked Kinetis device) - Mon Mar 01 16:30:41 CET 2021
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.3 (Jan 11 2021 16:41:13 - crt_emu_cm_redlink.exe build 9)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in C:/Users/binard/Documents/MCUXpressoIDE_11.3.0_5222/workspace/frdmkw38_heart_rate_sensor_freertos/Debug\MKW38A512xxx4.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
Connecting to probe 1 core 0 (using server started externally) reports:
'Ee(42). Could not connect to core.'
Retrying...
Reconnected to existing LinkServer process.
Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
============= SCRIPT: kinetismasserase.scp =============
Kinetis Mass Erase Script
Error: Wire Ack Fault - target connected?
Assert NRESET
Reset pin state: 00
Error: Wire not connected
Power up Debug
Error: Wire not connected
Error: Wire not connected
No Debug Power
============= END SCRIPT ===============================
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

0 Kudos