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

[support]

Hi,

Please try downloading the newest Nordic SDK and replacing the contents of the C:\Users\LabUser\AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.nordic.nrf5x\nRF52 folder with it.

[support]

Hi,

Normally this should not happen. Can you close the .cpp file, open the View->Clang IntelliSense Diagnostics console, clear it and open the .cpp file again?

The console should show some diagnostic messages explaining why VisualGDB decides to use Clang IntelliSense for this file. If they do not clarify the situation, please post them here so that we could suggest further steps.

[support]

Hi,

Does it work when you run your program manually via SSH? If not, the only advice we could give is to try stepping into the library code and figuring out why it cannot open the device. Perhaps the device is already open by some other app?

• This reply was modified 9 years, 5 months ago by support.

[support]

Hi,

Good to hear you got it to work. Regarding the size, please try switching to newlib-nano. It significantly reduces the size of your binary.

[support]

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

[Author]

Posts