AnsweredAssumed Answered

K60FX512 FT2232 and Linux KDS3.0 debug

Question asked by Nikolay Kulikov on Jul 15, 2015

I have a debugger made on the FT2232 and the device microcontroller K60FX512. I create an empty project with OpenOCD debug session.

Trying to start debugging on Linux KDS3.0 ends error messages. The system is also set OpenOCD 0.8.0. If you specify in the settings of the external debug OpenOCD specifying configuration files for K60 and FT2232 also ends error messages. From the command line and KDS 2.0 K60 is programmed properly. How to configure Linux KDS 3.0 to debug guaranteed to work?
https://community.freescale.com/message/516578#516578 - the answer is not helpful.

openocd log:

Open On-Chip Debugger 0.8.0-dev (2015-01-09-16:23)

Licensed under GNU GPL v2

For bug reports, read

    http://openocd.sourceforge.net/doc/doxygen/bugs.html

Info : only one transport option; autoselect 'jtag'

srst_only separate srst_gates_jtag srst_push_pull connect_deassert_srst

adapter speed: 1000 kHz

Info : add flash_bank kinetis k60.flash

cortex_m reset_config sysresetreq

Info : add flash_bank kinetis pflash.0

Info : add flash_bank kinetis pflash.1

Info : add flash_bank kinetis pflash.2

Info : add flash_bank kinetis pflash.3

Started by GNU ARM Eclipse

Info : clock speed 1000 kHz

Info : JTAG tap: k60.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)

Info : k60.cpu: hardware has 6 breakpoints, 4 watchpoints

Info : accepting 'gdb' connection from 3333

Warn : acknowledgment received, but no packet pending

undefined debug reason 7 - target needs reset

Info : JTAG tap: k60.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)

target state: halted

target halted due to debug-request, current mode: Thread

xPSR: 0x01000000 pc: 0x0000069c msp: 0x20000000

semihosting is enabled

Warn : No RTOS could be auto-detected!

Warn : No RTOS could be auto-detected!

Error: JTAG-DP STICKY ERROR

Error: MEM_AP_CSW 0x23000062, MEM_AP_TAR 0x4

Error: Failed to write memory at 0x00000004

Error: JTAG-DP STICKY ERROR

Error: MEM_AP_CSW 0x23000062, MEM_AP_TAR 0x404

Error: Failed to write memory at 0x00000404

Info : dropped 'gdb' connection

In the attached file is writed firmware. Secure chip is disable. Erase and retry program does not end with success

Original Attachment has been moved to: temp.bin.zip

Outcomes