Forum Replies Created
-
Posts
-
Hi,
Please try following this tutorial for diagnosing library-related problems. For CMake projects, you can find the library-related settings under VS project properties for specific targets (e.g. for your main executable).
Most likely, you have edited some files or configuration entries in the Arduino IDE to resolve this and did not change the VisualGDB configuration accordingly.
Unfortunately, without being able to reproduce the issue on our side (successful build with Arduino IDE and failing build with VisualGDB) it is not possible for us to offer any solution.
Our best advice would be to follow the Arduino Diagnostics Tutorial to compare the command lines used by the Arduino IDE and VisualGDB in order to narrow down the configuration difference.
Sorry, this is way too specific and won’t be of much use for most of our users. In order to keep our product prices reasonable, we focus on features that would appeal to many of our users at the same time. Hence we are not able to add functionality that has very limited use, as we have a backlog of features that would bring productivity improvements to a much larger group of users. Hope this explains and sorry we could not help.
Hi,
Most likely, you are not using the VisualGDB build engine to build the project. Just building the code with the –coverage flag will introduce immense memory overhead, so VisualGDB does some advanced pre-link patching to move most of the coverage logic to the PC side. Please try creating an MSBuild-based projects and check with it instead.
Alternatively, please try running the following command line after compiling the code, but before linking it:
VisualGDB.exe /decover <full path to the ELF file> <full paths to all .o files>
Then re-link your ELF file as usual. This will greatly reduce the memory overhead caused by the code coverage.
We are also preparing a tutorial showing the related settings and best practices. Feel free to follow us on Twitter to get notified once we publish it (or simply check our tutorials list next week).
Hi,
This is already supported via ESP-IDF components. Please refer to the ESP-IDF documentation or VisualGDB tutorials for details on managing the ESP-IDF components.
Sorry about that. We have just caught this with our pre-release tests as well. Please try this build: VisualGDB-5.5.2.3410.msi
We have tried building the configuration you mentioned using Arduino IDE on a clean machine (Arduino IDE 1.8.10, Arduino Core for STM32 v1.7.0, stm32sleep cloned from Github, Generic STM32F1 Board) and it failed with the same error that you reported for VisualGDB:
fatal error: libmaple/gpio.h: No such file or directory
Hence it looks like the problem is caused by a specific 3rd-party library and not by VisualGDB.
Hi,
It looks like your technical support has expired. In order to continue receiving technical support, please renew your support here: https://sysprogs.com/splm/mykey
Hi,
Depending on the SDK you are using, the VTOR might indeed not get set explicitly (not all device SDKs support this). Setting it manually from your code (guarded with #ifdef sram_layout) should fully fix the problem through.
Hi,
It looks like some VisualGDB-specific files got corrupt. Please try uninstalling VisualGDB via the Add/Remove Programs window and installing it back from scratch (it will preserve your setting and license information).
If this doesn’t help, please follow the steps on this page: http://visualgdb.com/support/loadfail/
Sorry, we were not able to reproduce the problem. We have tried creating a new project from scratch using the new toolchain and it worked.
Most likely, the issue you are experiencing is caused by incompatibility between the toolchain and a specific project, or some corrupt files. Please consider posting the logs on the Espressif forum to get further help on this.
Just wanted to let you know that we have improved the BSP referencing logic in the following VisualGDB build: VisualGDB-5.5.2.3404.msi.
You can now use the VisualGDB Project Properties -> Embedded Project -> Shared Files -> Change button to switch between 2 modes of referencing a BSP:
- Using a global path shared between all projects
- Explicitly specifying the relative path to the BSP
Hope this helps. Let us know if you have any further suggestions/feedback.
Most likely, you are still using different library/hardware directories between VisualGDB and Arduino IDE.
Please carefully examine both command lines with the latest settings and make sure that the -hardware, -tools and -libraries flags match. If not, please adjust the flags used by VisualGDB via VisualGDB Arduino Settings until those flags match.
This looks like a warning from the ESP-IDF that expects an earlier toolchain version. It should normally not affect the build.
Either way, we have just updated our toolchain to include the latest fixes to ESP-IDF 4.0, that should also eliminate this message. You can re-download it from http://gnutoolchains.com/esp32/
