Forum Replies Created
-
Posts
-
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?
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.
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?
Hi,
To use VisualGDB with projucer you need to figure out 2 things:
- The exact command line to build your Projucer project
- 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.
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.
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.
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.
Hi,
The main difference is that the settings from the Embedded Project page are shared between all configurations (e.g. Debug/Release), while the settings on the Makefile Settings page are per-configuration.
For normal projects the common settings are automatically generated when you select an MCU from the list, however once you convert your project to a stand-alone one, VisualGDB replaces the MCU selection GUI with and editor the lets you modify the MCU flags directly.
