[support]

Hi,

VisualGDB internally uses a lightly patched version of libssh2 to handle the SSH connections, so the “handshaking” delay must come from inside this library. Unfortunately investigating this on our side and optimizing the library is beyond what we could offer with our regular VisualGDB support, however if you managed to narrow this down to a specific change to libssh2 and send us a merge request, we would be able to integrate it into VisualGDB.

[support]

Hi,

Please refer to the following page for instructions on troubleshooting this: https://visualgdb.com/support/nodevice

[support]

Hi,

Thanks, looks like our bug. We have fixed it and released an updated STM32 BSP. Please update it via Tools->VisualGDB->Manage VisualGDB Packages.

[support]

Hi,

The license key should not be related to this – the problem you are encountering occurs between OpenOCD and ST-Link and the license key only affects VisualGDB.

Most likely the connection fails due to one of the following reasons:

• The ST-Link itself got damaged. This can be checked by trying to connect to it via the ST-Link utility (also updating firmware to the latest version might help).
• The drivers for the ST-Link got corrupted. Uninstalling the driver and reinstalling the regular ST-Link driver from ST might help.
• Some USB virtualization/forwarding software is interfering with ST-Link. Disabling any software of this type might help.

[support]

Hi,

If the framework changes, VisualGDB won’t replace the entire file list overriding your changes. Instead it will add the new sources to the project, keeping the “does not build” flag for the old ones.

If the new source files only contain functions/methods used by the old ones, the linker will automatically eliminate them (as long as other files are excluded), so you won’t need to update this manually.

Long term, we will solve this by fully supporting the Advanced CMake Project Subsystem for embedded projects – the frameworks will be converted to separate CMake targets and you will be able to fine-tune the references by editing the CMake files, although this will be added after the upcoming v5.4.

[support]

Hi,

Unfortunately the download location is fixed, however you could simply download the installer manually from gnutoolchains.com and install it to any location of your choice. Once the installation completes, VisualGDB will be able to find the toolchain.

[support]

Hi,

Good to know it works. If you encounter any further problems, feel free to get back to us.

[support]

Hi,

This is a known limitation. Referencing a framework automatically adds its source files to a project, that affects all configurations. Hence all framework-related settings are shared between the configurations.

If you are using MSBuild, the easiest workaround would be to mark the framework files as “does not participate in build” for the release configuration. This will prevent VisualGDB from building them (adding/removing frameworks won’t override this as long as the files are physically present).

[support]

Hi,

Please try selecting the default “Shown on the Windows computer via XMing” option and then specify the DISPLAY variable manually (note the caps) via the “Additional Environment” field above.

[support]

Hi,

Thanks for the screenshots. Unfortunately as you have cropped them, it is hard to see your project type and give further diagnostic instructions.

In order to pinpoint this further, please try adding “-Wl,-verbose” to the linker flags as suggested earlier and check the build output.

[support]

Hi,

Sorry, as this MCU is not as popular as other similar devices, we don’t have any plans for supporting it.

If you are looking for a supported Bluetooth LE microcontroller, please consider using Nordic nRF5x devices.

Another option would be to setup a project manually as described in this tutorial: https://visualgdb.com/tutorials/arm/legacy/

[support]

Hi,

Good to know it works. Unfortunately the statistics is currently computed when the report is built (it involves a few advanced cases like multiple sources reporting the same function implemented in a header file), so the filters won’t affect it. We might be able to improve this in the next major release, but we won’t be able to push this into v5.4, sorry.

The entries in the exclusion lists are actually prefixes (e.g. /usr will cover both /usr/local/include and /usr/include). Right-clicking on the files will add the entire directory of this file to the exclusion list, and then you can fine-tune via VisualGDB Project Properties (e.g. exclude the parent directory).

[support]

Hi,

Thanks for the update. Could you please also check if the files/registry values mentioned in steps 7 and 8 are present (replace VisualGDB with VisualKernel in all names)?

[support]

Hi,

Thanks for checking this. Please also check that the .so file is present in the cross-toolchain’s sysroot directory.

If it does, please try adding “-Wl,-verbose” to the linker flags and check the linker output. It will show where exactly the linker is searching for the library.

If nothing helps, please attach a screenshot of the error and the build output with the verbose linker mode turned on.

[support]

Hi,

Sorry for the delay. We originally planned to include an advanced mbed project subsystem into the upcoming Preview 4, that would eliminate the need for a special BSP package, but it got delayed to due a few changes in other external tools. We will investigate the latest mbed release next week and will release an updated BSP.

[Author]

Posts