Forum Replies Created
-
Posts
-
Hi,
Thanks, we have confirmed this. Looks like GNU Make doesn’t properly handle values with spaces regardless of the escaping.
As a workaround please try adding the following code directly to CFLAGS/CXXFLAGS:
-D__int64="long long"
Hi,
Good to know it works. Please feel free to follow up in the JTAG topic and we will try to suggest further diagnostic steps. E.g. we noticed that the JTAG test shows the “halted, PC=xxxx” line, while the actual debug session doesn’t. Can you confirm that behavior 3 times in a row (i.e. debug, test, debug, test, debug, test). If the results are not consistent, this is likely due to flaky wiring.
Hi,
The easiest way to do this would be to select the “bootloader + gdb stub” debug method. If you don’t actually include a debug stub, you will be able to program your firmware, but not debug it. If you do include the stub, you will be able to debug it as well. You can read more about the gdb stub in this tutorial: https://visualgdb.com/tutorials/esp8266/gdbstub/
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.
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/
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.
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).
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.
Hi,
Thanks, looks like our bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.3.17.1948.msi
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.
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.
