Forum Replies Created
-
Posts
-
Hi,
No problem. We have released an updated ESP8266 toolchain based on the latest toolchain from Espressif and the SDK v3.4.
You can download it via VisualGDB Package Manager or directly here: https://gnutoolchains.com/esp8266/
No problem. Please let us know the CentOS version you are using and also the list of files in the /etc/yum.repos.d directory and we will check what is going on.
Hi,
Thanks for the detailed demonstration. We have updated Live Watch to properly support statically allocated threads and queues. Please try this build: VisualGDB-5.6.1.4098.msi
Hi,
You can simply synchronize the cross-toolchain’s sysroot with the target via VisualGDB Project Properties -> Build Settings -> Synchronize Sysroot and then use the regular syntax for library names and directories. You can find more information on the following page: https://visualgdb.com/documentation/linkerinputs/
Hi,
Please refer to the following documentation page for more details on configuring CodeJumps: https://visualgdb.com/documentation/intellisense/#codejumps
Hi,
There is no special command to deploy the application, however you can script it via the Custom Shortcuts, or simply use the Debug->Start Without Debugging command.
Hi,
This is something to check on the VS side. VisualGDB reports the sketch files, source files and SPIFFS folder contents in exactly the same way. We have also double-checked it with git integration and it worked as expected as well.
Hi,
For Arduino projects VisualGDB relies on the regular Arduino build process (arduino-builder.exe) that does not support adding arbitrary resources. The only exception is the SPIFFS file system that is only available when using the ESP32 Arduino core. VisualGDB supports it starting from the Custom edition as shown in this tutorial.
Hi,
J-Link indeed typically works better than ST-Link, and it comes with its own fully tested and supported GDB stub that replaces the open-source OpenOCD. VisualGDB supports both OpenOCD and J-Link software via interchangeable debug plugins, so our users can pick the debug probe that works the best for their setup.
Hi,
As per the VisualGDB feature table, unit tests are supported by the Ultimate, Android and Custom editions.
Hi,
According to our records, your trial has expired. We can gladly investigate this further, however we would kindly ask you to purchase a license first.
Hi,
No problem. The warning about spaces in path is meant for a different package type. CMake can be safely installed into paths with spaces.
We have updated VisualGDB internally to not show it when installing CMake and will include this fix in the next VisualGDB update.
Hi,
This looks like an incompatibility between some feature of the Qt framework and XMing (the tool for showing Linux X11 GUI on Windows). You can work around it by manually installing and launching vcxsrv a more modern build of Xming. If it doesn’t help, please try switching your project to show the GUI on the Raspberry Pi itself (via VisualGDB Project Properties -> Debug Settings).
Hi,
No problem. We have rechecked the handling of CommonExecutablePath and ExecutablePath by the regular VC++ projects and updated VisualGDB to replicate its behavior.
Please try this build: VisualGDB-5.6.1.4083.msi
Hi,
For all questions related to licensing, activations, renewals and quotes, please contact our sales via the contact form.
