Similar issue to AustinLindquist on his post.
Following the guidance provided on VisualMicro.com website for adding GDB 3rd party support, I have been attempting to create a GDB configuration for a Segger J-Link and an Arduino MKR1000. While I have successfully integrated the J-Link\MKR1000 with OpenOCD, I have not been able to get Microsoft GDB Debugger to appear with any “custom” board.txt, boards.txt or platforms.txt configuration change. So far the only way I have got the Microsoft GDB Debugger to appear is by selecting Arduino/Genuino Zero (Programming Port).
Created a new board script (mkr1000-jlink.cfg) for OpenOCD at C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\MH2UHNSB.YKA\Micro Platforms\default\tools\openocd-0.9.0\scripts\board.
Create a new boards.txt section (section separated as boards.mkr1000-jlink.append.txt)
Appended the following to the platforms.txt file.
# Platform external debugging
# --------------------
debug.tool=gdb
tools.gdb.pre_init.tool=openocd
tools.gdb.cmd=bin/arm-none-eabi-gdb
tools.gdb.cmd.windows=bin/arm-none-eabi-gdb.exe
tools.gdb.path= C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Linux\gcc_arm\bin
tools.gdb.pattern="{path}/{cmd}" -interpreter=mi -d {build.project_path}
tools.gdb.tcp=localhost:3333
tools.gdb.openocd.cmd=bin/openocd.exe
.0
tools.gdb.openocd.params.verbose=-d2
tools.gdb.openocd.params.quiet=-d0
tools.gdb.openocd.pattern="{path}/{cmd}" -s "{path}/scripts/" -f "{path}/scripts/{build.openocdscript}"
#-f "{runtime.platform.path}/variants/{build.variant}/{build.openocdscript}" -c "telnet_port disabled; program {{{build.path}/{build.project_name}.bin}} verify reset 0x00002000; shutdown"
Does not appear to turn on the Microsoft GDB Debugger tool.
1. 3rd party hardware GDB guide - .
https://www.visualmicro.com/post/2016/01/17/3rd-Party-Hardware-GDB-Configuration...;
So I have tried…
2. Option 1 (boards.txt) from link above
3. Option 2 (platform.txt) from link above
4. Adding board.txt to project (as described in link above).
None of these 3 approaches, as attempted, turn on the Microsoft GDB Debugger under vMicro > Debugger. If the Microsoft GDB Debugger is not “turned on”, how can one attempt to create a configuration for GDB debugging?
VM Team your support on this would be very much appreciated.
Greg