I am using the nRF52832 in several projects for several different clients. I have created a "project" under Visual Studio using VisualGDB for each one, using the automated build process. Every time I switch from one project to another, I get a VisualGDB warning "Could not locate BSP with ID.....". Choices presented are "Download BSP", "Use version x.xx", or "Locate BSP". I have tried all three at various times; I inevitably end up in another nightmare, killing a couple hours, trying to get the project back together and all the mysterious include files pulled from the right places. Surely the tools can't be THAT amateurish as to preclude multiple parallel projects, so I must be missing something.
1) Why does the message pop up, and why is it not resolved when I load the latest version to all projects?
2) Where do I set the various include paths (which in true Microsoft style, is at least a dozen directories deep)?
3) Is there a better way to do real world development?
SteveHx said:Is there a better way to do real world development
Use one of the supported IDE/Toolchains?
Segger, Keil, ...
At least then you have a larger pool of support
I am using Visual Studio 2019 and a self-created BSP for 15.3 and besides the learning curve of using VisualGDB instead of the supported IDEs, have had no issues.
As annoying as VisualGDB can be, I have stuck with it and cannot imagine switching to Segger (Or Keil or whatever). Also, this question will probably be better answered on the VisualGDB forum. From what I can tell there are only a handful of us using VisualGDB for development here.
Patrick said: I have not used SES much but from what little I have used it, I believe you also have to add each source file to the project manually
Because Nordic provide base projects, that saves you a lot of grunt work with the "standard" stuff.
Of course, anything you want to add to that, you have to do yourself.
You only have to add .c files - not the headers - although you do have to manually add include paths as necessary.
Patrick said:this question will probably be better answered on the VisualGDB forum
Patrick said:From what I can tell there are only a handful of us using VisualGDB for development here
As Andrew and Patrick is saying, I think that the first two questions are better to ask on the VisualGDB support page, as we don't have much experience with it here at Nordic.
As for question three, Andrew is right. Using SES or keil uvision are the two IDEs that are best supported by Nordic, and easiest to use with Nordic products.
After beating on this for a couple days over at VisualGDB support, I have reinstalled VisualGDB and the Nordic BSP, with some tweaks to the directories, and now I can compile a new project and can switch between projects smoothly. However, with v15.3 of the Nordic support, new projects don't get NRF_LOG_INFO etc. displaying to the serial port. The project that I was previously using works fine in that regard, so I know the hardware is okay. Is there something special needed in the switches when creating a new project?