Forum Replies Created
-
Posts
-
Hi,
Indeed, the only way to create stand-alone frameworks currently is to clone an existing framework from the BSP. If you are using a device family that does not include any frameworks, please consider creating a temporary project for a different device, cloning one of the frameworks there and editing it manually. We will try to add support for creating the frameworks from scratch to one of the next VisualGDB releases.
Hi,
No problem, please refer to the following page for a very detailed overview of custom frameworks, BSPs and other ways of managing shared code: https://visualgdb.com/documentation/embedded/bsps/
Sorry, we release multiple hotfix builds almost every day, and hence the older ones get replaced very fast. The new functionality is here to stay though – it is available in the Beta and will be available in the subsequent releases. If you are hesitant to switch now, we would advise simply waiting for the end of the project and getting the latest build available then – it will include this feature as well.
Hi,
This looks like an issue caused by the toolchain cache. Please try restarting Visual Studio, it should fix the issue.
Most likely, you have selected an incompatible combination of settings at some point.
We can help you understand what is going on if you could share the steps for reproducing the problem from scratch per our problem reporting guidelines. Please make sure the steps include entire uncropped screenshots of all the relevant windows as shown in the “screenshots” section of the guidelines.
Hi,
No problem, please see the following page for a detailed explanation of formatting-related settings: https://visualgdb.com/documentation/intellisense/
Hi,
You can find the registration key used by VisualGDB in registry (HKEY_CURRENT_USER\SOFTWARE\Sysprogs\VisualGDB\Settings\RegistrationKey).
However, please note that it your support has expired a few years ago, the latest VisualGDB version will not work with your key, and the older version may not support the latest VS. You can find out more on the following page: https://sysprogs.com/splm/mykey
Hi,
According to our records, your trial period has expired. If you would like to continue receiving support, we would kindly ask you to purchase a license. If your need more time to evaluate VisualGDB, please feel free to contact our sales from your corporate email address, and we will be happy to help you and your team get everything working in no time.
Hi,
There is no special API for sending timestamps via semihosting. As the DWT_CYCCNT register is a part of the ARM core and not part of VisualGDB, it is not covered by our support. Please refer to the ARM documentation for more details.
For a more high-level solution, please consider using real-time watch instead.
Regarding the integration tests, simply pressing the “delete” button on the selected test should work.
Sorry, the “undefined reference” is not something specific to VisualGDB. It’s an error shown by the linker if the project does not include definitions (not declarations) of the referenced symbols. The best thing we can offer via our regular product support is the 2 tutorials linked above. They explain the differences between the definitions and declarations in detail. We would advise taking time to follow them and go through the diagnostic steps described there, as it will help you get a better understanding of the logic behind handling of references.
If you believe the issue is on the VisualGDB side, please try reproducing it from scratch (including creating a new project) and documenting every step. If you could share all the steps with the relevant screenshots, we can try to pinpoint the most likely cause of the issue.
We can also review your specific project and point out the locations of the declarations/definitions of the symbols, and adjust the settings to include all the necessary files, however as it’s something specific to the project, we would have to charge a consulting fee for it. Feel free to contact our sales if you would like to get a quote.
Hi,
The trial period is indeed 30 days. However, according to our records, it has previously expired. Please note that re-downloading/reinstalling VisualGDB does not restart the trial period.
Hi,
No problem, please see the following tutorial for a detailed explanation of the “undefined reference” errors: https://visualgdb.com/tutorials/linux/libraries/diagnosing/
There is also another one that explains a similar issue for the embedded projects: https://visualgdb.com/tutorials/tips/externc/
According to our records, your trial period has expired. If you would like to continue receiving support, we would kindly ask you to purchase a license. If your need more time to evaluate VisualGDB, please feel free to contact our sales from your corporate email address, and we will be happy to help you and your team get everything working in no time.
Hi,
No problem, we can help you. However, we would kindly ask you to confirm your support status first. Please let us know the email address associated with your license key and we will link it to your support profile.
Hi,
Sure, you can sue the regular Embedded Project Wizard to either create a basic “LEDBlink” project, or to clone one of the STM32CubeMX samples. This requires the regular Embedded Project Wizard (not the STM32CubeMX Project Wizard) and does not involve any external tools.
You can find more details in the following tutorial: https://visualgdb.com/tutorials/arm/stm32/
