I'm trying to follow the tutorial here but have some questions
https://www.visualmicro.com/post/2016/01/17/3rd-Party-Hardware-GDB-Configuration...

I modified my boards.txt and platform.txt for my board package. On compiling I get this error:
Quote:


This is a new project with empty setup() and loop() functions.

I have the GDB extension installed as well as the android tools. I don't have "Use GDB" as a menu option, what should I check?

It appears for the (Programming Port) variant.

My config file is located in: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\mh2uhnsb.yka\Micro Platforms\default\tools\openocd-0.9.0\scripts\board

My gdb client is located in C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\mh2uhnsb.yka\Micro Platforms\default\tools\arm-none-eabi-gcc\4.8.3-2014q1\bin

fx450_gdb.cfg:
Code:

source [find interface/cmsis-dap.cfg]
set CHIPNAME at91samd21g18
set ENDIAN little
source [find target/at91samdXX.cfg]
 

boards.txt:
Code:

ae_fx450_gdb.name=FX450 (GDB)
ae_fx450_gdb.vid.0=0x239A
ae_fx450_gdb.pid.0=0x800B
ae_fx450_gdb.vid.1=0x239C
ae_fx450_gdb.pid.1=0x000D
ae_fx450_gdb.upload.tool=openocd
ae_fx450_gdb.upload.protocol=sam-ba
ae_fx450_gdb.upload.maximum_size=262144
ae_fx450_gdb.upload.use_1200bps_touch=true
ae_fx450_gdb.upload.wait_for_upload_port=true
ae_fx450_gdb.upload.native_usb=true
ae_fx450_gdb.build.mcu=cortex-m0plus
ae_fx450_gdb.build.f_cpu=48000000L
ae_fx450_gdb.build.usb_product="FX450"
ae_fx450_gdb.build.board=FX450
ae_fx450_gdb.build.core=fx450
ae_fx450_gdb.build.extra_flags=-DARDUINO_SAMD_ZERO -D__SAMD21G18A__ -mthumb {build.usb_flags}
ae_fx450_gdb.build.ldscript=linker_scripts/gcc/flash_with_bootloader.ld
ae_fx450_gdb.build.openocdscript=board/fx450_gdb.cfg
ae_fx450_gdb.build.variant=fx450
ae_fx450_gdb.build.variant_system_lib=
ae_fx450_gdb.build.vid=0x239E
ae_fx450_gdb.build.pid=0x800E
ae_fx450_gdb.bootloader.tool=openocd
ae_fx450_gdb.bootloader.file=fx450/samd21_sam_ba.bin 

platforms.txt:
Code:

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={runtime.vm.ide.platforms.path}/default/tools/arm-none-eabi-gcc/4.8.3-2014q1
tools.gdb.pattern="{path}/{cmd}" ­interpreter=mi ­d "{build.project_path}"
tools.gdb.openocd.cmd=bin/openocd.exe
tools.gdb.tcp=localhost:3333
tools.gdb.openocd.path={runtime.vm.ide.platforms.path}/default/tools/openocd­0.9.0
tools.gdb.openocd.pattern="{path}/{cmd}" -s "{path}/scripts/" -f "{path}/scripts/{build.openocdscript}"
tools.gdb.openocd.params.verbose=­d2
tools.gdb.openocd.params.quiet=­d0

tools.gdb.tcp=localhost:3333
tools.gdb.openocd.path={runtime.vm.ide.platforms.path}/default/tools/openocd­0.9.0
tools.gdb.openocd.params.verbose=­d2
tools.gdb.openocd.params.quiet=­d0 

Bump!

Tim, is GDB a lower priority or unsupported? 

I understand, as a small organization, support resources being stretched and responses will not be immediate.  But I am seeing threads just end abruptly on this topic and in another thread your statement...

Visual Micro wrote on Sep 8^th, 2018 at 12:12pm:



The VM software-based debugging is not cutting it for our needs as we support our customers using our libraries. We have invested quite a few hours over the last several weeks getting openOCD functional with our Segger hardware and the target boards. We have used the VM burn bootloader functionality (via the J-Link) and the last hurdle is simply why VM won't recognize the settings as spelled out in your documentation to enable vMicro>>Debugging>>Microsoft GDB Debugger.

#board.txt or platform.txt
debug.tool=gdb


If there is no support for GDB with Visual Micro, I regrettably will have to migrate off of Visual Micro to another toolset, most likely Platform IO. Given that we have been using VM for two years and built processes around Visual Micro this is not something I am looking forward to but I can't wait months.

Sorry to be so direct,
Greg

Any news on this?

Visual Micro wrote on Jan 11^th, 2019 at 5:29pm:

Woooo!