[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/

[support]

Hi,

No problem, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.3.2349.msi

[support]

Hi,

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

[support]

Hi,

We have quickly checked the internals of the Go to All mechanism and it looks it depends on some undocumented interfaces implemented by the regular Visual Studio project types. We might be able to support something similar during quick debug (by exposing a virtual pseudo-project), however we won’t be able to fit this into the upcoming v5.4, sorry.

[support]

Hi,

The regular ESP32 project support (not the new advanced ESP32 IDF project wizard) is based on ESP-IDF 2.x won’t work with examples from other ESP-IDF releases. It also uses a slightly different build process than the original ESP-IDF (in order to be compatible with MSBuild), causing problems with some samples.

This is exactly the reason we designed the new Advanced ESP-IDF Project Subsystem that works on top of ESP-IDF and is fully compatible with it. Please use the new advanced project subsystem (and the corresponding wizard) instead of the regular Embedded Project Wizard.

[support]

Hi,

Yes, any FT2232-based JTAG adapter (including Olimex ARM-USB-OCD-H) should work. For the exact pin configuration, please refer to the tutorial for the board you are using.

[support]

Hi,

If you are using a custom edition, you can simply add an extra pre-build action to transfer any amount of arbitrary source directories. If you are using a lower edition, simply creating a pseudo-project to facilitate the transfer should work as well.

Another option would be to try the Advanced CMake Project Subsystem and switch your project to CMake. CMake projects can have multiple targets (executables/libraries) inside one project sharing the same file transfer settings.

[Author]

Posts