Forum Replies Created
-
Posts
-
Good to know it works. Generally VisualGDB reconstructs the ESP-IDF project structure from analyzing the build logs, so if you get the “ESP-IDF build log did not report any built executables” error, trying to build the project would either resolve it (it if previously failed due to missing generated files), or point directly at the cause of the problem (i.e. a meaningful error message produced by the ESP-IDF build system).
The USE_FULL_LL_DRIVER is just a regular preprocessor macro, so you can easily set it via the regular build settings as shown below:
Regarding the automatic fix, if anyone could share the exact up-to-date repro steps for the issue and point out which files or flags need to be included, we should be able to add a workaround on our side in 1-2 business days. Otherwise, it will go into a lower priority queue, since it involves issues in 3rd-party components and we currently working on a few improvements to VisualGDB itself (specifically, stable VS2019 support and eliminating delays during VS startup).
No worries. If 2 very similar projects behave differently, it might be caused by an internal exception in VisualGDB while it’s handling a different part of the startup sequence. Please check View->Other Windows->VisualGDB Diagnostics Console for details.
If this doesn’t reveal anything, please try combining different parts of working and broken project (e.g. .vcxproj file from project A with .vgdbsettings file from project B, or <Build> element from project A with the <Debug> element from project B inside the .vgdbsettings file). This should help narrow it down fairly easily.
Hi,
The linkerinputs page indeed uses old screenshots, however it still reflects the structure of the GCC’s linker inputs and does not apply to Keil projects (since the Keil compiler has its own documentation and support, we would advise checking it first).
The errors look like the Keil compiler is missing some target-specific flags. Please try enabling the “generate .bat file” option in the uVision GUI, build the project and check the armcc command lines in the generated bat file (they will refer to reponse files with the actual command line parameters). Then check the command-line options used by VisualGDB by viewing the .gcc.rsp files in the VisualGDB\Debug subdirectory. If you could identify a specific flag that is different between uVision and VisualGDB, please either add it via VS Project Properties -> C/C++ -> Command Line, or let us know and we will see why VisualGDB doesn’t add it automatically.
If you cannot find the difference between the 2 projects, we would need to know the exact steps to reproduce it on our side so that we could check what is going on.
This looks like a known issue. It should not trigger in v5.4R2, however it would be present in some of the daily builds after it. We are currently refactoring the initialization logic of VisualGDB to make different components initialize on-demand and completely eliminate any delays during Visual Studio startups, so some of the daily builds were indeed buggy.
Please try this one, it has the breakpoint problem fixed: VisualGDB-5.4.103.2958.msi
Sorry, we do not support 8051 devices as they do not have a GCC/GDB-based toolchain and are not as popular as ARM-based devices.
Sorry, this doesn’t look like any known issue. If you could provide the exact repro steps for the problem, we should be able to tell what is going on.
Good to know it works. If you encounter any further issues, don’t hesitate to create another topic and we will be happy to help.
Hi,
The CC2530 device is indeed not supported out-of-the-box as it is not as popular as other devices. As a workaround, please follow our legacy device tutorial to setup a project manually.
It looks like your VisualGDB installation might be corrupt. Please share a screenshot of the Help->About VisualGDB window so that we could see what is going on.
The extensions.hpp file is likely included from a different file.
Please try this build: VisualGDB-5.4.103.2946.msi
Please check if the error is shown when opening one of the .cpp files, not the .hpp file, then switch the Clang IntelliSense Diagnostics Console to Projects view and click the “Save” button:
It will dump the IntelliSense state of all projects to an XML file. Please attach it here (or send it via our support form) and we will help you get this to work.
No problem. Please refer to the STM32 documentation for the description of the instruction sets supported by the STM32 devices and to the GCC documentation (and ARM Cortex core documentation) for differences between Thumb-1 and Thumb-2.
In VisualGDB 5.4R2 and earlier, the settings derived from the CPU definition override the settings in the project properties. We have reversed this behavior in the upcoming R3 (you will be able to override the CPU settings via the regular MSBuild pages), however it should not be critical in this case case the STM32 devices do not support the ARM (non-THUMB) instruction set.
Hi,
The ESP32 debugging is generally less reliable than for ARM devices, so glitches like this one are expected. As it is something caused by the low-level interaction between the ESP32 chip and the Espressif’s port of OpenOCD, please consider asking on the Espressif’s forum. They might be aware of the issue and might be able to suggest some specific workaround.
