Forum Replies Created
-
Posts
-
No problem. Most likely this is caused by some other declaration or setting. Please try getting a minimal example that triggers the problem on a newly created project and share it with us so that we could see what is going on.
The error looks correct (the private functions Parent are not accessible to derived classes). You can double-check this by trying to build the project – the compiler should show the same error.
Hi,
Yes, please try running the following command:
<VisualGDB directory>\VisualGDB.exe /build <full path to .vgdbcmake file>
The daily builds with hotfixes do not always pass our internal tests, so some issues are to be expected. That said, the 5.4.106 branch has passed most of the tests and should be much more stable (we are also planning to release a stable R6 update today).
VisualGDB simply requests the target to enable the X11-over-SSH forwarding. The exact implementation of this logic is provided by the target and is outside VisualGDB’s control. Please refer to the Linux and X11 documentation for more details.
VisualGDB simply requests the target to enable the X11-over-SSH forwarding. The exact implementation of this logic is provided by the target and is outside VisualGDB’s control. Please refer to the Linux and X11 documentation for more details.
Sorry, this is not something managed by VisualGDB, so it’s hard to give any specific advice. Please refer to the Linux and X11 documentation.
Just wanted to let you know that we have updated VisualGDB to detect the gcc version for the GNUARM toolchains and also to show all discovered versions of the toolchain instead of just the latest one.
Please feel free to try this build: VisualGDB-5.4.106.3173.msi
Hi,
VisualGDB already supports selecting arbitrary ESP-IDF checkouts to use with your projects. Please use VisualGDB Project Properties -> ESP-IDF Project -> ESP-IDF Checkout to select a version you would like to use (VisualGDB can automatically clone IDF releases from Github).
We are also working on an update to our ESP32 toolchain that will include a newer IDF checkout.
Hi,
If you are using clang-format, please use our graphical format file editor to change the line break logic. If you cannot find a specific setting, please refer to the clang-format documentation here for an exhaustive list of formatting settings.
Thanks for the update. It indeed looks like Espressif has ported their OpenOCD fork to a newer OpenOCD version, adding support for more devices.
We have merged these changes into our branch and released an updated debug package. Please update it via Tools->VisualGDB->Manage VisualGDB Packages.
Hi,
Please check whether the code formatting for your project is managed by clang-format, or the legacy formatting engine. If a formatting icon appears in the top right corner of the text editor, the file is managed by clang-format and the formatting behavior can be configured by clicking at this icon. For legacy formatting engine, you can use Tools->Options->Text Editor->C/C++ (VisualGDB)->Formatting.
If you are not sure, please send us a screenshot of your Visual Studio window having the source file open and we will provide you with more detailed steps.
Good to know the entry point works.
Regarding bootloader.bin, please try enabling verbose logging via Tools->Options->Projects and Solutions->Build and Run->MSBuild Project Output Verbosity -> Diagnostic.
This should produce a detailed build log showing the project build order and also when the .bin file is generated and when it is used by another project. If it doesn’t help, please feel free to post it here and we will try to help you get it to work.
Hi,
Sorry, we don’t have a ready-to-use driver for the Parallel NOR FLASH, however you should be able to create your own plugin for NOR FLASH based on our QSPI plugin (see this tutorial). You may also want to check with Segger support whether they have ready-to-use J-Link-specific plugins for this memory type.
Hi,
The easiest way to create the project structure you described would be to create the regular Application projects and then edit the .pro files, manually switching their type to libraries.
However for advanced Qt-based projects, we would advise using either MSBuild or CMake. Although this requires extra initial setup, such setup would be much more scalable due to better integration with VS.
