[support]

Hi,

Indeed, as the overwhelming majority of devices targeted by our users are ARM-based, VisualGDB was only tested with IAR for ARM. That said, we will be happy to extend this to Renesas targets if you could run a few tests on your side.

Please try searching for IAR in the <VisualGDB Directory>\KnownToolchains.xml file. You will locate a ToolchainLoader element that specifies the exact registry key where VisualGDB searches for the IAR toolchain, and also the names of the compiler/linker and predefined include directories.

You can then copy the <ToolchainLoader> element into another instance and change its contents to match your Renesas toolchain. Then simply restart Visual Studio, or reopen Tools->VisualGDB->Manage VisualGDB Packages, and VisualGDB will detect the new compiler.

We can also do the necessary research and testing on our side, however as the Renesas devices are much more rarely used compared to ARM targets, we would have to charge a customization fee for it (the fee would be credited towards future VisualGDB license purchases).

[support]

This looks like a different popup from the one mentioned in the original thread. Either way, we have added a Tools->Options->Text Editor->C/C++(VisualGDB)->Other->Disable Quick Info setting that allows disabling generic Quick Info popups. Please try this build: VisualGDB-5.5.102.3872.msi

[support]

There are no special steps required on the VisualGDB side to handle included Makefiles. We would advise the following steps to get it working:

1. Make sure you can build the original Makefile outside VisualGDB by launching GNU Make manually as described here.
2. Restructure the Makefile according to your requirements and make sure it still builds. Please note that we are not able to provide any help on this step.
3. If the restructured Makefile works outside VisualGDB, but doesn’t work with VisualGDB, we can help you configure VisualGDB to replicate the stand-alone build results.

[support]

Please refer to our Makefile documentation. It explains this topic in detail.

[support]

Please note that we are not able to provide any help with learning the GNU Make syntax, or other low-level tools. Our support is strictly limited to issues in VisualGDB itself. If you prefer a solution that works out-of-the-box, please consider switching to MSBuild or CMake that are specifically designed to handle this better.

[support]

Thanks for your clarification. Indeed, due to a bug in VisualGDB, excluding a file from mbed-os itself would create a .mbedignore file in the root folder, rather than in the folder containing the excluded file.

We have fixed this behavior in the following build: VisualGDB-5.5.102.3871.msi

That said, we do not advise modifying the contents of the mbed repository itself, as any changes you make will be discarded next time you check out the repository. A better way to customize the mbed port would be to create a custom target as shown in this tutorial.

[support]

Thanks for the clarification. You can achieve the same effect with GNU Make by manually managing and including .mak files, however this will require learning advanced GNU Make syntax and the VisualGDB GUI will not show the settings added via custom .mak files, and these settings will not automatically affect IntelliSense (although they will be used for building).

Generally, we do not advise using GNU Make-based projects, as the newer MSBuild and CMake project types provide much better integration with the GUI and successfully address many shortcomings of GNU Make.

[support]

Hi,

Yes, please consider using MSBuild property sheets or Advanced CMake projects with multiple targets.

[support]

Thanks for your purchase! The latest VisualGDB 5.5 already contains a setting that allows fine-tuning the code suggestion tooltip behavior.

Please try setting Suggestion Tooltip Delay to a large value (e.g. 99999) to effectively disable them.

You can disable the refactoring during typing by setting the Max. change-driven tags option to 0.

You can find the exact up-to-date paths to both settings in the VisualGDB global setting reference that is automatically synchronized with the latest VisualGDB build.

 

[support]

Thanks for clarifying this. Target-specific building indeed only works for CMake-based projects using the ESP-IDF framework. ESP8266 projects do not use CMake and have a fewer number of options working out-of-the-box.

That said, you can easily configure VisualGDB to run the “make ota” command either directly after build, or in response to a custom command in Solution Explorer context menu. Simply try adding the “make ota” command (with the correct environment and working directory) to either VisualGDB Project Properties -> Custom Build Steps -> After Building, or VisualGDB Project Properties -> Custom Shortcuts, and you should be able to achieve the same effect.

[support]

Hi,

Normally, VisualGDB will try to use the .mbedignore file inside the project directory. If this is not the case, your project layout might be different from what VisualGDB normally expects.

Please try reproducing the problem on a clean project created from scratch (you don’t need to re-clone the shared mbed repository), and share the exact steps we could follow on our side to reproduce it, including full paths of all projects and files you used on your side.

[support]

Hi,

No problem. Please try dumping the build command used by VisualGDB in a .bat file as shown on this page. Then try running the build command manually and check if it produces the necessary files. If adding “ota” to the ninja arguments works, you can achieve the same effect by locating the “ota” target in Solution Explorer and building it via the “Build” command in the context menu.

[support]

Hi,

Unfortunately, we were not able to reproduce the problem based on the description you provided.

If VisualGDB behaves differently than you expect, please share the complete steps to reproduce the problem from scratch per our problem reporting guidelines and we will try to investigate this further.

[support]

Hi,

Please try selecting the file in Solution Explorer and pressing the Delete button (or selecting “Remove” from the context menu). Visual Studio will ask whether you want to remove the file from project, or physically delete it. Selecting “Remove” will automatically add the file to the .mbedignore file. Selecting “Delete” will physically delete it from the disk.

[support]

Hi,

Good to know you have found a workaround.

As the clang-format integration works very well in most scenarios, we no longer add new settings to the legacy formatting engine and advise using clang-format if you would like to tweak parameters that are not available in the legacy engine.

[Author]

Posts