Forum Replies Created
-
Posts
-
Hi,
GCC has rather non-trivial rules for passing libraries to the linker. VisualGDB provides convenient GUI for managing these parameters, and can automate some routine tasks, like searching nearby libraries for unresolved symbols, but it cannot replace the understanding of how the C++ linking works.
Feel free to check this page for an explanation of how various VisualGDB settings are mapped to the linker parameters. We would also advise studying the GNU linker documentation related to the handling of symbols and libraries. It is rather complex, but it will help get reliable results in the long term.
Hi,
No problem. We have updated VisualGDB to show the toolchain-level settings (e.g. newlib) via VisualGDB Project Properties -> Embedded Project for STM32CubeMX projects. It now works the same way as for the regular projects.
Please feel free to try the following build: VisualGDB-5.6.1.4073.msi. This will also be included in the upcoming VisualGDB 5.6 Beta 2.
Hi,
Most likely, your Windows port ended up missing some of the parts required by the Windows platform. We can gladly review your project and point out what is causing the issues as a part of our consulting services. Feel free to forward it to us and we will give you a quote.
Alternatively, please try following our simulation platform tutorial. Make sure you select the device, toolchain and other options exactly as shown in the tutorial, and you should be able to get a usable project that includes all the necessary parts. You can then use it as a reference to fix the errors in the current project that doesn’t build.
Hi,
No problem. The EFP.XML file is a reflection of the EmbeddedFrameworkPackage type from the BSPEngine assembly. You can try opening one of our open-source BSP generators and navigating to the definition of EmbeddedFrameworkPackage to see a full list of members.
You can find some basic documentation on the BSP and framework mechanism here: https://github.com/sysprogs/BSPTools/wiki
Generally, if you are planning to heavily invest into making multiple frameworks for your environment, we would advise cloning one of our open-source BSP generators and stepping through its logic of generating the BSP. E.g. the CC3220 generator relies on a relatively small SDK and produces a BSP with many frameworks. You can then make a similar generator for your own BSP, or modify it to just generate framework definitions (in BSP generators, the frameworks would end up inside the BoardSupportPackage object, while in framework packages they would be placed under EmbeddedFrameworkPackage).
If you are looking to create a relatively small and simple framework, the easiest way would be to download our advanced semihosting and profiler framework, and create your own one by modifying its EFP.XML file. The definition of the profiler framework uses most parts of the framework engine, so it could be used as a good starting point.
Hi,
Please note that our support is limited to VisualGDB issues only. Based on the information you provided, VisualGDB is working as expected – the compiler reports a build error and VisualGDB displays it.
Please note that we receive a large volume of inquiries asking to help troubleshoot a specific project, port a library to a different device, or fix a build error, and are not able to investigate them without directly billing the users for the time required to do that.
Hi,
@arrow201, thanks for pointing this out!
@Southbranch, good to know it works. BTW, you can find other mbed tutorials using the mbed tag in our tutorial system.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.
