[support]

Hi,

Sorry, we have indeed not tested this explicitly with ESP32, so it may need some minor adjustments. Feel free to let us know the errors you encounter and we will suggest how to solve them.

[support]

Hi,

Thanks for the repro, we have fixed it in this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.15.1399.msi

[support]

Hi,

ESP32 has only 2 hardware breakpoints, so you may simply run out of them. You can use the “info breakpoints” command to quickly check how many breakpoints are currently set.

[support]

Hi,

Sorry, looks like we forgot to update the tutorial. Starting from VisualGDB 5.2, the build message templates have been moved to the <VisualGDB directory>\RegularExpressions.xml file along with other regular expressions used by VisualGDB so that you can tweak them more easily.

You can now also override the message templates for each project individually. Please see the updated Keil tutorial for details.

[support]

Hi,

Please ensure you are using the Clang-based IntelliSense and are not using 3rd-party plugins like Resharper as they are not fully compatible with GCC-specific code.

[support]

Hi,

If you are using a Custom edition or higher, you can add a custom pre-built step via VisualGDB Project Properties -> Custom Build Steps.

If you are using a lower edition, you would need to manually create a custom MSBuild target as described in the MSBuild documentation.

Note that for converting binary files to resources you can conveniently use the embedded resource mechanism as described here: https://visualgdb.com/tutorials/arm/resources/

• This reply was modified 7 years, 1 month ago by support.

[support]

Hi,

Sorry, we are not the vendor for the ESP32 IDF and hence can only provide help on issues related to VisualGDB. If you can confirm that this problem only happens when using VisualGDB and not when building from the ESP-IDF directly, we will re-investigate it, but otherwise the ESP32 forum is the best place to seek advice on this.

[support]

Hi,

FTDI JTAG uses the JTAG interface to program the SPI FLASH. Normally you only need the set the driver to either WinUSB or LibUSB (both refer to the same driver, but sometimes one of them fails to install). Note that OpenOCD will try using both interfaces of the USB device that will result in an ACCESS_DENIED or a similar error even if the settings are correct and the second interface can be opened successfully. Although it should not affect programming/debugging, it could be misleading.

If you still cannot get debugging to work, feel free to post your OpenOCD log here and we will check it for common issues.

[support]

Hi,

Please try using our UsbDriverTool to change the driver type. It supports changing the drivers for each interface individually.

[support]

Hi,

Sorry, we are not aware of anything similar. As this looks like a very minor issue, we would suggest simply ignoring it until you get a 100% repro that will make it easy to understand what is causing this.

[support]

Hi,

We have not explicitly tested the Qt natvis files with VisualGDB. Hence our best advice would be to create a new .natvis file like described in this tutorial, ensure that it works and then add definitions from the Qt debug helpers one-by-one. If you can confirm that a specific construct from the Qt natvis file works with the regular VS but not with VisualGDB, let us know and we will release a hotfix.

[support]

This could be caused by excessive line endings in the printed lines. Our best advice would be to isolate the exact sequence of steps that causes it and then try removing the line endings (or replacing \r\n with \n).

[support]

Hi,

If the board does not come with a pre-compiled OpenCV, you would need to build it from scratch. This could be somewhat tricky as it’s a big library, but a good starting point would be our Raspberry Pi OpenCV tutorial: https://visualgdb.com/tutorials/raspberry/opencv/build/. It summarizes the build steps and describes the common issues, although the exact steps for Intel Edison may be slightly different.

[support]

Hi,

Sorry, troubleshooting issues specific to the open-source GNU tools unfortunately goes beyond the bounds of our product support. There are plenty of tutorials online though (e.g. this one) or we could guide you step-by-step as a part of our paid consulting services if you don’t want to spend time figuring it out yourself.

[support]

Hi,

Thanks for the update. It’s good to see that ESP32 is getting more documentation. VisualGDB supports the ESP32 OpenOCD as described in that document, but all the debug limitations mentioned in other threads and in our blog are unfortunately still present.

[Author]

Posts