MCUXpresso IDE and FDRM-K64F programming issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MCUXpresso IDE and FDRM-K64F programming issue

1,174 Views
atfarsoni
Contributor I

I've just started using the FRDM-K64F board and encountered several issues:

1- When for the first time the board is connected to the USB port of my PC, the pre-loaded (Bubble) app does not work as expected. 

2- With the board powered by the USB port, my PC opens a directory MBED (E:\) with several empty files.

3- With all software installed, I tried to program the board using SDK examples, at the end of programming (Debug), I get a connection error. Attached is the debug log console.

Below was also copied from the Console window:

============= END SCRIPT =============================
Probe Firmware: MBED CMSIS-DAP (MBED)
Serial Number: 0240020163867E7C9E7883C4
VID:PID: 0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#8&160b5c6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
connection failed - Nn(05). Wire ACK Fault in DAP access.. Retrying
Failed on connect: Nn(05). Wire ACK Fault in DAP access
Connected&Reset. Was: NotConnected. DpID: 00000000. CpuID: 00000000. Info: <None>
Last stub error 0: OK
Last sticky error: 0x0 AIndex: 0
Debug bus selected: MemAp 0
DAP Speed test unexecuted or failed
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
(100) Target Connection Failed
error closing down debug session - Ee(FF). Redlink interface error 255.

I appreciate any help.

Thanks! 

0 Kudos
4 Replies

615 Views
lpcxpresso_supp
NXP Employee
NXP Employee

The console logs I'd like to see can be copied from the MCUXpresso IDE console tab. One console is for gdb-traces. The other is the debug log. See The Debug Log. Please copy these and paste as a response, or, add as an attachment.

Thanks and regards,

MCUXpresso Support

EDIT: If you're a Windows 10 user, there have been reports of the OpenSDA v2.1 becoming corrupted. See OpenSDA Serial and Debug Adapter|NXP.

0 Kudos

615 Views
lpcxpresso_supp
NXP Employee
NXP Employee

You don’t have a viable debug connection. Please post the entire debug console log which captures the output from the script execution. You may need to use the mass erase script.

Thanks and regards,

MCUXpresso Support

0 Kudos

615 Views
atfarsoni
Contributor I

The entire debug console log is attached. I also noticed that the board works fine with PCs running on Window 7. Only PCs with Windows 10 have these issues.

Thanks!

0 Kudos

615 Views
lpcxpresso_supp
NXP Employee
NXP Employee

Thanks, we'll let you know what we find.

MCUXpresso Support

0 Kudos