[support]

Hi,

OK, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.4.820.msi

Then open the Clang IntelliSense Console window via the View menu and look for a line like this:

Indentation size: 4, will insert spaces

Does it match your settings? Are tabs still inserted instead of spaces?

 

[support]

Hi,

Most likely when you stop at a breakpoint your PC is still sending some requests to the board and once it times out (as it is stopped in the debugger), the PC assumes it has disconnected. Can you confirm that it does not disappear when you don’t set any breakpoints?

[support]

Hi,

Yes, please go to the Debug Settings page of VisualGDB Project Properties, uncheck the “Specify automatically based on project settings” flag and select the “MK64FN1M0xxx12” value from the list.

[support]

Hi,

Sorry for the confusion. We are gradually updating our tutorials to reflect the newer HAL API (e.g. see the new timers tutorial), but we did not update the PWM one yet.

[support]

Hi,

If you are never intending to deploy or debug the project with VisualGDB, you can select any arbitrary SSH connection in the wizard as it won’t be used anyway. Let us know if this works.

[support]

Hi,

This setting is normally cached, so sometimes it’s not updated immediately. Please try reopening the source file or restarting Visual Studio after changing it.

[support]

Hi,

Thanks, the build type was indeed ignored. We have fixed this in the development tree. If this is critical to you, we can share a daily build with the fix.

We will add an option to delete the remote files corresponding to recently deleted local files in v5.2.

You can specify explicit subdirectories by selecting “Include selected subdirectories only” and then unchecking the .git directory explicitly.

[support]

Hi,

We have actually added it to v5.1 some time ago. Please ensure you are using the latest version. If you still don’t get it to work, please let us know the exact steps to reproduce it and we will fix it.

[support]

Hi,

OK, please let us know what errors you are encountering so that we could help you.

[support]

Hi,

Thanks, we’ll consider adding an option for that in v5.2.

[support]

This is a known issue; VisualGDB does not deploy the shared libraries during toolchain testing. You can safely ignore the error. If you get it during debugging, please ensure that the project producing the libraspicam.so is referenced by the project you are debugging. Alternatively you can add a pre-debug action to deploy the .so file manually.

[support]

Hi,

Please locate the stm32f0xx_hal_conf.h file in one of the directories with the generated files and add it to the Include Directories field on the Makefile Settings page of VisualGDB Project Properties.

[support]

Hi,

We have fixed the problems related to the Find Symbol Results window in this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.2.794.msi

It also contains numerous improvements to the IntelliSense engine that make it much faster for large projects.

You can resolve the stm32_compat.h problem by opening Visual Studio project properties (not VisualGDB Project Properties) and removing the stm32_compat.h file from the “Forced Includes” field.

Let us know if you encounter further problems.

[support]

Hi,

Indeed, you have probably missed the “Import a project -> Import a project built with other tools” option in the project wizard. As long as you select it, VisualGDB will create a project with a custom build system, but still import the source files you select. You can also import them later via right-clicking in the Solution Explorer and selecting “Add folder recursively”.

[support]

Hi,

You can use the system() function:

#include <stdlib.h>
int main()
{
    system("sudo apt-get upgrade");
    return 0;
}

Let us know if this works.

[Author]

Posts