[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.

[support]

Hi,

OK, we have fixed the map problem in the upcoming Beta 1.

[support]

Thanks for reporting this, we have fixed it in the upcoming Beta 1.

[support]

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.

[support]

Hi,

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]

Hi,

Please try using the Clang-based IntelliSense.

[support]

Hi,

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]

Good to know. Let me know if you need any further help.

[support]

Hi,

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.

[support]

Hi,

Looks like you have somehow changed the build command in VisualGDB Project Properties. If it’s just a simple test project, the easiest way to fix this would be to re-create it.

[support]

Hi,

That makes sense. VisualGDB keeps a log of all GDB commands to display them in the GDB Session window, so a log over 700 MB + formatting and timestamps could easily exceed the maximum 2GB allowed per user-mode process.

What happens if you clear the gdb session log from time to time? Does it reduce the memory usage of devenv.exe in Task Manager?

[support]

Hi,

You can then use a combination of an additional startup command in VisualGDB Project Properties and the Raw Terminal (Custom and Ultimate editions only). Simply configure the terminal to connect to the port where Segger forwards the tracing output.

[Author]

Posts