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.
Thanks for trying. It worked in several cases on my side. Maybe indeed your device is permanently bricked.
Tried the script....no dice. But thanks for pointing me in that direction.
As the screenshot indicates:
"Resurrect locked Kinetis device": this feature exists for Kinetis devices only.
If you happen to have an LPC: try erasing the flash from the bootloader, or you might use a recover script like described here: https://mcuoneclipse.com/2023/07/25/linkserver-scripting-and-how-to-recover-mcus-with-a-script/
In mcuxpressoide-11.7.1_9221 there is no such thing as "Resurrect locked ..."
I have the same issue, do you find a solution?
@CBI Did you manage to find the solution for this? I am facing the same problem and tried the same solution but it is not working for me as well
Hi,
We are also having the same problem as CBI.
Is your problem resolved? If so please post it here.
Thank you very much.
The Problem has not been solved for me... I search a solution !!!
Hi all,
I am young in this forum
Meanwhile When I perform this
I have the following result
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
Worked for me as well. Thanks man!
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:
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!
I have the same problem.
How did you solve the problem in the end?
I have the same problem.
How did you solve the problem in the end?
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!
-----------------------------------------------------------------------------------------------------------------------
Thanks,
The issue has been resolved.:)
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
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!
-----------------------------------------------------------------------------------------------------------------------