[support]

Hi,

Thanks for letting us know. We are currently testing the new BSP based on the SDK 15.0 and might be able to fix this before releasing it.

[support]

Hi,

Sorry, the new ESP-IDF project subsystem is relatively new and is indeed missing support for some advanced use cases. We are working on improving it though.

Editing component.mk will be a reasonable workaround. Simply reload the project afterwards and VisualGDB will automatically update Solution Explorer.

[support]

Hi,

Thanks for confirming this. We have published a detailed tutorial demonstrating the apptrace mechanism (debug output from ESP32 projects) here: https://visualgdb.com/tutorials/esp32/apptrace/

Let us know if you have any questions/suggestions.

[support]

Hi,

You might be able to control the initializer list formatting using the ConstructorInitializerIndentWidth parameter (see clang-format reference). If this doesn’t help, please consider checking with the clang community. Since the clang-format logic is a part of clang, we are not able to tweak it more than clang itself allows, however we should be able to integrate new versions of the formatter into our engine as they come out.

If the formatting commands don’t work, please try checking the View->Clang IntelliSense Diagnostics Console for error messages. If nothing helps, please let us know if there is a specific sequence of steps that could reproduce this issue.

With the highlighting colors, VisualGDB has to use a relatively complex workaround in order to synchronize its color settings with the regular VC++ color settings and sometimes the VS color cache gets corrupt, preventing proper synchronization. Normally changing the corresponding color via Tools->Options manually fixes the problem.

If it doesn’t help, please attach a screenshot of the incorrectly colored code (the entire VS window including the navigation bar so we could check for other possible clues) and a screenshot of the corresponding color setting.

[support]

Hi,

This might be an OpenOCD or gdb bug (unfortunately the ESP32 debugging tools are not as mature as the ARM tools). If you could reproduce this on a basic “blink” project and let us know the exact steps to reproduce it on our side, we could check if there is an easy workaround.

[support]

No problem and thanks for confirming your license.

The ESP-IDF projects use a different structure than the regular VC++ projects (ESP-IDF maintains a list of source folders and will automatically include all sources from each source folder).

If you want to add an existing folder with multiple files to VisualGDB, there are 2 ways to do so:

1. Simply right-click on the project in Solution Explorer and click “Add -> Existing Item”. Then select multiple source files at once. This will add the current directory with the files to the list of ESP-IDF source directories. They will be compiled with your project, but will physically reside in the original folder.
2. Alternatively, right-click at the Source Files folder (or any subfolder) and select “Add -> New Folder”. This will create a new physical subfolder (you can see its full path via the VS Properties window). Copy the external source files to that subfolder using Windows Explorer and add them to the project via Add->Existing Item. This will automatically update the related ESP-IDF properties and add the files into the project. We will add a command for automatically copying files from an external directory to an existing folder to one of the next VisualGDB releases.

[support]

Hi,

It looks like you are not calling the InitializeInstrumentingProfiler() function from your main() function.

Please ensure you call it, so all the related logic gets initialized properly. If you are not sure, please try creating a basic “Blinking LED” project for an STM32 device and then start a profiling session. This will automatically insert the initialization code to the main source file, so you could compare it with your current project.

[support]

Hi,

Thanks for clarifying this. The OpenOCD version bundled with VisualKernel does support aarch64 targets, although we have indeed tested it with a 32-bit Raspbian distro (we used the raspberrypi3.cfg file).

If you could post the error you are getting with raspberrypi3.cfg, we might be able to help you resolve it, however as we have not explicitly tested the 64-bit mode, it might be failing due to an OpenOCD bug. We should be able to provide more details once we see the error message.

[support]

Hi,

Sorry, the “import folder recursively” command is not supported for advanced projects yet. If you meant a different command, we can help you figure it out, but first please let us know the email associated with your license key so that we could check your support status.

[support]

Hi,

The tutorial you mentioned describes low-level kernel debugging of the Raspberry Pi itself. If you are using VisualGDB (i.e. debugging user-mode applications), you don’t need JTAG and can simply debug your applications via SSH.

If you are trying to use Raspberry Pi itself as a JTAG debugger for a barebone ARM device, please consider using one of the Olimex devices instead (e.g. arm-usb-ocd-h). Although OpenOCD can be configured to use Raspberry Pi as a JTAG debugger, it will be relatively slow (due to various latencies) and unreliable.

[support]

Hi,

Please let us know the email address associated with your VisualGDB license so that we could check your support status.

[support]

Hi,

Sorry, live variables require the target to support reading memory without stopping. This is supported by ARM Cortex-M and some Cortex-A targets, but not on ESP8266 or ESP32 targets.

[support]

Hi,

VisualGDB primarily focuses on setups that support debugging, so it doesn’t offer out-of-the-box support for FLASHing the non-debuggable chips with avrdude. That said, there’s a very easy workaround for that.

The VisualGDB build process produces the regular ELF files compatible with almost all open-source tools (including avrdude), so running it manually with a VisualGDB-produced executable should work.

If you are using a Custom edition or higher, you can automate this by adding a custom project shortcut (Project->VisualGDB Custom Shortcuts). This will add a custom menu command to the Project menu and the context menu (if using VisualGDB 5.4 preview) that will run an arbitrary command line.

[support]

Hi,

Thanks for the suggestion, we will consider adding detailed allocation analyzer to one of the next VisualGDB releases.

Currently VisualGDB supports FreeRTOS thread names through an open-source plugin (requires the custom edition or higher, should fully work in trial mode). If it doesn’t work, please share a diagnostic gdb log and a screenshot of the Threads window and we will investigate.

Although VisualGDB currently won’t show dynamically allocated regions, it can highlight the bounds of global variables and stack frames in the memory window. Simply use the advanced memory window and enable global variable highlighting via the toolbar.

[support]

Hi,

Please refer to the following page for the explanation of the linker-related settings: http://visualgdb.com/support/linkerinputs/

[Author]

Posts