[support]

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).

[support]

This is already supported. Please refer to the VisualGDB Arduino tutorials for details.

[support]

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.

[support]

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

[support]

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.

 

[support]

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

[support]

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.

[support]

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/

[support]

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.

[support]

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:

1. Using a global path shared between all projects
2. Explicitly specifying the relative path to the BSP

Hope this helps. Let us know if you have any further suggestions/feedback.

 

 

[support]

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.

[support]

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/

[support]

Thanks for the log files. It looks like the hardware directories and libraries used by VisualGDB vs. Arduino IDE are indeed different. Specifically, the following options are used by Arduino IDE, but not by VisualGDB:

-tools C:\Program Files (x86)\Arduino-1.8.9\hardware\tools\avr 
-tools C:\Program Files (x86)\Arduino-1.8.9\portable\packages 
-libraries C:\Users\Ian\Documents\Arduino\libraries

The following options are used by VisualGDB, but not by the Arduino IDE:

-hardware C:\Program Files (x86)\Arduino-1.8.9\portable\packages\STM32\hardware 
-hardware C:\Users\Ian\AppData\Local\Arduino15\packages 
-tools C:\Users\Ian\AppData\Local\Arduino15\packages 
-libraries C:\Program Files (x86)\Arduino-1.8.9\libraries 
-libraries C:\Program Files (x86)\Arduino-1.8.9\libraries\u8g2\ 
-libraries C:\Program Files (x86)\Arduino-1.8.9\libraries\STM32duino-bootloader-master\Arduino_STM32-Drivers

Also the STM32 tools used by the Arduino IDE vs. VisualGDB are different:

C:\Program Files (x86)\Arduino-1.8.9\portable\packages\stm32duino\tools\stm32tools\2019.10.9

vs

C:\Users\Ian\AppData\Local\Arduino15\packages\STM32\tools\STM32Tools\1.3.0

If looks like you have tried adding some of the missing directories from the Arduino IDE to the VisualGDB settings and ended up with an incompatible combination of packages.

In order to fix this, please try deleting the %LOCALAPPDATA%\VisualGDB\ArduinoSettings.xml file and the %LOCALAPPDATA%\Arduino15 directory and restarting Visual Studio. Then open VisualGDB Arduino Settings and set the following:

1. Set the Arduino IDE directory
2. Add $(ARDUINO_ROOT)/portable/packages (without the STM32\hardware part) to Hardware Directories.

Do not add any library or tool directories. If the project still doesn’t build afterwards, please check the command line used by VisualGDB again. Its -hardware, -tools and -libraries flags should match the ones used by the Arduino IDE. If not, use the VisualGDB Arduino Settings to adjust them until they fully match.

If this still doesn’t help, please share the updated build log and we will provide further troubleshooting instructions.

 

[support]

Hi,

Most likely, the Arduino IDE and VisualGDB are using different library directories, preventing VisualGDB from locating them. We can help you resolve this, however we would need additional information from you.

1. Please capture the exact arduino-builder command line used by VisualGDB (it is shown in the build log after you build the project).
2. Please try using Process Monitor to capture the command line used by Arduino IDE to build the sketch. (note that the IDE will launch arduino-builder.exe several times with shorter command lines before the actual build).

Once you capture both command lines, please share them here along with a screenshot of the VisualGDB’s Arduino Settings and the list of additional library directories defined in the project settings (if any) and we will help you replicate the build results from Arduino IDE with VisualGDB.

[support]

Please try creating a new project from scratch. Please also update to VisualGDB-5.5.2.3403.msi​. This version will download missing packages when you open the project, given that it was fully loaded before (won’t help for projects that were never loaded with the new build).

[Author]

Posts