[support]

Hi,

We have retested the STM32Nucleo-L476RG board with the latest ST-Link firmware (V2.J34.M25) and unfortunately still could not reproduce the problem. We would advise trying another board instead.

[support]

Hi,

Based on our experience, upgrading the project to a newer ESP-IDF release might be a non-trivial task, since different ESP-IDF versions are not 100% backward-compatible.

Our best advice would be to read the release notes and check how similar code examples changed between different versions.

[support]

Please note that our technical support covers the issues with VisualGDB only. We are not able to help troubleshooting specific projects, or resolve any issues in external tools.

[support]

Sorry, most likely the file was too large to be uploaded. Would you be able to upload it to a file sharing service (e.g. Dropbox) and share a link with us?

[support]

Thanks, we have reproduced the problem. Indeed, the new SDK uses a slightly different format in order to accommodate multi-core devices, and our SDK importing logic is not handling it correctly.

Due to the considerable changes to the SDK structure, it will take us about a week to fully update our SDK importer and test it. We will publish an update here once it is ready.

[support]

Hi,

Thanks, the board should be normally supported. Most likely, some previous firmware changes have affected some of the functions used by Analyzer2Go.

Unfortunately, it’s hard to suggest anything more specific without being able to reproduce the problem on our side, so our best advice would be to try another board.

[support]

No problem. Once you send us the SDK archive, we will investigate this.

[support]

Hi,

As every device-specific SDK generated by SDK builder is different from others, indeed some SDK versions or some devices may not be imported properly. As long as this is an MCUXPresso SDK, it is fully covered by our support. Please attach (or send to our support) the SDK archive and let us know the device name and the sample you pick from the wizard, and we will update our importer plugin to handle it correctly.

[support]

Our tutorials demonstrate how to efficiently use various VisualGDB features using various popular frameworks and libraries as examples. They are intended to help our users find productive ways of using VisualGDB in large real-world scenarios. We usually update them when the related VisualGDB features are considerably redesigned or new functionality is introduced on our side.

The tutorials would normally work as long as you are using the same version of the framework as shown in the tutorial. If you decide to try out a newer version of the library shown in the tutorial, you may indeed need to make adjustments to accommodate the differences introduced in the new version.

[support]

Yes, this is correct.

[support]

Hi,

This looks like an OpenCV issue and not something specific to VisualGDB, hence it is not covered by our support. Please consider asking on OpenCV forums for help for OpenCV-specific issues.

We will eventually update our OpenCV tutorial to reflect the latest version, however it has a relatively low priority, so we are not able to give any time estimates for it now.

[support]

Hi,

Most likely, you have converted the project to a stand-alone one, losing the ability to edit the frameworks. You can recheck it on the first page of VisualGDB Project Properties. If it shows the list of GCC flags rather than a list of devices, it is a stand-alone project that only includes a snapshot of a specific BSP configuration and cannot be automatically configured further.

[support]

Hi,

Sorry, this looks like a bug in OpenOCD. As the OpenOCD’s FLASH programming logic is maintained by ST, we don’t have many insights into it, however based on our previous experience, trying to rearrange various sections of your program (e.g. making sure they are aligned and none of them is too small) should fix it.

You can also try building OpenOCD from sources as shown here. Alternatively, please consider trying Segger J-Link. It comes with its own GDB stub that is more reliable than OpenOCD, and usually just works out-of-the-box.

[support]

Hi,

Please try using the “Signals and Exceptions”  button (lightning icon) in the GDB Session window. This will open gdb-specific exception settings that let you configure specific exceptions.

[support]

VisualGDB stores the cached headers under %LOCALAPPDATA%\VisualGDB\RemoteSourceCache\<host name>. If you would like to avoid re-downloading them, consider simply copying or symlinking some of the directories there.

[Author]

Posts