[support]

Hi,

Just wanted to share an update that we have added support for embedded code coverage (including Live Coverage) to the following build: VisualGDB-5.5.2.3390.msi

You can enable it via VisualGDB Project Properties -> Code Coverage.

For most accurate results, please consider upgrading to the latest GCC 9.2.1-based ARM toolchain (that is a repackaged version of the official GNUARM toolchain).

[support]

Hi,

Looks like you are viewing the installed packages. Please try switching to the “online” view instead.

[support]

Sorry, unfortunately we are not able to provide project-specific help as a part of our regular product support. The only advice we can give is to make sure you follow and understand each step of the tutorial mentioned in the previous post. It does explain the “undefined reference” problem and the techniques used to troubleshoot it.

[support]

Please follow the tutorial below for measuring the time between events on embedded devices: https://visualgdb.com/tutorials/arm/chronometer/

[support]

Hi,

The Cortex-A devices are typically used together with Linux and hence require a special Linux toolchain built for the exact distribution/configuration that is running on the target.

We provide toolchains for the most commonly used Cortex-A boards (e.g. Raspberry Pi, Beaglebone). If you are using a different board, please check the board vendor for a cross-toolchain.

If you are looking for a barebone environment (without Linux), please try creating a project manually as shown in this tutorial: https://visualgdb.com/tutorials/arm/legacy/

[support]

Yes, please try deleting all the toolchains and installing the one from https://gnutoolchains.com/esp32/.

Then check if you can create, build and debug a new project from scratch. If it doesn’t work please share the details and we will help.

If a new project works, but the existing one doesn’t, you may need to port your project to the new ESP-IDF (the ESP-IDF releases are not 100% backward-compatible). If you are getting errors specific to ESP-IDF API, please consider asking on the ESP32 forum.

[support]

Hi,

Sorry, the built-in gdb simulator doesn’t work well for ARM targets and cannot be recommended for any practical scenarios. It is only usable for basic low-level tests (e.g. quickly checking that the ELF file can load into gdb and has the necessary debugging symbols).

[support]

Hi,

Yes, please try using the $(TargetDir.forwardslashes)/$(TargetNameWithoutExtension) syntax.

You can disable the regular FLASH programming via the “Program FLASH memory” setting on the Debug Settings page of VisualGDB Project Properties.

[support]

Hi,

In order to use ESP-IDF 4.0, please update to VisualGDB 5.5 Preview 1.

Please note that the old ESP32 toolchain based on gcc 5.2 only supports ESP-IDF 3.x. See this page for a full list of supported toolchain/ESP-IDF combinations.

[support]

Hi,

No problem, you can always install the previous debug method via Tools->VisualGDB->Manage VisualGDB Packages->Show Old Package Versions.

Generally, the ESP32 tool ecosystem is relatively fragile, so some combinations of toolchain/ESP-IDF/debug package may indeed not work.

If you encounter weird reliability issues, we would advise starting with a basic LEDBlink project using one of the toolchain+ESP-IDF combinations shipped by us (they passed minimal tests on our side) and then comparing the working setup with the one that behaves unreliably. This should help pinpoint the specific parameter that is causing the issues.

[support]

Unfortunately, the description you provided does not contain sufficient details for us to reproduce the issue. Please consider describing the issue per our problem reporting guidelines so that we could try reproducing it on our side.

[support]

Unfortunately, the description you provided does not contain sufficient details for us to reproduce the issue. Please consider describing the issue per our problem reporting guidelines so that we could try reproducing it on our side.

[support]

Looks like you are referring to the this thread.

We have mentioned that the oldest version of FreeBSD tested with SysprogsSync was 9.3. Once you provided more details, we pointed out that the error was caused by a 32-bit build of FreeBSD, and that using a 64-bit build, or patching SysprogsSync as we suggested, would solve the problem.

If you do not have any specific version constraints, please try using a 64-bit build of the latest FreeBSD. Although some minor functionality may not work as expected, most of the functionality should work.

It also looks like your forum account is using a different email address that is not linked to your license key. Please let us know the email address associated with your key via the support form, or update the forum profile accordingly, so that we could link it to your support profile.

Edit: the latest error looks like the latest gdb might not be compatible with the FreeBSD version you are using. Sorry, unfortunately this is outside of VisualGDB’s control. Please try installing the latest 64-bit FreeBSD as suggested above.

 

[support]

Sorry, VisualGDB does not support GDB 6.1, as it is more than 15 years old and is missing many critical functionality. If you absolutely have to use this version, we could add limited support for it as a custom paid feature. Please contact our sales to get a quote.

[support]

Hi,

Looks like your gdb version does not support some of the gdb/mi commands used by VisualGDB. Normally, updating to gdb 7.0 or later (although we recommend the latest 8.3.1 release) should solve the problem.

[Author]

Posts