Debug Build Error: This hardware might not support the default Visual Micro Debugger. If this project is using OTA/WiFi upload then please use the vMicro>Debugger menu to set the Serial COM and Remote port for the debugger. Otherwise switch the toolbar from 'Debug' to 'Release' and build again. or switch off Automatic Debugging or configure the SoftwareSerial debugger option.Debug build failed for project 'dsfafdsaafdsafsd'dsfafdsaafdsafsd.ino:8: In file included from void begin(Serial_ *theSerial) void begin(Serial_ *theSerial, unsigned long baud)

If you switch the board to "Arduino Zero (Native)" does the menu item appear?

Tim, where in the configuration path does the above setting trigger Microsoft GDB Debugger to turn on (enable)?

I am working on enabling GDB via a Segger J-LINK for a MKR1000 (initially), step 2 is an Adafruit M0. So far I have cloned the MKR1000 section from boards.txt (board code "mkr1000_jlink" for new config section Arduino/Genuino MKR1000 (w/ J-Link)). But as you suggest, the Microsoft GDB Debugger only appears when the target board is Arduino/Genuino Zero (Programming Port).

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...

There has been a lot of changes in the IDE's in relation to GDB. It will be re-done over the coming months.

In the meantime I am sorry that there is no support time available to help people with GDB .

I suggest looking for an alternative or use the serial debugger

Thanks

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.txtdebug.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.

There is some news. Visual Studio 2019 SP2 will break compatibility with VS2012 and VS2013. This forces us to either drop support for the older IDE's or create a 2nd slightly different version of Visual Micro to cater for both IDE types.

It has been VS2012 and VS2013 that has held back the ability for Visual Micro to integrate a simple and tightly integrated GDB solution.

Therefore, time allowing, over the next few months we should see some leaps in Visual Micro.

There is some news. Visual Studio 2019 SP2 will break compatibility with VS2012 and VS2013. This forces us to either drop support for the older IDE's or create a 2nd slightly different version of Visual Micro to cater for both IDE types.

It has been VS2012 and VS2013 that has held back the ability for Visual Micro to integrate a simple and tightly integrated GDB solution.

Therefore, time allowing, over the next few months we should see some leaps in Visual Micro.