[support]

Hi,

VisualGDB would normally just use the “load” command to program the FLASH memory and would not issue any locking commands. You can find out the exact commands used by VisualGDB by creating a gdb log file. You can try passing additional commands to the gdb stub (using the “monitor <command>” syntax) by expanding the “Advanced Settings” view under VisualGDB Project Properties -> Debug Settings. See the J-Link documentation for a list of monitor commands related to memory protection.

If nothing helps, please consider checking with Segger support. They might be able to suggest a command for controlling the FLASH memory erasing.

[support]

Hi,

Please try updating to the latest VisualGDB 5.5 (you may need to renew your key here). If the problem persists, please collect and attach a gdb log file as shown here and we will investigate this further.

[support]

Hi,

This is to be expected. The STM32CubeMX tool generates Plain C files, so placing C++ code in them will result in errors. You can still add .cpp files to the STM32CubeMX-generated projects as shown in our STM32CubeMX tutorial, however it will require carefully partitioning the code into Plain C and C++ parts, and declaring the functions that need to be visible from both parts with extern “C”.

As an alternative, please consider using the regular VisualGDB Embedded Project Wizard that can generate a C++ main file instead.

[support]

Please note that we prioritize the reported issues based on the amount of affected users. As this issue does not affect other users, we will not be able to provide any further help with it. If you are not able to continue your VisualGDB trial due to it, please consider using other tools as we will not be able to address it at this point.

[support]

Thanks for your feedback. We have added it to our internal issue tracker and will investigate it further if the issue is confirmed by other users.

[support]

Hi,

These files should normally be a part of the toolchain and should be located automatically. If they don’t work, most likely either toolchain, or the project is corrupt.

Please try reinstalling the toolchain via Tools->VisualGDB->Manage VisualGDB Packages. If it doesn’t help, please try reproducing the problem on a project created from scratch.

[support]

Thanks for confirming your support status. You can turn off unsupported encoding hints using the “Show Unsupported Encoding Hints” setting under Tools->Options->VisualGDB, as long as you are using the latest VisualGDB 5.5R2. See this page for the exact and up-to-date path of the setting.

[support]

No problem, we will clarify. VisualGDB supports many different project types. Some of them (like MSBuild or Advanced CMake) are recommended for new setups, while others (like Makefile-based) are considered legacy and are only recommended if you need backward compatibility with older VisualGDB versions, or projects that were created earlier.

[support]

No problem. This looks like a legacy VisualGDB project type that is internally implemented as a NMake-based VC++ project. You can try narrowing down the problem by creating a regular VC++ Makefile project via the VC++ project wizard and setting a dummy build command (e.g. “cmd /c echo done“). If it breaks the same way, please try checking with Visual Studio support.

If the VisualGDB-based project behaves differently from the regular NMake project, please try comparing and merging the .vcxproj files. Some element (e.g. PlatformToolset) could be set differently in these 2 projects and could be causing this behavior.

Also, for most of the new project setups we recommend using Advanced CMake projects. They do not require the VC++ project subsystem and often work more reliably.

[support]

Hi,

Thanks for reporting this. We have reproduced and fixed the issue. Please try this build: VisualGDB-5.5.102.3881.msi

[support]

Hi,

As the message suggests, ninja expects to be run as root on Raspberry Pi.

You can configure Raspberry Pi to permit root logins as shown here and then create another SSH connection in the VisualGDB wizard or project properties (root@raspberrypi instead of pi@raspberrypi).

[support]

Thanks for the update. VisualGDB does show a clear message when the trial expires, as long as you do not modify any components or registry keys. Manually editing licensing-related keys will indeed suppress the expiration message, but will still prevent VisualGDB from working.

[support]

Sorry, it looks like some of the files are corrupt on your side. Unfortunately, this is outside of our control and hence we are not able to resolve it from our side.

[support]

Please make sure you use an unmodified VisualGDB installer and do not modify the downloaded packages in any way either. As long as both VisualGDB and the packages are not modified, the installation will work out-of-the-box in both online and offline modes.

[support]

No problem, please try replacing the SysprogsUnitTestInterface.c inside the toolchain with the updated version from the VisualGDB directory. This should fix the setting check.

[Author]

Posts