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

[support]

Hi,

The recent version of VisualGDB would use the clang-format engine to format the code (including the comments). Clang-format could be tuned in numerous of ways by editing the .clang-format files (VisualGDB provides a graphical editor for them). Please see this page for an explanation how clang-format is integrated into VisualGDB and this page for an overview of clang-format options.

[support]

No problem. If the project has no custom steps, the problem is likely happening on the MSBuild level. Please try enabling diagnostic MSBuild logging as shown here, reproduce the problem and share the diagnostic build log from a clean operation that triggered the error.

[support]

Thanks for the screenshot. This is the new STM32CubeMX-based project that is split into the STM32Cube-controlled part (under the blue STM32CubeMX icon) and the VisualGDB-controlled part (outside the STM32CubeMX part).

It looks like you are trying to add files to the STM32CubeMX-controlled part that is not editable because it will be overwritten by STM32CubeMX once the project is regenerated.

Please try adding files outside the STM32CubeMX Files node. See this tutorial for a detailed introduction in the new STM32CubeMX-based workflow.

• This reply was modified 4 years, 9 months ago by support.

[support]

No problem, we will clarify. You can use any version that was released within the “free update” year for free. In your example, you will be able to use the “VisualGDB-5.5.2.2222.msi” version (released just before the year was up) forever.

That said, VisualGDB always shows the update link to the latest available version, not the latest version compatible with the current license key. If you try activating that version with a key that is not compatible (i.e. had the “free update” year expired before the release date), it will direct you to the https://sysprogs.com/splm/mykey page where you can either renew your key, or download the latest version that works with it.

Update: We usually do not enforce expiry limits on early preview builds (e.g. VisualGDB 5.5 Preview X). I.e. they will often successfully activate even if the renewal period was already expired at the time of release. Once we switch from a Preview build to a stable build (5.5RCx or 5.5Ry), we start enforcing the expiry limits again, so updating from Preview X to a stable build may require renewing the license.

Hope this explains. Let us know if you have any further questions.

[support]

Hi,

Sorry, this looks like an issue with a specific board, or specific computer. Please try different a different computer or a different CYUSB3KIT-003 board.

[support]

Hi,

This should normally work. If not, please try attaching the screenshots showing what exactly you are trying to do and we will try to point out the possible cause of the problem.

[Author]

Posts