[support]

OK, which of the boards are you using? The one with AVR microcontroller or the ARM Cortex-based one?

[support]

Sure. Let us know once you have further information.

[support]

Hi,

Normal VC++ projects don’t automatically add files from the file system and VisualGDB is trying to follow that behavior.

We could add a command to rescan the files and update the project similarly to the Import Directory Recursive command. Would that be helpful?

[support]

Hi,

Please try the following build:http://sysprogs.com/files/tmp/VisualGDB-5.1.4.650.msi
Then open a VisualGDB project, launch the toolchain testing and send us the contents of the VisualGDB Launcher Output view from the Output window. It should ​contain detailed log messages explaining the gdbserver location logic.

[support]

You can modify your makefile as follows to support per-file flags

1. Modify the file rule templates to include file-specific variables:

$(CXX) $(CXXFLAGS) $($(basename $(notdir $<))_FLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep)

2. Add file-specific flags defines above the FileSpecificTemplates line:

LEDBlink_FLAGS := -O0

You can modify the $(basename $(notdir …)) expression to use the directory name instead of the file name. See the GNU Make function reference for more details.

You can similarly add the “include” lines to the Makefile to include your own files containing lines like “CFLAGS += some_flag”.

[support]

Hi,

As of v5.1, VisualGDB only supports profiling for barebone targets like STM32. We do consider adding Linux support in the future versions. We will announce through our Twitter once it is available.

[support]

Hi,

The checkbox results in defining the USE_HAL_LEGACY macro that enables some backward compatibility features in the HAL headers. You can search for the macro in the HAL headers and sources to see which exact functionality is affected.

[support]

OK, we’ve added this to the preliminary feature list of v5.2

[support]

Hi,

You can replace the CppEngineCore.dll file with a debug build from http://sysprogs.com/files/tmp/CppEngineCore.dll, create a dump file via Task Manager and send it to us. This way we should be able to see what is causing the crashes and fix them.

[support]

Hi,

This happens because _nop()  is not a GCC compiler extension and VisualGDB IntelliSense does not know about it.

You can work around it by adding something like #define _nop() to gcc_compat.h in the VisualGDB directory. The definition will only affect IntelliSense, so the code will be compiled the same way as before.

[support]

Good to know it works. If you encounter further problems, let us know.

[support]

Hi,

The answer depends on the board type. Is the board based on Linux, or is it running barebone firmware?

[support]

Yes, there was a small bug in our Github repository. Please update your git checkout and try again.

[support]

Hi,

Please find the answers to your questions below.

We did not explicitly test ESP8266 with Atmel-ICE. You can try it at your own risk by specifying the corresponding interface script to OpenOCD, but we cannot guarantee that it will work.

The source code of the ESP8266 library is not provided by Espressif, so it’s not a limitation of VisualGDB.

Yes, the embedded edition is enough for ESP8266.

[support]

Hi,

When you are creating an mbed project, VisualGDB uses the files from the official mbed distro on github. Perhaps the file is named differently there? Can you find a BLE example specifically for mbed?

[Author]

Posts