AnsweredAssumed Answered

OpenOCD - to use or not to use it?

Question asked by piotrek on Nov 26, 2014
Latest reply on Apr 9, 2015 by Pratiek Bhadranavar

With KDS 2.0.0 and FRDM K64F board I've tried to use OpenOCD Debugging with no much of a success  The result is:

 

Open On-Chip Debugger 0.8.0-dev (2014-10-31-11:10)

Licensed under GNU GPL v2

For bug reports, read

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

Info : only one transport option; autoselect 'cmsis-dap'

Error: unable to open CMSIS-DAP device

Error: unable to init CMSIS-DAP driver

Error: Error selecting 'cmsis-dap' as transport

Runtime Error: D:/Freescale/KDS_2.0.0/openocd/bin/..//scripts/kinetis.cfg:3:

in procedure 'script'

at file "embedded:startup.tcl", line 58

in procedure 'interface' called at file "D:/Freescale/KDS_2.0.0/openocd/bin/..//scripts/kinetis.cfg", line 3


Sometimes followed by:


Quit (expect signal SIGINT when the program is resumed)


Is there something fundamentally wrong with OpenOCD and FRDM K64F board and the OpenOCD debugging should not be used?

Or am I doing something wrong?


Outcomes