Forum Replies Created
-
Posts
-
Hi,
We have just rechecked our ARM toolchain and it works just fine. Most likely, you have configured something incorrectly on our side.
We will monitor the issue and will consider investigating it further if other users report similar issues.
Hi,
The FreeRTOS integration is available starting from the Custom edition. If you have purchased a lower edition, it would work while the trial period was still active, and would then turn off.
If this is the case, you can always upgrade your VisualGDB key via this page or see this page for a full list of the Custom Edition features.
No problem. Feel free to bump this thread once ESP-IDF v5 is officially released (not beta and not RC) and we will provide a timeline on fully integrating it.
If you you would like us to review your code and suggest the best layout for it, please contact our sales for a consulting quote.
Otherwise, please make sure you reproduce the issue on a smaller “hello, world” setup involving the minimal amount of sources and libraries, and solve it successfully for a regular Win32 C++ project. If you then share the steps you needed to solve it for a Win32 project per our problem reporting guidelines (with full screenshots from scratch), we can point out the equivalent steps with VisualGDB.
Hi,
VisualGDB projects use the same semantics as the regular Win32 C++ projects. If you are new to C++ and are not familiar with header files and libraries, we would advise first creating the project layout you need using the regular Win32 C++ project type. Once that works the way you intend, feel free to let us know how you created it and we will point out the locations of equivalent VisualGDB settings.
That said, the VisualGDB settings for C++ projects are designed to be as close as possible to the original Win32 C++ project properties, so once you get it working for the regular project type, finding the VisualGDB settings should be straight-forward.
This is by design. C++ and C# projects have different semantics, so this button is not needed on C++ projects.
Hi,
Please try using the Add->Existing Item command in Solution Explorer. It should do just what you described.
Hi,
Thanks for your suggestion. Currently VisualGDB indeed only searches the property captions and not the underlying variable names. We will look further into it next week and will publish an updated build that will search both captions and internal names.
No worries. Due to some reason, Visual Studio sometimes randomly resets this specific color setting (it appears to be related to switching between the light and dark theme), but we never managed to reproduce it reliably, so we just showed its exact location in our documentation.
If you (or anyone else) discover a reliable way to reproduce this, feel free to post an update and we will look further into it.
Hi,
It looks like your technical support period has expired. We would be happy to help you, however we would kindly ask you to renew your technical support on the following page first: https://sysprogs.com/splm/mykey
Hi,
Sorry, MSBuild and CMake handle the build settings in rather different ways, so there is no automatic conversion between them. Our best advice would be to use the generic import logic and then manually adjust the project settings to match the MSBuild project.
Hi,
The fast semihosting works for output only, however it is backward-compatible with the regular semihosting, that works both ways. I.e. you can use the fast semihosting to output data from the device without any delays, and at the same time use the regular semihosting API to read the input from VisualGDB.
If you are looking for a fast way to send data to the device, please consider using the Test Resource Manager API.
Unfortunately, it is hard to suggest anything specific based on the description you provided.
In order for us to provide any help with this, we need to be able to reproduce the problem on our side.
Please provide complete and detailed steps to reproduce the issue as described below:- The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
- Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch. If the problem happens with a specific ioc file, please provide the steps (with full uncropped screenshots) how you create that file.
- The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.
You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.
Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.
Thanks for confirming your license. The .ioc files contain settings for the STM32CubeMX generator and do not directly reference any source files/build settings or anything else that could be imported.
In order to import them into VisualGDB, you would first need to open them in STM32CubeMX, then generate an STM32CubeIDE project, and finally import the generated STM32CubeIDE project using the VisualGDB Embedded Project Wizard.
Hi,
Please refer to the following tutorial for detailed troubleshooting instructions: https://visualgdb.com/tutorials/arm/import/diagnose/
