Forum Replies Created
-
Posts
-
Hi,
Most likely the app_trace is not enabled for your project. Please try following this tutorial in order to enable it: https://visualgdb.com/tutorials/esp32/apptrace/
Hi,
This looks like a TCP communication error between VisualGDB and OpenOCD. Please try restarting your computer and disabling the firewall, as it might be blocking OpenOCD.
If the error persists, please try ignoring the error and starting a debug session. Then check both OpenOCD and gdb logs for more detailed error messages.
Hi,
Looks like you are using VisualGDB 5.3. In that version you can achieve the same effect by adding “-DKEY=VALUE” arguments to CMake command line. Alternatively please consider updating to VisualGDB 5.4 Preview 10 – we have redesigned many configuration dialogs and pages in that version to make them more intuitive and easy to use.
Hi,
The Keil components are fully supported, although due to the relatively high complexity of the Keil pack definitions, this feature is only available in the Custom edition. If you are using a lower edition, please consider creating a project in the uVision IDE, discovering the list of source files and preprocessor macros and adding them manually to your VisualGDB project.
Hi,
For Keil projects VisualGDB imports the device list (and the packages) directly from the Keil packs. Hence please double-check that you can create a project for your device using the uVision IDE. If not, please install the missing Keil packs and restart Visual Studio. VisualGDB will then rescan the Keil packs and show the devices in the device list.
Hi,
This might be a remnant from the old Cygwin-based toolchain. Please try installing the latest ESP32 toolchain and create the project from scratch. If this solves the problem, please re-import your project into VisualGDB.
Hi,
Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2617.msi
Hi,
Sorry, that probably comes from the fact that you are using templates. Counting references for templates is fairly complicated due to the way compiler tracks them internally, so the one-line summary may indeed not be 100% accurate (it has to be computed using a somewhat simplified logic due to performance constraints). We should be able to eventually fix this, however we won’t be able to fit it in v5.4.
Hi,
Good to know it works. Just in case anyone else runs into the same problem, here’s another workaround to this: https://blogs.msdn.microsoft.com/shawnfa/2008/03/14/disabling-the-fips-algorithm-check/
Hi,
No problem, we can help you, however it looks like your technical support has expired. Please renew it and we will be happy to walk you through resolving this.
Hi,
It looks like your technical support period has expired. Please renew your license here and we will be happy to help you resolve this.
Hi,
Sorry, it’s a known bug of Preview 10. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2610.msi
Hi,
Sorry about that, it’s a known issue with Preview 10. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2609.msi
Hi,
Yes, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2609.msi
Simply select a shared checkout when creating a new project and VisualGDB will automatically configure it for you.
Thanks again for the wait and let us know if you have any further questions/suggestions.
