[support]

Hi,

No problem, we help you pinpoint this and find a workaround. Could you please attach a screenshot of the IntelliSense errors you are getting so that we could check if they look like any of the known issues?

[support]

Hi,

We have been investigating this since the slow extension reporting was added in one of the VS preview builds and it looks like t might be caused by the “Start your trial” message shown by VisualGDB when you start VS. We will look into displaying the window when a VisualGDB project is opened instead.

If you believe something else is affecting the startup time, please check the View->Other Windows->VisualGDB Diagnostics Console window. The first line there should report the actual time it took VisualGDB to initialize.

[support]

Hi,

We have successfully run our internal integration tests on VS2017 and have also received feedback from our users indicating that the main functionality works. There are minor glitches (like VS showing the “VS2015” label for the old projects), but they don’t disrupt the workflow.

[support]

Hi,

OK, this means that the esp32 linker cannot convert the binary file to an ELF file (so that the linker could merge it into your project). Please try locating the <file>.bin2obj.rsp file in your build folder and running the xtensa-esp32-elf-ld.exe manually with the flags specified there. Then try experimenting with adding and removing flags to see if ESP32 requires some special options to make it work.

Once you get a combination of options that work, you can edit the %VISUALGDB_DIR%\MSBuild\Targets\binary.targets file to ensure VisualGDB always uses those options.

[support]

Hi,

It’s hard to say why the breakpoints would not work. ESP32 and ESP8266 is generally very unreliable and some other settings may be interfering with the breakpoints. Our best advice would be to try setting them in different locations and try to see what causes them to fail (e.g. code in RAM/FLASH or code executed during startup).

[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 8 years, 4 months 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.

[Author]

Posts