[support]

Hi,

Thanks for updating your profile. However, it looks like your technical support period has expired a while ago.

Please consider updating it here: https://sysprogs.com/splm/mykey (the 50% discount will add 1 year to the original expiration period; alternatively please contact our sales for a 10% late renewal discount that will extend the expiration period to a year from now).

As soon as you renew your support, we will be happy to explain the semantics on $(LOCAL_PATH) and other Android-related settings.

[support]

Hi,

Depending on the mode you used for importing the project, the preprocessor macros might not have been imported automatically.

If you could attach your keil project file (no source files are necessary), the screenshots of all the steps of the VisualGDB import wizard and the macro name that is set in the Keil project and not automatically imported into VisualGDB, we should be able to tell what is going on and update our importer accordingly.

[support]

Hi,

No problem. Please let us know the email associated with your license key so that we can link it to your forum profile and we will be happy to help you.

[support]

Hi,

Please consider using the MSBuild Exec task instead. It should work regardless of the project type and other VisualGDB-related settings.

[support]

Hi,

Please try creating a temporary copy of the interface configuration file (e.g. esp32_devkitj_v1.cfg) and add the ftdi_serial command there (OpenOCD should show the serial numbers of connected devices if multiple matching adapters are found), then specify the copied script in the Debug Settings.

Normally VisualGDB should do this automatically, however we have not explicitly tested this with the ESP32 devices, so minor adjustments might be required. Feel free to let us know your observations and we should be able to update VisualGDB to do this automatically.

[support]

Hi,

Most likely the Keil project is using a different configuration file.

If you have 2 similar projects and would like to compare them, please consider enabling the preprocessor output in VisualGDB (VS Project Properties -> C/C++ -> Outputs) and Keil. This will expand all #include<> directives and the preprocessor macros, so you should be able to see where are various macros/variables defined and why the corresponding definition was not included in the other project.

[support]

Hi,

Sorry, this is by design. This feature is available starting from the Custom edition of VisualGDB. If you are using a lower edition, please consider adding a Make or MSBuild target manually.

Alternatively, you can update your license to the Custom edition here: https://sysprogs.com/splm/mykey

[support]

Hi,

Most likely, your project does not enable the CRYP module in the configuration file. Please try searching for CRYP (case-sensitive, whole word) in the ST peripheral library folders. Most likely you will find a definition #ifdef-ed with a macro like STM32_CRYP_ENABLED. Then check your configuration file (typically stm32_*_config.h in the project directory) for similar definitions and uncomment/add the definition enabling the CRYP module.

[support]

Hi,

Thanks for sharing this.

The Live Variables rely on the debug probe’s ability to provide an independent interface (completely parallel to GDB) for accessing the memory. Last time we checked, BMP did provide such an interface.

If anyone could patch the BMP sources to support a separate memory access interface, we will be happy to share instructions on creating a VisualGDB debug plugin to use it similarly to OpenOCD and J-Link.

[support]

Hi,

Sorry for the confusion. The command got renamed to Manage VisualGDB Packages as it now also handles Linux test frameworks and other non-embedded packages. Please use the new command instead.

[support]

Hi,

The GDB binary is typically supplied with your toolchain and depends on your project type. Generally, we were not able to get gdb to work reliably with spaces in paths during our tests and hence recommend using paths without spaces. You can try working around this via the Path Mappings page of VisualGDB Project Properties (see the “All Commands” view of the GDB Session window to see the exact commands sent by VisualGDB), setting the “Use file names only” checkbox on the Advanced GDB Settings page, or by running the breakpoint commands with different path syntax directly via the GDB Session window.

If you manage to find a specific breakpoint command that works with your paths, feel free to post it here and we will help you configure VisualGDB to issue this command.

[support]

Hi,

This looks like the c:/sysgcc/raspberry/bin/../arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf/libm.so file was not synchronized properly. It could be a VisualGDB bug, or might be caused by something else.

Please try deleting all subdirectories in the toolchain’s sysroot directory except for etc, then resynchronize it again.

If the problem persists, please try checking whether libm.so file is a symlink (note the backslash instead of forward slashes):

dir c:\sysgcc\raspberry\bin\..\arm-linux-gnueabihf\sysroot\usr\lib\arm-linux-gnueabihf\libm.so

If it is a symlink, please check if the target file pointed by the symlink physically exists and contains a valid ELF signature. Please also check any warnings shown during sysroot synchronization. E.g. insufficient disk space or corrupt file system might prevent some files from being synchronized.

[support]

Hi,

Please try synchronizing the toolchain using VisualGDB 5.4 Beta 2. It includes an optimized file transfer engine that works around known problems with sysroot synchronization.

[support]

Hi,

The issue is not related to any VisualGDB settings – it is 100% between the toolchain and the target. Please let us know which toolchain and what SD card image you are using.

[support]

Hi,

Thanks for reporting this. We have fixed it in the following build: http://sysprogs.com/files/tmp/VisualGDB-5.4.12.2672.msi

[Author]

Posts