Yes, tried version 9 as installed by Visual Micro.  Jlink firmware is the latest.  I didn't change any USB drivers for the reasons I said in my last post.  I can connect and control the jlink module using Jlink Commander and, in fact, can flash within Visual Micro using the command line version of it.  This means the jlink hardware and jlink usb driver are fine.   

The full attempt to connect to jlink by OpenOCD is below.  I am using the jlink.cfg that comes with OpenOCD and created the MK20Board.cfg and k20.cfg (which uses kx.cfg that comes with OpenOCD).

MK20Board.cfg (don't know if flash banks are properly defined but will fix that later, if req'd):

#
# MK20 Board

source [find target/k20.cfg]

$_TARGETNAME configure -event reset-init {
	puts "-event reset-init occured"
}

# Bank definition for the 'program flash' (instructions and/or data)
flash bank pflash.0 kinetis 0x00000000 0x40000 0 4 $_TARGETNAME
flash bank pflash.1 kinetis 0x00040000 0x40000 0 4 $_TARGETNAME
 

K20.cfg:

# Freescale Kinetis K20 devices

set CHIPNAME k20
source [find target/kx.cfg]
 

error results for command: openocd -f interface/jlink.cfg -f board/MK20Board.cfg 

C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\3vu3t
p0o.aov\Micro Platforms\default\tools\openocd-0.9.0\bin-x64>openocd -f interface
/jlink.cfg -f board/MK20Board.cfg
Open On-Chip Debugger 0.9.0 (2015-05-19-12:09)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use
'transport select <transport>'.
Info : add flash_bank kinetis k20.flash
adapter speed: 1000 kHz
none separate
cortex_m reset_config sysresetreq
Info : add flash_bank kinetis pflash.0
Info : add flash_bank kinetis pflash.1
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: Cannot find jlink Interface! Please check connection and permissions.
 

I had another thought...

JLink comes with it's own GBD server.  Can this be used instead and simplify all of this???  Segger JLink is a very popular programmer/debugger module and now with the EDU version it is very affordable at $29.95 (non-commercial use).

It seems Visual Micro should support it directly!

Hi,

Adding an arduino 3rd party programmer

For the programmer I would open arduno ide and find the "Upload using programmer" has an issue with your definition. Then it is okay to ask for help on the http://forum.arduino.cc where they have people who can help.

When you have that working I can easily help you tune it or make it more flexible but they know their own spec for programmers much better than I do.


j-Links owns GDB

I have a j-link but never had time to use it. If you can find the direct calls then we can certainly look at using it instead. You will see that you can configure in the visual micro gdb settings which programs it needs to run to launch a gdb session..

So in theory just specify the gdb.path or just hard code the entire .pattern to start with. This assumes no openOCD

debug.tool=gdb

tools.gdb.pre_init.tool=openocd

tools.gdb.cmd=[hardware tool chain gdb.exe]

tools.gdb.path={runtime.tools.[hardware tool chain path}/bin

tools.gdb.pattern="{path}/{cmd}" ­interpreter=mi ­d "{build.project_path}"

tools.gdb.openocd.cmd=bin/openocd.exe

tools.gdb.tcp=localhost:3333

I'm making progress and can now use OpenOCD to flash and restart my board.  I changed the JLink USB driver to winUSB and it now connects and works.  I created an OpenOCD script  based on a GitHub script I found which includes a program() and attach() procedure using SWD.  I found it here:
https://github.com/geomatsi/stm32-tests/tree/master/boards/stm32f103-mini/script...

It works to load my hex file and restart the MCU. It is hardcoded to the hex file path right now but this should be straightforward to pass in platform.txt (maybe... everything has been a battle thus far!).  I haven't tried the attach function at this point.

The script follows and is called to flash the device with this command:
    openocd -f setup_MK20.cfg -c "program ()"

# openocd setup for MK20

source [find interface/jlink.cfg]
transport select swd

source [find target/k20.cfg]

# write image and restart target
proc program () {
	init
	reset init
	halt
	flash write_image erase "C:\\Users\\Al Testani\\Documents\\Arduino\\Blink2\\Debug\\Blink2.hex"
	reset run
	shutdown
}

# reset target and attach to debug
proc attach () {
	init
	reset run
}
 

Where are the "runtime.vm." path values defined?  I am looking for the one that is the openocd BIN path, i.e. I  want the one that points to here (on my machine):

C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\3vu3tp0o.aov\Micro Platforms\default\tools\openocd-0.9.0

In "Arduino 3rd Party Hardware GDB Configuration Guide", the sample platform.txt uses:

.9.0

I can't find where {runtime.vm.ide.platforms.path} is pointing to. 

I need to know where the "real" openocd folder is as I want to add some cfg files to the scripts folder.

Thanks

Yes have done that countless times.  It doesn't expand the paths I am concerned with.   

I can hard code the paths and get it to work but it isn't clear how this will work on other computers I have.  That is why I am looking for the {} paths.

I *am* testing in the IDE and editing platform.txt.  I am looking for what {runtime.vm.ide.platforms.path} actually points to as it is not where I can find it and it doesn't point to where VM is installing openocd.  

This works if I hardcode the path to:
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\3vu3tp0o.aov\Micro Platforms\default\tools\openocd-0.9.0

but not with {runtime.vm.ide.platforms.path}

What I really want is what the equivalent {runtime.vm.xxx.xxx.path} is for the hardcoded path above.

My alternative is to install openocd at C:\openocd so I know for certain where it is and where my scripts are. 

I guess I am not making myself clear.  I think I know what it is and how it is a "shortcut" to an actual path. If this is incorrect, please let me know.

On my main development machine the Visual Micro extensions seems to be in:
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\3vu3tp0o.aov\...

In there, is the openocd folder where scripts (inc. mine) are stored and the executable lives

The 3vu3tp0o.aov folder is not present on my notebook so the equivalent folder is *somewhere* in the VS Extensions folder.  So, if I want all this to work on any machine where I do development, I want the path shortcut to be transportable and, obviously, hardcoding the path isn't.   

So the question is if I use pathtest1 = {runtime.vm.ide.platforms.path}, what is the REAL path that pathtest1 represents?

This does not work.

I even did a project "Clean" and Rebuild to see everything and only the one line in platform.txt where I put the pathtest1={} line shows up. I am attaching the build output so you can see for yourself.

I do see a couple of openocd paths but neither is the one in the VM extension folder.  I also see this line:

vm.platform.root.path=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\i5drq5bg.rqa\Micro Platforms\arduino16x

Backing up one level, there is a \default\tools\openocd path so possibly this is where the scripts are being search for.

The fact is that I still have no clue which openocd folder is being used and likely the reason I am having trouble and frustration.  I am going to put my own openocd folder at C:\openocd so I know definitively where it is.