Forum Replies Created
-
Posts
-
No problem, please let us know the email address associated with your license key, so that we could check your support status.
Hi,
This would involve manually editing the CMakeLists.txt files created by VisualGDB. You can generally use the if (SIMULATION) syntax to make sure that a certain part of the CMake script will only be relevant to the simulation platform, or vice versa. E.g. you could define different versions of the same library for simulation vs. hardware, or 2 different versions of the statement that references common libraries.
That said, editing the project structure via Solution Explorer will ignore the parts of CMakeLists.txt that are currently inactive, that may lead to build errors later. We can only recommend this for users familiar with CMake semantics that are OK editing the generated scripts manually and troubleshooting possible errors later. If you would like to rely solely on GUI, please try using #ifdef SIMULATION in the code instead.
Sorry, we are currently prioritizing a few other features over it. We will post an update here if we get more concrete plans for releasing an SDK.
Hi,
This looks like an IPv6/IPv4 issue. Please try specifying “127.0.0.1” or instead of localhost, or using the IP address from another network interface.
Hi,
No problem, indeed the header file list from the Pico SDK directories was overriding the header list from the target directory. We have fixed it in the following build: VisualGDB-5.6.1.4074.msi
Hi,
Thanks for pointing out the subdirectories. We have rechecked it and indeed, one of the cases with subdirectories in project samples was not handled correctly. Please try this build: VisualGDB-5.6.1.4074.msi
In order to use the Fast Semihosting and Profiler framework with FreeRTOS, please make sure that the BSP defines the USE_FREERTOS macro and adds the directory containing FreeRTOS.h to the include search path. The easiest working example of it would be the STM32 BSP (search for AdditionalIncludeDirs and AdditionalPreprocessorMacros in the BSP.XML file).
No problem, we have merged the new thread with the old one.
The “multiple definition” error is expected if STM32CubeMX provides its own definitions of the semihosting-related functions that conflict with the toolchain-provided ones. In order to use the implementations enabled via VisualGDB Project Properties, you would need to remove other conflicting implementations from the project, either by patching the STM32CubeMX-generated sources, or by changing the STM32CubeMX configuration.
Hi,
We would advise comparing the sample definitions with the existing BSP (where the examples work). E.g. you can copy a single sample project from the regular BSP, make sure it works, and then modify it, one step at a time, to match the custom example you would like to ship with the BSP. If you verify that the examples work after each step, you can easily find the step that causes the build errors.Hi,
Good to know it works. BTW, we do have a couple of tutorials explaining extern “C” and the generic “undefined reference” error:
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.
