[support]

Hi,

Are you looking into running hardware-specific tests in a simulator (fully supporting the emulation of the STM32 hardware), or are trying to run high-level tests that do not have any hardware dependencies?

[support]

Hi,

Thanks for the suggestion. We will research this and try to support CTest in the next major VisualGDB release (after v5.4).

[support]

Hi,

Sorry about that and thanks for sharing the 100% repro steps. Looks like VisualGDB was not unescaping some arguments properly. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2583.msi

[support]

Hi,

Sorry about that, looks like our bug (we did not compensate for the fact that –login resets the working directory). We have updated the logic for wrapping the Cygwin commands in this build and tested it in several scenarios, so it should finally work: http://sysprogs.com/files/tmp/VisualGDB-5.4.10.2583.msi

Please open the toolchain editing window and manually set the command launch mode to “Interactive Bash Session”.

[support]

Hi,

Unfortunately it’s hard to suggest anything specific without knowing more details, so we would advise looking through the following pages:

• https://visualgdb.com/tutorials/tips/externc/ – tutorial explaining how to diagnose “Undefined symbol” errors
• http://visualgdb.com/support/linkerinputs/ – overview of various types of linker inputs

If this doesn’t help, please share more details about the exact errors you get and we will suggest further troubleshooting steps.

[support]

Hi,

This should be already done automatically when you start debugging. Also if you are using the Advanced CMake Project Subsystem, you can use the new “Install All Targets” command (see this tutorial). If it doesn’t help, please let us know more details about your scenario and we will try to suggest a better solution.

[support]

Hi,

Yes, you can upload the code using the COM-to-USB interface. Simply select the COM port on the first page of the VisualGDB Project Properties (for advanced ESP-IDF projects) and then right-click on the project in Solution Explorer and select “Program FLASH Memory”. This will automatically invoke the esptool.py script from the ESP-IDF that will program the memory via the COM port.

[support]

Hi,

This might happen due to a bug in VisualGDB 5.3. Please try updating to VisualGDB 5.4 Preview 9.

[support]

Hi,

You can find the retarget command by right-clicking on the mbed-os library in Solution Explorer.

The build error looks like some of the paths in your project settings might be incorrect. Please let us know the VisualGDB build number you are using (from the About window) that corresponds to the stack trace above and share the diagnostic output from View->Other Windows->VisualGDB Diagnostic Output that is generated when you try to open the project.

[support]

Hi,

Please try right-clicking on the project in Solution Explorer and select Add->Manage Mbed Platforms.

[support]

Hi,

Thanks for confirming this. It looks like an IntelliSense-related error, so please first check if the project builds successfully.

Then try creating a new project from scratch (ensure it uses the same make/cmake tool) and check if the problem persists.

If the problem does not affect build, please try clearing the VisualGDBCache and CodeDB folders when the project is closed and then reopening it. If the problem affects build, please try comparing your project settings with a newly created project that builds.

Finally, if you cannot create any project at all, please try reinstalling the ESP32 toolchain, as it might have gotten corrupt.

[support]

Hi,

Are you using the new advanced ESP-IDF project subsystem, or is it a regular VC++-based project?

[support]

Hi,

Yes, please try marking the sections for the external FLASH memory with the NOLOAD attribute in the linker script. This will prevent the objcopy tool from trying to place them in the same contiguous binary file as the regular FLASH sections.

[support]

Hi,

Thanks for reporting this. It looks like the advanced popup mode was inadvertently activated in some cases where VisualGDB could not fetch the regular QuickInfo text.

We have fixed it in this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2571.msi

No change of settings is necessary – the advanced popups will now only appear when activated explicitly.

[support]

Hi,

Sorry for the delay. We have pinpointed and fixed the issue in this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2571.msi

[Author]

Posts