[support]

No problem, we ran a quick test with OpenOCD. It turns out that when OpenOCD accepts an incoming connection from gdb, it tries to detect the FLASH ID of the on-board FLASH memory and the code used to do that hangs, so on OpenOCD side it looks like a gdb timeout and on gdb side it looks like an OpenOCD timeout.

Looks like there were attempts to add support for LPC1549 into OpenOCD (e.g. see this patch), but they seem to be abandoned, most likely due to low interest. As the J-Link solution works out-of-the-box and does not require any extra hardware (the on-board LPC-Link can is turned into a J-Link), we would recommend using it instead and will not do any more investigation into the OpenOCD bug. Let us know if you would like us the send you the board back.

[support]

Hi,

Thanks, that’s a good point. We will consider adding some sort of an “under investigation” flag to the forum posts so that we can share the investigation progress without closing the topics.

[support]

Hi,

Please try running devenv.exe /ResetSkipPkgs. If this does not help, please double-check that the “C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Sysprogs\VisualKernel\extension.vsixmanifest” file exists and is not corrupt. If this does not help either, please try running devenv.exe /log and check the ActivityLog.xml file for messages related to VisualKernel.

[support]

Hi,

VisualGDB supports the .natvis files on all supported VS versions as long as the files are explicitly added to the project in Solution Explorer.

You can check the View->Other Windows->VisualGDB Diagnostics Console for messages explaining the .natvis file search.

[support]

Hi,

Our latest STM32 BSP includes many of the ST examples, so you can simply select “STM32Cube examples” on the sample selection page of the VisualGDB project wizard and pick a sample project to import.

If you want to import a different project, you can use the “Import existing project” option in the wizard, but you would need to manually locate and specify various build settings (e.g. include directories and preprocessor macros).

[support]

Yes, we have just released the new toolchain.

Note that it requires a few extra configuration steps, so please follow the updated ESP32 tutorial to get started with it.

[support]

Hi,

You can try installing the WinUSB driver for the virtual J-Link device and using OpenOCD to debug it (FLASH programming may be less reliable and may require selecting a script manually), although the debugging experience will be less convenient than with the Segger software.

 

[support]

Hi,

Sorry, an overnight fix on Sunday night is a bit beyond our capabilities.

We have investigated this and confirmed a bug in our register definitions for Tiva devices. We have updated our BSP with the correct definitions.

You can install the latest BSP via Tools->Manage VisualGDB Packages.

[support]

Hi,

Yes, sorry about that. The STM32 BSP comes with different versions of the cmsis_os.h and the VisualGDB header discovery does not go deep enough to validate them.

Normally if you add references to FreeRTOS via the Embedded Frameworks page, VisualGDB should set the correct include directories automatically and you won’t need to fix anything manually.

[support]

Hi,

No problem. The shared library should do as well, as long as it is always present on your target system.

[support]

Hi,

This could happen if your toolchain is not compatible with the deployment computer. Please examine the error log shown by VisualGDB for further clues (e.g. an “invalid file format” or “invalid ELF target” message would definitely suggest a wrong toolchain being used).

[support]

Hi,

Yes, we have published a detailed tutorial last week: https://visualgdb.com/tutorials/arm/mbed/lpc1549/

[support]

Hi,

Sorry, if you want to import complex 3rd-party projects into VisualGDB, you do need to understand how to build them manually and locate/install the necessary build tools. VisualGDB can simplify a lot of the common tasks through features like automatic header discovery, but it requires understanding of the underlying build process if you want to go beyond creating & modifying basic samples that work out-of-the-box.

Our best advice would be to check with the project vendor for specific steps required to build the project under Windows.

[support]

Hi,

This would normally indicate a problem with the project’s Makefile and selecting a different VisualGDB configuration won’t affect this.

Please try checking if you can build the project on Windows via command line (by running make.exe manually). If not, the project’s build scripts may not be compatible with Windows and would need to be fixed before you can import the project into VisualGDB.

[support]

Hi,

This is actually by design and replicates the regular VS debugging experience. The watch window and hardware registers are only active when the target is stopped (e.g. at a breakpoint). To view the variables while the target is running, please use the Live Variables window.

[Author]

Posts