[support]

Hi,

Thanks for confirming this. ESP8266 and ESP32 devices are relatively new and the debugging experience is often unreliable. Knowing the limitations, it is usually possible to get meaningful debug sessions, but the usability is unfortunately never near the ARM-based devices. VisualGDB tries to address some of the issues like disabling watchdogs and programming SPI FLASH, but there are unfortunately still many missing pieces.

[support]

Hi,

You can always explicitly specify which linker script file to use via VisualGDB Project Properties. As long as it is specified, including .lds files in the project should not affect anything.

[support]

Hi,

The options shown in the tutorial were added to the new profiler package released just before 5.2R8. Please install it via Tools->VisualGDB Package Manager->Updates.

The new package also adds an option to exclude the sampling profiler code, so you won’t need to modify the code anymore.

[support]

Hi,

Please try adding them to Solution Explorer.

[support]

No problem, the -s switch should be supported on all systems, so we have switched VisualGDB to using it. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.14.1376.msi

[support]

Hi,

Looks like your project includes files meant for the IAR compiler (IAR\ARM_CM3\portmacro.h). Please double-check the list of imported files and the preprocessor macros and ensure that only files meant for GCC are included.

If you are using Clang IntelliSense, you can quickly check why a certain file was included by opening it in Visual Studio and checking the bar on top of the source file. It will show the source file that includes the header and the entire inclusion stack.

[support]

Hi,

Thanks for reporting this, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.14.1375.msi

[support]

Hi,

VisualGDB does not cache the headers from the WSL, instead it configures the IntelliSense to directly look inside the WSL directories.

If you are using CMake on WSL, you may be affected by a bug that prevents VisualGDB from querying CMakeLists.txt properly. If this is the case, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.14.1375.msi

[support]

Hi,

We have rechecked the sample project and it had 2 references to the system_stm32f0xx.c file: one from the BSP and another one from the STM32CubeMX project.

Please remove the reference to the one from the BSP via VisualGDB Project Properties -> Embedded Frameworks -> Default System file, then rebuild the project (Build->Rebuild All). This should get the build to work.

[support]

No problem. Let us know if you need advice on interpreting the section offsets/sizes.

[support]

Hi,

We had it available as an option and less than 1% of our users actually enabled it (still causing troubles due to spamfilters). Sorry.

Regarding the on-page notifications, you can get a brief overview of the recent replies by clicking on your username near the post and then selecting “topics” (e.g. https://sysprogs.com/w/forums/users/bmcdonnell_psi/topics/). Each topic will show the last post time.

We understand that this may not be the most usable way to display topics and updates, but due to priority constraints we have to rely on the existing forum engine without doing serious modifications to it.

[support]

Hi,

Sorry for the delayed reply. We have reviewed the process of making a custom cycle counter driver for real-time watch and profiler and published a detailed tutorial here: https://visualgdb.com/tutorials/profiler/realtime/cyclecnt/

Let us know if you encounter any troubles with it.

We also recommend updating your profiler package via VisualGDB Package Manager and using the latest pre-release build of VisualGDB: http://sysprogs.com/files/tmp/VisualGDB-5.2.14.1374.msi

[support]

Hi,

Thanks, we have fixed it in this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.14.1374.msi

[support]

Hi,

Unfortunately the Visual Studio extensibility API cannot handle variables in .cpp file paths properly, so VisualGDB has to use relative paths with the user name.

It will automatically update those paths if you open the project on a different machine where the paths are different. Another option would be to relocate the BSP to a location under the source control (see this tutorial). Then VisualGDB will use relative path to that location.

[support]

Hi,

Most likely something went wrong with the alignment and one of the sections ended up not being aligned properly. Running “arm-eabi-objdump -h <ELF file>” and checking the section addresses and sizes could explain what could be wrong.

[Author]

Posts