- This topic has 3 replies, 2 voices, and was last updated 2 years, 7 months ago by
.
-
Posts
-
Hello to all. I started experimenting VisualGDB to import an existing Keil project (I don’t want to pay anymore for a Mikrovision IDE license which is killing my budget insanely) . So here I am ! For this first import, my only problem resides in a type mismatch on the ARM library ‘__value_in_regs’. This is the error I get :
In file included from C:/Users/Utilisateur/Desktop/SP100-Final/SP100-Final/mbed-src/targets/cmsis/TARGET_STM/TARGET_NUCLEO_F072RB/TOOLCHAIN_ARM_MICRO/sys.cpp:37:
../../../../Desktop/SP100-Final/SP100-Final/rt_misc.h:65:8: error: ‘__value_in_regs’ does not name a type
65 | extern __value_in_regs struct __argc_argvCan someone give me a clue on how to solve it?
SOLVED – I had to replace the deprecated ARM5 keyword ( __value_in_regs) by its ARM6 updated variant <code class=”hljs”>__attribute__((value_in_regs))
Hello. I get a compiling error on this variable, which appears not to be recognized/found by the compiler (after having imported and generated an STM32 KEIL project into GDB). Does anyone have a clue how to solve it… (File attached for a quick view).
Build log :
C:/Users/Utilisateur/Desktop/SP100-Final/SP100-Final/mbed-src/targets/cmsis/TARGET_STM/TARGET_NUCLEO_F072RB/TOOLCHAIN_ARM_MICRO/sys.cpp: In function ‘__initial_stackheap __user_setup_stackheap(uint32_t, uint32_t, uint32_t, uint32_t)’:
C:/Users/Utilisateur/Desktop/SP100-Final/SP100-Final/mbed-src/targets/cmsis/TARGET_STM/TARGET_NUCLEO_F072RB/TOOLCHAIN_ARM_MICRO/sys.cpp:45:25: error: ‘__current_sp‘ was not declared in this scope
45 | uint32_t sp_limit = __current_sp();Please note that VisualGDB is a productivity tool for software developers. It can make developers more productive by providing convenient GUI for common time-consuming tasks, and integrating various external tools into Visual Studio, so that they are always a few mouse clicks away.
We are able to offer VisualGDB at affordable price, because we focus on developing and supporting functionality that works the same way for multiple users, hence the development and testing effort is reused between multiple license holders.
We also receive a huge amount of inquiries asking to fix a specific broken project, help make the correct design choice, explain how a specific C++ feature works, or assist porting a library to a different platform. These inquiries require considerable effort to research and communicate the best solution. They do not scale between multiple users. I.e. helping one user solve this type of problem will not automatically help other users. It also does not help the same user avoid the same type of problem in the future. Hence, we are not able to address them within our regular support. If we included this type of help in our support, we would simply not have sufficient resources to provide it at the current license prices, or to allocate any resources to VisualGDB development.
We are happy to offer project-specific help via our consulting service per Zoom, TeamViewer or any other screen sharing service of your choice at our consulting rate and are happy to solve any problems our users encounter. This includes a detailed follow-up email at the end of the session, that includes an overview of the used techniques and a summary of solved problems and future recommendations.
Alternatively, please consider browsing our documentation and tutorials. Our documentation lists most VisualGDB settings, and the tutorials show how to use VisualGDB for in many real-world scenarios. Our technical support is limited to issues in VisualGDB itself, that can be reproduced from scratch per our problem reporting guidelines (i.e. do not depend on external projects that can potentially contain errors).
- You must be logged in to reply to this topic.