Forum Replies Created
-
AuthorPosts
-
support
KeymasterNo problem. Let us know if you run into any problems.
support
KeymasterHi,
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.
support
KeymasterGood to know it worked. Let us know if you encounter further problems.
support
KeymasterHi,
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.
February 8, 2016 at 06:42 in reply to: Unable to debug std::map when cmake is configured with flag -std=c++11 #7613support
KeymasterGood to know it works. Let us know if you encounter further problems.
support
KeymasterHi,
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
KeymasterHi,
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.
February 5, 2016 at 02:42 in reply to: Unable to debug std::map when cmake is configured with flag -std=c++11 #7605support
KeymasterHi,
OK, we have fixed the map problem in the upcoming Beta 1.
support
KeymasterThanks for reporting this, we have fixed it in the upcoming Beta 1.
February 4, 2016 at 06:18 in reply to: Difference between Embedded Project and Makefile settings in project properties #7602support
KeymasterHi,
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.
support
KeymasterHi,
The IntelliSense errors do not actually stop the build. Can you double-check whether the build succeeds? You can use the Output window to see what exactly happens there.
support
KeymasterHi,
Please try using the Clang-based IntelliSense.
support
KeymasterHi,
Not yet. We have actually managed to get TCP/IP to work with the STM32 devices using their lwIP port, but if anyone wants to share instructions on the W500P chip, we will happily repost them.
support
KeymasterGood to know. Let me know if you need any further help.
support
KeymasterHi,
You can try downloading our BSP generator (https://github.com/sysprogs/BSPTools/tree/master/generators/nrf5x) and running it on the latest SDK. For nRF52 we used the nrf5x_v10_v092 SDK.
-
AuthorPosts