[support]

Hi,

Yes, please contact our sales with your license key information and we will issue you a trial extension voucher.

[support]

Hi,

This would be fairly tricky as VisualGDB expects the MSBuild projects to define a few VisualGDB-specific variables that would be missing in the project if it is controlled by an external MSBuild rules. The easiest way to get VisualGDB to debug it would be via the Embedded Quick Debug mechanism.

[support]

Hi,

This looks like a problem that was recently fixed in our development branch. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2081.msi

 

[support]

Hi,

Thanks for checking this. Looks like it could be some configuration issue rather than a race condition then. In order to pinpoint this, please follow the steps below:

1. Take a note of the module list block from the gdb log (e.g. x/16xb 0xbf1e8940)
2. Start OpenOCD manually using a command line from the OpenOCD window in VisualKernel (stop the VisualKernel session first).
3. Start gdb on the Linux machine manually and connect to gdb (target remote …)
4. Try reading the module list block by running the x/16xb <address> command manually. Does this result in non-zero values?

If the manual setup yields non-zero block contents, please try comparing the initialization commands between the manual mode and the VisualKernel GDB session log.

If the manual setup also reproduces the problem, please try checking if other commands (e.g. bt, disassembly) work and if reading memory using the OpenOCD commands (e.g. mon mdw <address>) works. This should help us understand which part of the debugging pipeline is affected by the bug and devise a workaround.

[support]

Hi,

Thanks, this is already fixed in our development branch and will be included in the upcoming v5.4 Preview 1. Until then, editing the XML file manually is the recommended workaround.

[support]

Hi,

This would happen for environment variables that are only set for interactive shells. We actually have a detailed page describing this (and known workarounds) here: http://visualgdb.com/support/fixenv/

If it doesn’t help, please let us know and we will investigate this further.

[support]

Hi,

Yes, we removed the compactcpp library from the latest toolchain as it is no longer needed with the latest libc++ optimizations. VisualGDB would normally update your project automatically if you change any settings on the first page of VisualGDB Project Properties, but removing it manually should produce exactly the same result and is totally OK.

[support]

Hi,

Please try selecting “Show STM32CubeMX samples” on the sample selection page in the VisualGDB wizard. It will show the sample projects that came with the STM32CubeMX software libraries and might include an out-of-the-box UART example for your board.

[support]

Hi,

Sorry, we don’t have any tutorial for the STM32Cube programming tool. However you can easily program your firmware without starting a debug session by selecting Debug->Program Embedded Firmware.

[support]

H,

Thanks for the repro. It looks like your toolchain fine sets the CXX executable in a way that confuses CMake. Please try moving the compiler arguments into a separate CMAKE_CXX_FLAGS statement:

set(ENV{CXX} "arm-vgdbtest-linux-gnueabi-g++" CACHE STRING "" FORCE)
set(CMAKE_CXX_FLAGS "-march=armv7ve -marm -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=$ENV{SDKTARGETSYSROOT}" CACHE STRING "" FORCE)

[support]

Hi,

Thanks for reporting this, looks like a side effect of the recent WPF redesign of the authentication GUI. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2081.msi

[support]

Hi,

No problem, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2081.msi

 

[support]

Hi,

OK, we have released v5.4 Preview 1 that supports the new advanced ESP-IDF project subsystem. You can download the build here. You can read the announcement with the main highlights of the new subsystem here: https://sysprogs.com/w/announcing-visualgdb-5-4-preview-1/.

• This reply was modified 7 years, 6 months ago by support.

[support]

Hi,

The build number (2077) looks correct, so looks like it got installed properly this time.

[support]

Hi,

Perhaps you have configured the VisualGDB’s raw terminal to open COM2? Either way, please try searching the .vgdbsettings file for any mentions of COM2. If none are found, please attach a screenshot of the error message you get and we will try to suggest you which setting could be affecting it.

 

[Author]

Posts