[support]

Hi,

The Arduino might be using the built-in bootloader, not JTAG. In this case the problem could be caused by JTAG wiring issues (cross-talk, bad soldering, etc). In case of weird JTAG problems we usually recommend using one of the boards that listed in our tutorials, replicating the wiring 1-to-1 and once you get it to work, switching the setup to your regular board.

The problem could also be software-related (sometimes ESP8266 firmware modifies some undocumented ESP8266 registers making debugging impossible). In this case erasing the FLASH memory via the bootloader and esptool.py and then programming it again might help.

[support]

Hi,

You might be able to import Arduino into the ESP-IDF, however we won’t be able to provide detailed instructions until we ensure that all basic scenarios work and officially support it.

If you are using mintty, please try running “mintty -” (dash as the only command line argument). This will ensure that the environment is loaded properly and the “make menuconfig” works.

We also have a detailed tutorial showing how to use ESP-IDF with VisualGDB here: https://visualgdb.com/tutorials/esp32/esp-idf/

[support]

Hi,

Looks like the target is identified properly, but something goes wrong when OpenOCD tries to reset it. Please try connecting the reset pin to JTAG pin #3 or #15 (different JTAG debuggers use different pins). If nothing helps, please try disconnecting it completely and selecting a different reset method.

[support]

Hi,

You can specify which file extensions are transferred on the first page of VisualGDB Project Properties (e.g. add “*.xml” to the file transfer masks).

[support]

Hi,

The VisualGDB navigation bar works slightly differently (it automatically picks up the most relevant project and instead shows scopes and referenced entities). Either way, it should not be empty. Please feel free to attach a screenshot of the entire VS window (errors, highlighting irregularities, etc. might provide useful clues) and we will try to help you diagnose this.

Another quick option would be to switch back from Clang IntelliSense to VS IntelliSense. It is less compatible with GCC-specific language extensions, but will provide the regular VS navigation bar.

[support]

Hi,

Thanks, looks like our bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.3.17.1948.msi

[support]

Hi,

Thanks for getting back to us. If the layout and the clock frequency are the same, the problem could be indeed caused by the incorrect FLASH setting (e.g. QIO vs DIO or frequency).

Please try setting the lowest memory size and switching FLASH mode to DIO.

[support]

Hi,

Normally there should not be any difference. Please try enabling the verbose mode via View->Other Windows->VisualGDB Diagnostics Console to see the exact command lines launched by VisualGDB.

Another option would be to add “-d -d -d” to the make arguments so that it displays debug information about what is going on.

[support]

Hi,

Yes (you need to update to V5.3R7 if you are using Win10 Fall Creators Update).

[support]

Hi,

We have just double-checked the latest VisualGDB build with the VS 15.5.0 and could not reproduce any issues. We will be happy to help you diagnose why this isn’t working on your machine, but please renew your technical support first.

[support]

Hi,

Looks like the programming succeeds, but your board might be using a different clock frequency or different UART pin numbers. Please try changing the gdb stub baud rate to 115200 (or look up the correct value in the board documentation). You may also need to edit the gdb stub to use a different UART port.

If you are not sure about the exact steps, please try using one of the boards directly supported by VisualGDB instead (e.g. Olimex mod-wifi-esp8266-dev).

[support]

Hi,

Strange. Just to double-check: does this happen before installing VisualGDB, or after?

[support]

Hi,

It looks like Microsoft is trying to add many new features in VS2017 and that indeed sometimes compromises stability. It’s hard to say whether anything could be done on VisualGDB side to fix this – we regularly test VisualGDB with the latest VS updates (that includes updating existing VS installation with VisualGDB), however have never encountered any problems on any of our test machines. Reinstalling VS/Windows could be indeed the fastest way around this, sorry.

[support]

Thanks, this looks like a corrupt installation. Reinstalling VisualGDB/Visual Studio should normally help.

Please also note that your technical support has expired. In order to keep on receiving support, please renew your license (or update your profile email so that it matches the new license email).

[support]

Hi,

Thanks the for the update. We will try to include support for new devices in our next refresh of the AVR toolchain.

[Author]

Posts