Hi,

We provide out-of-the-box integration for mainstream devices with many active users, however this looks like a much more niche device with a smaller user base. Hence, we will not be supporting it directly unless some of our users agrees to directly cover the cost of integrating VisualGDB with it.

That said, VisualGDB is designed to be very flexible. If the device vendor provides a GCC-based toolchain, you can simply import it into VisualGDB by using the import link in the toolchain selector. Then, you can follow this tutorial to manually specify the compiler flags and locate the driver files necessary for that device. This way you can enjoy most of the VisualGDB functionality even if the device is not directly supported by us.

Thanks for clarifying this. If the toolchain is not based on GCC, you can simply create a custom Makefile for building your code and import it into VisualGDB as an externally built project. This way VisualGDB will simply invoke make with the specified arguments to build the project and won’t care that the underlying tools are not based on GCC. If the tools report error messages in a non-typical way, you can tweak VisualGDB to recognize them by editing %VISUALGDB_DIR%\Rules\RegularExpressions.xml.

On the debugging side, if the vendor provides a gdb executable for their platform, you can use VisualGDB to debug the code by overriding the gdb path via VisualGDB Project Properties. If they use a completely proprietary debugging protocol, we can still add support for it as a custom paid feature, but it would be a rather complex one.