[support]

Hi,

You can check out this tutorial for step-by-step instructions on using lwIP with STM32: http://visualgdb.com/tutorials/arm/stm32/lwip/

[support]

Hi,

Yes, the beta has a few minor issues, but is generally stable. We have updated the BSP definition so that it will only show up as an update for the latest VisualGDB 5.1.

[support]

Hi,

The “AlternativeType” system is not recursive, so the definition in your case should look like this:

  <Type Name="std::map&lt;int32_t, std::string&gt;">
    <AlternativeType Name="HandleValueT"/>
  </Type>

We have just retested it on a simple MinGW project. What does the GDB session window show when you try evaluating your variable? Does it show any errors (you need to switch it to the “All GDB interaction” mode)?

[support]

Hi,

Does Visual Studio eventually unfreeze? Can you enable creation of GDB logs (via VisualGDB Project Properties -> Advanced GDB Settings) and see if the log keeps on growing when VS is frozen? If this does not immediately clarify the problem, please attach the log here or submit it to our support email.

[support]

Hi,

Thanks for pointing that out, we will improve the SmarTTY logic for handling upload errors in the next release.

Regarding the debugging error, do you mean the “Invalid deployment path” one? If yes, what exactly are the deployment paths you set for both projects?

[support]

Hi,

If you are doing heavy multi-threaded debugging, you may find the Parallel Stacks window usable. You may also find it usable to sketch relations between multiple functions and data objects (e.g. mutexes) via Code Map. VisualGDB actually supports it very well for C++ projects.

[support]

Hi,

Have you managed to upload the built OpenCV to your Raspberry Pi (step 11 of the tutorial)? Was libopencv_videostab.so.3.1 among the built files? Is the directory where it was copied among the ones in LD_LIBRARY_PATH?

[support]

No problem. If you encounter further problems, feel free to create a new thread.

[support]

No problem. Let us know if you run into any problems.

[support]

Hi,

To use VisualGDB with projucer you need to figure out 2 things:

1. The exact command line to build your Projucer project
2. The location of the executable it builds

Once you know both of those, simply select “Import a project built with command-line tools” in VisualGDB Project Wizard and specify the command line and the executable. VisualGDB will automatically create a project that will wrap your projucer setup.

[support]

Good to know it worked. Let us know if you encounter further problems.

[support]

Hi,

The `clock_gettime@GLIBC_2.17′ error occurs when your headers and libraries end up being mismatched after a partial sysroot sync. Please resynchronize your sysroot again. If this does not help, simply reinstall the toolchain from scratch and synchronize it then.

[support]

Good to know it works. Let us know if you encounter further problems.

[support]

Hi,

Most likely either your user account does not have access to the directory where you are trying to create the file, or you are running it on a wrong machine. Please try to change the directory of the file to /tmp and if it does not help, try running the executable directly over SSH.

[support]

Hi,

This is by design. The preview version of the nRF52 chip has a bug the includes in wrong memory placement, so only the first 32KB are accessible (unless you create a separate memory region and place some data there). Hence VisualGDB treats it as a 32KB device.

[Author]

Posts