8 years, 9 months ago.

Strange behavior using FRDM-KL25Z on Coocox with CMSIS-DAP

Hey there,

i encountered a strange problem with Coocox using it for the FRDM-KL25Z. The FRDM-KL25Z board is setup with the latest CMSIS_DAP driver and Coocox is also setup accordingly. For testing I run the mbed_blinky example which just blinks the LED on the board. I am using Coocox Version: 2.0.3, Build id: 20150527-2.0.3 on Windows 7 (64 bit).

When I compile and debug the program, Coocox writes the program to the flash of the FRDM-KL25Z, but then, instead of running the debugger, instantly stops the debugger and returns in the editing mode. (The program is on the bord and executes without problem.)

What I get on the debug consol is this:

<terminated> mbed_blinky.configuration [Cortex-M Application] C:\Program Files (x86)\GNU Tools ARM Embedded\5.2 2015q4\bin\arm-none-eabi-gdb (20.03.16 18;54)
Reading symbols from C:\Users\Michael Kraft\Documents\Coocox Projects\mbed_blinky\mbed_blinky\Debug\bin\mbed_blinky.elf...done.
file "C:/Users/Michael Kraft/Documents/Coocox Projects/mbed_blinky/mbed_blinky/Debug/bin/mbed_blinky.elf"
Reading symbols from C:/Users/Michael Kraft/Documents/Coocox Projects/mbed_blinky/mbed_blinky/Debug/bin/mbed_blinky.elf...done.

I played around but couldn't get the debugger going. At a certain point I switched the debugger to ST-Link, instead CMSIS-DAP, to provoke an error and see the resulting output - INSTEAD IT STARTED DEBUGGING!!!

How this works is far beyond my understanding. Well, it works, but the debugger cannot see the SRAM_L of the KL25Z, while the SRAM_U and the flash are correctly displayed.

Can please someone shed a light on this mess and help me to get the debugger to work correctly? Thanks for any suggestions!