[support]

Hi,

Sorry for the delay. We have reproduced the issue on our side. VisualGDB was applying the “nrf*” filter to the boards in the custom directory similar to the way it does for the regular Zephyr boards.

We have fixed it in the following build: VisualGDB-5.6.1.4039.msi

[support]

Hi,

No problem. We have rechecked this and indeed the STM32 SDKs contain a ready-to-use version of mbedTLS. We have updated our STM32 BSP generator internally and will include it in the next STM32 BSP release.

You can also add it to the latest 2021.02 BSP by extracting the following file into the BSP directory: https://sysprogs.com/files/tmp/mbedtls.7z

 

[support]

Hi,

Most likely, you are using a MinGW toolchain that has not been tested with TinyEmbeddedTest. Please try using our MinGW toolchain instead.

[support]

Hi,

Based on the description you provided, OpenOCD or gdb likely exits unexpectedly and hence VisualGDB ends the debug session.

We would advise checking OpenOCD logs and GDB logs for anything that could explain what is causing the session to end. You can find more about various diagnostic logs in the following pages:

• https://visualgdb.com/documentation/troubleshooting/logs/
• https://visualgdb.com/support/logsubmit

[support]

Thanks for renewing your license. Regarding the installation issues, please see the following page: https://visualgdb.com/documentation/troubleshooting/install/

Regarding other issues, we can gladly investigate them, however we would need to know the steps we could follow to reproduce them on our side. Please follow our problem reporting guidelines and share the steps (including all relevant screenshots) to reproduce the issues from scratch and we will look further into it. For better tracking, we would advise creating a separate forum thread for each issue.

[support]

Hi,

We generally cannot advise STM32-compatible devices that are not manufactured by ST (or for ST) to our users due to the following concerns:

1. Many of the components of the ST software library are published under this license, that explicitly limits it to ST devices:
   

   This software or any part thereof, including modifications and/or derivative works of this software, must be used and execute solely and exclusively on or in combination with a microcontroller or microprocessor device manufactured by or for STMicroelectronics

   We are aware that some of the vendors provide their own software libraries, however the original ST libraries compatible with the genuine ST devices offer a wider selection of components, examples and libraries. Hence, we recommend using the original ST devices instead.

2. We did a brief research on the availability of the ST-compatible devices on major distributors (DigiKey and Mouser). At the time of checking, they did not carry any of the devices we checked.
3. We considered adding support for the STM32 Blue Pill board to Analyzer2Go some time ago and ran a few stress tests on some of the boards. As a result, the boards we tested stopped working. We did a brief online search involving the part number on one of the boards and found a few posts warning about the ST clones.
4. Comparing Google Trends for STM32 and some of the compatible device families showed a heavy bias towards the STM32-related search inquiries. We concluded that focusing on improving the STM32 integration will make our product relevant to a larger user base, than adding support for STM32-compatible devices not manufactured by ST.
5. We believe that the STM32 devices gained their popularity due to exceptionally well-designed and maintained software libraries, examples and configuration tools. As these tools are available free of charge and are funded by the sales of the genuine STM32 devices, and as an official ST partner, we believe it would be fair to advise our users to use the genuine STM32 parts.

After carefully reviewing the factors mentioned above, we decided to not officially support them. That said, VisualGDB is very flexible and offers various workarounds in case you would like to target the devices that are not supported officially:

1. VisualGDB is fully integrated with the IAR and Keil compiler, so you can simply install it and pick it in the Embedded Project Wizard if you would like to target a device not directly supported by VisualGDB.
2. You can also try creating a project manually as shown in this tutorial. This will also work with any device that is not directly supported by VisualGDB, but is based on a supported core (e.g. ARM).

• This reply was modified 4 years ago by support. Reason: clarified the reasons for not supporting the devices

[support]

No problem, we will be happy to help you, however, we would kindly ask you to renew your technical support first via the following link: https://sysprogs.com/splm/mykey

[support]

Hi,

Most likely, you are still using the SDK imported using the old VisualGDB version. Please try deleting the entire SDK folder, and also the project, and re-creating everything from scratch.

[support]

No worries. CMake has several advantages to any other build system we are aware of, and is actively maintained, so we wouldn’t expect it to disappear anytime soon.

On the VisualGDB side, it is now the main and the recommended build system for embedded projects because because of the great separation of project-level, target-level and platform-level settings it offers.

[support]

Hi,

Indeed, the v2.9.1. internal format has slightly changed and won’t work with VisualGDB 5.5R4. We have fixed it on our side in the following build: VisualGDB-5.6.1.4033.msi (it will also go into the v5.6 Beta coming out this week).

[support]

Sorry, we do not have any plans for supporting the Chinese clones of the ST devices. If you would like to get reliable development experience, please consider purchasing a genuine ST device and a genuine VisualGDB license.

[support]

No worries. We ask users to confirm/renew support for issues that require investigation on our side. Raspberry Pi Pico is getting a lot of attention recently, and we are working on supporting it anyway, so we are happy to share the latest preview build with anyone interested in trying it out.

[support]

Hi,

You can try this build: VisualGDB-5.6.1.4033.msi. It has partial for the Pico SDK (allowing to clone and build projects), but debugging still needs to be configured manually (you can use this OpenOCD executable with the official Raspberry Pi scripts) and the GUI for editing the PicoSDK configuration variables won’t apply them yet. The official release with the missing functionality added is expected next week.

 

[support]

Hi,

This is correct. The Advanced CMake Project Subsystem reuses the same set of settings for multiple targets and configurations, so the custom action lists will run for all configurations.

To make it easier to support your scenario, we have added a “condition” parameter to the “Reference a reusable action list” action. E.g. you can set it to “$(Configuration)” = “Debug” to only run the reference list when building/debugging the Debug configuration.

Please try this build: VisualGDB-5.6.1.4033.msi

[support]

This happens because the build fails due to an error shown on the screenshot. Most likely, your Visual Studio process does not have permissions to create symbolic links. Please try running Visual Studio as administrator.

[Author]

Posts