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

[support]

Hi,

This doesn’t look like any error that should interfere with attaching. Please check the gdb log for other errors.

[support]

Hi,

Sorry, we are not currently planning direct support for changing the option bytes, as the ST-Link utility from ST already provides a convenient GUI for editing them.

[support]

Hi,

Sorry for the delay. Based on a quick look, we should be able to support one of the TFS-supported formats relatively easily. We should be able to get you a time estimate in the next week. Would that work for you?

[support]

Hi,

Thanks for the very detailed description. It looks like an internal exception in the Visual Studio Automation logic used by VisualGDB to create some project types. It used to get triggered a lot in early preview builds of VS2017, but was fixed after we filed a bug report with Microsoft. This might be another instance of it, or a completely different bug.

We tried quickly reproducing it (creating a new Make-based project in a solution that already has a project), but could not get it to crash. As it might be a glitch in one of the recent VS2017 updates, our advice would be to keep on using the workaround until the next VS update (15.8) rolls out. If the issue persists after the next VS update, please try reproducing it from scratch (i.e. first create a new solution with a new project, then add another project) and share the exact choices you make in the wizard so that we could try reproducing it on our side.

[support]

Hi,

Yes, we are working on that. Due to the large amount of changes (also the integration of the IoT SDK), it’s taking us a bit longer than expected. The current estimate is 2-3 weeks more.

[Author]

Posts