[support]

Thanks for sharing this. Yes, our internal BSP build is somewhat usable, although a few example projects from Nordic use library settings that were not present in the previous SDKs, so we are making sure that VisualGDB can clone them properly. We also understand that it took us longer than usual to process this, so we will give a higher priority to supporting the next Nordic SDK so it won’t take that long.

[support]

Hi,

The Preview Changes dialog is actually rendered by Visual Studio based on the data VisualGDB reports to it, so the amount of tweaking we could do to it is limited.

That said, reference highlighting was indeed broken in the latest VisualGDB 5.4R2, so we have fixed it in this build: VisualGDB-5.4.103.2810.msi

[support]

Hi,

Yes, we are currently running internal tests on it and expect to release it in a few next weeks (there have been non-trivial changes to the Nordic samples).

[support]

No problem and good to know it works. FYI: we are updating our installer to support VS2019, so we will try to improve the detection of multiple VS2017 installations as well.

[support]

Hi,

Please let us know whether the VisualGDB.pkgdef file mentioned in step 7 of the diagnostic instructions exists and whether the registry value mentioned in step 8 is set correctly.

[support]

Look like something on your computer is preventing VisualGDB from running the Arduino builder properly.

Please double-check that your antivirus is not blocking the following file:

C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino\arduino-builder.exe

If it doesn’t help, please open View->Other Windows->VisualGDB Diagnostics Console, reproduce the problem and share the log from the console.

[support]

Hi,

The Makefile itself does not get overwritten (it is part of the VisualGDB’s design to do small and very focused edits to the Makefile itself so that our users can edit it to modify the build logic), however the auxiliary files (e.g. stm32.mak) do get overwritten. As long as you edit the files that do not have the “THE FILE WILL BE OVERWRITTEN” warning, you should be on the safe side.

[support]

Hi,

According to our records, your trial has started considerably earlier (see your previous forum account). We are happy to help users that have active VisualGDB licenses, or are evaluating VisualGDB (i.e. running the 30-day evaluation period to decide whether it could be useful in their environment), however we are not able to provide any help outside of these constraints. If you are looking for a free IDE/code editor that does not come with any limitations, please consider using Vim, Emacs or Eclipse.

[support]

According to our records, your trial has expired, so unfortunately we won’t be able to provide any further support unless you purchase a VisualGDB license. Sorry.

[support]

According to our records, your trial has expired, so unfortunately we won’t be able to provide any further support unless you purchase a VisualGDB license. Sorry.

[support]

Hi,

It looks like your system sets the %AS% environment variable to the default x86 assembler and the Makefile picks it up. Please try locating the following code in your Makefile:

ifeq ($(AS),)
AS := $(CC)
ASFLAGS := $(CFLAGS) $(ASFLAGS)
endif

Once you locate it, simply make it unconditional (remove the ifeq and endif lines). This will override the incorrect value inherited from the environment.

[support]

Hi,

We were just going to suggest that option, but it looks like you were faster. In case anyone else searches for this, the option is called “Group sources by paths” and is available for CMake-based, ESP-IDF-based and Arduino-based projects.

[support]

Hi,

The automatic sysroot synchronization indeed can only download the files from the root of the target filesystem. The easiest way to work around it would be to synchronize the files manually using SmarTTY, or add custom project shortcuts (requires Custom edition or higher) for downloading the arbitrary directories from arbitrary machines into the toolchain’s sysroot. Once defined as a custom shortcut,  you will be able to trigger synchronization via the Project menu.

Regarding the case sensitivity, such files will indeed override each other on the Windows side. You can try enabling the case-sensitive mode for a specific NTFS folder as described here, but this may not be handled correctly by the toolchain or Visual Studio itself. Generally, unless you are building custom kernels, this should not be a problem as this type of file name collisions is rare. If it does interfere with your projects, please consider creating an Advanced CMake-based project configured to directly access the remote filesystem via SSH. This mode will properly handle case-sensitive file names, although you would need a Linux machine to build the code.

[support]

Thanks for the update. Looks like the busybox version on your target is more limited than one we tested.

The problem happens because VisualGDB tries to run the following command line in order to list all files in a certain directory:

find . -maxdepth 1 -print0 | xargs -0 stat -c "StatEntryL:|%N|%Y|%d|%s|%f"

It uses the ‘-0’ option so that xargs won’t get confused if some of the file names have spaces. We have tested this on busybox 1.27.2 and it did work, so if possible, please try updating the busybox version on your target. If this is not possible, please try running ‘xargs –help’ on your target and share the output so that we can try to find a command line that will work on your target.

[support]

Hi,

Please double-check with Espressif (the vendor for ESP-IDF) whether there is an officially supported and stable way to do this. If yes, we will be happy to add a GUI setting for it.

[Author]

Posts