Hello,
I tried upgrading the mbed firmware in my FRDM-K64F board to start debugging using OpenOCD, but it still does not work. Here is a screenshot of the errors that I get in console
I have also used the -f kinetis.cfg as mentioned in some other thread. I am now shifting to the Segger interface. But I would like to know if there is some way to use OpenOCD.
The Segger interface is working!! But is there any solution to use OpenOCD?
Hi
OpenOCD looks to need the CMSIS-DAP debugger installed - I don't know whether this works with KDS since usually the P&E one tends to be used.
Rowley Crossworks does use CMSIS-DAP for debugging and, when working with this IDE, I load the attached debugger instead. (Again not necessarily the latest version but has been used successfully).
Regards
Mark
Kinetis: µTasker Kinetis support
K64: µTasker Kinetis FRDM-K64F support / µTasker Kinetis TWR-K64F120M support
For the complete "out-of-the-box" Kinetis experience and faster time to market
Thank you Mark. I will try this and inform you about the results. Thanks for your help:smileyhappy:
Hi
The mbed boot loader doesn't allow debugging with KDS.
You need to use the P&E loader instead (which then doesn't support USB-MSD drag.and-drop loading).
I have attached a version that I have used for some time - there may be newer ones available on the P&E web size.
Regards
Mark
Kinetis: µTasker Kinetis support
K64: µTasker Kinetis FRDM-K64F support / µTasker Kinetis TWR-K64F120M support
For the complete "out-of-the-box" Kinetis experience and faster time to market
Hello Mark, the Segger interface is working. If you check in mcuoneclipse, Erich Styger's blog he has mentioned that to use OpenOCD on the OpenSDA v2 interface, it is necessary to upgrade the firmware to version 211. I am interested in using OpenOCD basically because it allows me to flash and debug other custom boards as well.
Ok I will try out Segger first and if it does not work then I will try your option.