[support]

Hi,

No problem and good to know it works. If you encounter any further issues, please feel free to contact us again.

[support]

Hi,

Thanks for the update. We would definitely need to see the screenshots to advise you further. By “Entire Visual Studio Window” we mean the physical window created by Visual Studio (including the navigation bar, Solution Explorer and Errors pane). Those panes may contain clues to  the problem and we would need to see them to understand which parts of the IntelliSense engine have been initialized properly.

[support]

Hi,

This looks like an incomplete toolchain installation. Please try restarting Visual Studio and creating a new project with the same toolchain. If it doesn’t help, please let us know if you are using GNU Make or MSBuild.

[support]

Hi,

This looks like all necessary header files were included properly, but the .cpp file (or library) containing the implementation of HardwareSerial::begin() was not included in the project. The solution would be to locate the source file implementing this method and add it to the project as well.

If you encounter any further problems, feel free to post the details here and we will help you resolve them.

Also if you prefer a turnkey solution ASAP, please feel free to send us the Arduino code you would like to convert to a VisualGDB project and we will give you a quote for doing this on our side.

[support]

Hi,

VisualGDB inserts extra indentation after incomplete statements (not ending with ‘;’ or ‘}’), so this is by design.

If this is annoying, we could add an option to disable this behavior for templates. Could you give us an example of how you usually format your template declarations so that we could ensure the new option supports it?

[support]

Hi,

This is strange. We have just tried reproducing this on a clean project, but could not get the errors you are experiencing. Most likely your project picked up a wrong C++ language standard setting.

We could help you pinpoint this if you could let us know the project type (Make, MSBuild, CMake, Advanced CMake) and whether you can reproduce the same behavior on a clean “Hello, World” project.

[support]

Hi,

Sorry, the remote source cache location is fixed and cannot be changed.

One quick workaround would be to try using the Advanced CMake Subsystem with the direct SSH file access. It will perfectly support long paths, duplicate case-sensitive names and other scenarios that don’t work on Windows.

Another option would be to indeed copy the toolchain directory somewhere locally and then use the header discovery mechanism to quickly locate the missing headers.

[support]

Hi,

We are sorry that it’s not working out. We are planning to add Arduino support in the upcoming VisualGDB 5.4, however we still don’t have a specific deadline for it set (we are currently finishing a major VisualKernel update and will make more specific VisualGDB plans once it is released).

Until we officially support it, we can answer general questions (e.g. help you resolve the Wire.h problem), but we cannot guarantee that it will fully work, as there might be non-trivial Arduino-specific changes. We could also help you convert the project to VisualGDB as a part of our paid consulting services, however if you are OK waiting a few months until Arduino is fully supported, you will get this functionality as a part of your regular VisualGDB license.

[support]

Hi,

The code analysis results are normally shown in the regular Errors pane (and are also highlighted in the code). They don’t interfere with the build and can be distinguished by the “[Clang IntelliSense]” prefix:

If they don’t appear for your project, please try creating a new project from scratch and see if this works. If yes, please try comparing project properties between the 2 projects.

Attachments:

You must be logged in to view attached files.

[support]

Hi,

No problem, we have released a toolchain update including SDK 2.1.0. You can update it via VisualGDB Package Manager.

[support]

Hi,

This looks like a VS bug that was present in a few preview builds of VS2017, but got fixed later. Could you please attach a screenshot of your About Visual Studio window (not about VisualGDB), so that we could double-check that the build number matches the one in our test environment?

[support]

Hi,

Sorry, this would not work. VisualGDB activation system is designed to be a non-intrusive as possible and to avoid frequent reactivations, so reverting to trial won’t deactivate VisualGDB (the feature is intended for checking out the features of higher editions when considering an upgrade).

Please note that we do offer an experimental floating license (that counts simultaneous sessions, but requires continuous Internet connection) in some cases. Please contact our sales with a description of your setup so that we could help you find a suitable licensing model.

[support]

Hi,

Thanks for attaching the project. The new STM32CubeMX importer actually does exactly what you are describing – it explicitly removes references to the STM32 HAL installed by VisualGDB so that the project can use the version from STM32CubeMX.

The project you attached doesn’t build because you have both the regular and the advanced semihosting enabled at the same time. Please disable the regular semihosting as shown below:

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

Attachments:

You must be logged in to view attached files.

[support]

Hi,

This looks like a project created with an old version of the STM32 BSP. Newly created projects with the latest BSP should not have it. Either way, the warning is harmless and can be ignored.

[support]

Hi,

That would be normal if the imported code provides its own I/O functions. The linker usually mentions both source files defining the conflicting function in the error message, so you can simply locate the one coming from CubeMX and remove it from the project.

[Author]

Posts