Forum Replies Created
-
Posts
-
Hi,
This is a known bug in the STM32CubeMX generator. It doesn’t properly escape the “&” symbol in the generated XML files (i.e. produces “value1&value2” instead of “value1&value2”). The easiest workaround would be to patch the file manually before importing it into VisualGDB.
Please also consider reporting this to ST, as the issue is on their side.
Thanks, we have reproduced the problem and fixed it in the following build: VisualGDB-5.5.5.3599.msi
Let us know if you encounter further issues and we will be happy to help.
Hi,
No problem, we have a very detailed tutorial on creating custom projects that are not directly supported: https://visualgdb.com/tutorials/arm/legacy/
We have also open-sourced our tools for generating BSPs, so you can simply fork one of the similar BSP generators here: https://github.com/sysprogs/BSPTools/
Alternatively, we can do the necessary research and create a BSP based on your requirements as a part of our paid BSP program. Feel free to contact our sales if you would like to get a quote.
OK, we have updated VisualGDB to work with the latest MCUXpresso SDK: VisualGDB-5.5.5.3597.msi
For multi-core devices, it will create a separate device entry for each core (e.g. LPC55S69_CM33_CORE0), so you can choose a specific core when creating a project.
Please note that the example you mentioned (lpcxpresso55s69_host_suspend_resume_hid_mouse_freertos) does not build under the MCUXpresso IDE due to an error in the SDK definition. It will also not build with VisualGDB unless you manually resolve the build errors (same way as with the MCUXpresso IDE). Examples that build with MCUXpresso IDE will also build with VisualGDB.
Please refer to the regular Visual Studio documentation for steps on creating multiple projects in the same solution, they will work with VisualGDB as well.
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.
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.
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.
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?
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.
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.
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.
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.
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.
