MK64F512x chip could not be programmed.

chhsu0229 — Thu, 02 Dec 2021 07:12:06 GMT

I am working on MK64F512x chip. However, it could not be re-programmed and connected again.How can I fix this untinted behavior?

The following shows the debug message from J-Link tool.

- Executing default behavior previously saved in the registry.
- Device will be unsecured now.
- Timeout while unsecuring device. Erase never starts.
- Found SW-DP with ID 0x2BA01477
- DPIDR: 0x2BA01477
- Scanning AP map to find all available APs
- AP[2]: Stopped AP scan as end of AP map has been reached
- AP[0]: AHB-AP (IDR: 0x24770011)
- AP[1]: JTAG-AP (IDR: 0x001C0000)
- Iterating through AP map to find AHB-AP to use
- AP[0]: Skipped. Could not read CPUID register
- AP[1]: Skipped. Not an AHB-AP
- ERROR: Could not find core in Coresight setup
code -1
- ERROR: Failed to connect.
Could not establish a connection to target.

Re: MK64F512x chip could not be programmed.

Robin_Shen — Fri, 03 Dec 2021 09:20:52 GMT

Please refer the answer in Communication error while accessing MDM-AP.

Hope it helps.

Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

topic MK64F512x chip could not be programmed. in Kinetis Microcontrollers

MK64F512x chip could not be programmed.

Re: MK64F512x chip could not be programmed.