AnsweredAssumed Answered

Brand-new FRDM-K64F board not working

Question asked by Pol Welter on Nov 6, 2019
Latest reply on Nov 9, 2019 by Pol Welter

I just got a FRDM-K64F board.

 

I closely followed the Getting Started Guide (Get Started with the FRDM-K64F | NXP ).

 

I connected the PC to the debug adapter USB port. The device should have come flashed with a demo that should flash the RGB LED according to readings from the on-board accelerometer, but nothing happened.

 

Next I installed the development tools, and, again following the guide, tried the Hello World example. The example compiled fine, and the IDE could talk to the on-board debug adapter, but it failed to communicate with the target chip. The messages from the debugger can be found below.

 

I am on Windows 10. I am using the latest version of the SDK and MCUXpresso toolchain and IDE.

 

Please advise.

 

Many thanks & best regards

Pol

MCUXpresso IDE RedlinkMulti Driver v11.0 (Aug 27 2019 16:46:33 - crt_emu_cm_redlink build 22)
Found part description in XML file MK64F12_internal.xml
Reconnected to existing LinkServer process.
============= SCRIPT: kinetisconnect.scp =============
Kinetis Connect Script
Connecting to Probe Index = 1
This probe = 1
This TAP = 0
This core = 0
DpID = 2BA01477
Assert NRESET
Reset pin state: 00
Power up Debug
MDM-AP APID: 0x001C0000
MDM-AP System Reset/Hold Reset/Debug Request
MDM-AP Control: 0x00000000
MDM-AP Status (Flash Ready) : 0x00000037
Part is secured
Mass Erase Required
============= END SCRIPT =============================
Probe Firmware: MBED CMSIS-DAP (MBED)
Serial Number:  024002015CBA7E63A14483DB
VID:PID:  0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#8&10093261&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
Using memory from core 0 after searching for a good core
Using memory from core 0 after searching for a good core
connection failed - Nn(05). Wire ACK Fault in DAP access.. Retrying
Using memory from core 0 after searching for a good core
Using memory from core 0 after searching for a good core
Using memory from core 0 after searching for a good core
Failed on connect: Nn(05). Wire ACK Fault in DAP access
Connected&Reset. Was: NotConnected. DpID: 2BA01477. 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.
error closing down debug session - Nn(05). Wire ACK Fault in DAP access

Outcomes