Forum Replies Created
-
Posts
-
Hi,
Sorry, VisualGDB doesn’t provide any console-only commands for managing toolchains (you can install them via the VisualGDB Package Manager though). Please feel free to describe your setup so that we could suggest a better workaround.
Hi,
The new toolchain should not flash any other file apart from esp_init_data_default.bin. You can also disable the esp_init_data_default.bin flashing by setting the “FLASH Initialization file” under the advanced settings to an empty string to see if the new programming step affects the problem.
Hi,
For most of the cases we would advise simply using relative paths (e.g. ../SolutionDir). The relative paths are always interpreted relatively to the project directory.
Hi,
Sorry, this is currently not supported. We will integrate VisualGDB with the regular VS font settings as a part of converting the VisualGDB Project Properties window to the WPF framework (we are gradually doing this across several releases). As a quicker workaround, we could add an option to override the default font size manually.
Before we can do that, could you please check whether the issue only affects WinForms settings pages (e.g. Project Properties), or does it also affect the WPF settings pages (e.g. Advanced GDB Settings)?
Hi,
We are not aware of anything like this, however we can still help you pinpoint it. Next time you observe the issue please try switching the IntelliSense engine to the regular VC++ one and back (via the Clang IntelliSense Diagnostics Console). Does this resolve the issue? If not, does reopening the source file resolve the issue, or is restarting VS the only way to solve this?
Hi,
The deactivation requests are handled on a case-by-case basis, but we do handle them even for licenses with expired support (please note that you will only be able to install the VisualGDB versions released within a year from your license purchase; we also advise making backups of all BSPs/toolchains/debug packages as the newer versions are not always compatible with older VisualGDB releases).
Hi,
OK, we have double-checked this and it looks like our programming plugin indeed did not load the init data file correctly in some cases. We have fixed it in the R14 toolchain relesae available here: http://gnutoolchains.com/esp8266/
You can program the FLASH memory without debugging via Debug->Program Firmware without Debugging.
Hi,
We have managed to reproduce the problem. VisualGDB was not properly copying coverage directory information to the test container file when building it outside Visual Studio.
We have fixed it in this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2055.msi
If you encounter any further problems, feel free to contact us again.
Hi,
You can enable the .hex file generation via the Build Settings page of VisualGDB Project Properties (for GNU Make projects) or via the “Embedded Project” page of VS Project Properties (for MSBuild-based projects). Once enabled, the .hex file will be placed in the same directory as the .bin file.
Hi,
Strange, this should normally not happen. We can definitely investigate this if you could let us know the steps to reproduce it, or share the project files demonstrating the problem.
Hi,
The empty .job would normally mean that VisualGDB could not locate any raw coverage reports after running the project. This might be caused by some combination of settings that prevents VisualGDB from locating the files when running from command line.
Could you please check if you can reproduce this problem on a clean test project created via VisualGDB project wizard?
Hi,
Sorry, unit tests for Advanced CMake projects are not officially supported yet, so bugs like this one are to be expected. Either way, we can help you resolve this if you could attach the generated TestFramework.cmake file. Most likely CMake gets confused with some library references.
Hi,
As long as the KeepRawCoverageReports registry setting is set to 1, VisualGDB should keep the reports. Please try deleting the coverage report directory, running the tests via command line and let us know which exact files/directories were created. This should explain what is going on.
