SEGGER Embedded Studio Project Setup Errors

[Ryan Quinn]

Hi. This is my first experience using Nordic Products and I have run into some issues trying to "Open nRF Connect Studio Project" from SEGGER Embedded Studio. I want to run mesh sample projects to use my nRF52832 as a packet sniffer when paired with wireshark (I have seen other people post in this forum that this is possible). I believe (famous last words) I installed all the required software to start developing for my dev kit, but I am stuck with these errors when I try to bootup the example mesh projects. Any help would be appreciated. 

I am concerned from the portion I have highlighted that I my PC username ("Lab PC") my be messing something up due to the space in the name. hopefully this is not the case.

The final error I get is as follows.

Incase this helps with the debug, here are the various paths I was using to set up the project: 

One final question. Is there any benefit between using the sample projects form the "zephyr" folder or from the "nrf". I see both seem to have BLE Mesh sample projects?

[JONATHAN LL]

Hi Ryan,


Try removing any white spaces in the path, I see that you have /Lab PC/, this location includes a whitespace and that generally works poorly whit SEGGER.  Try to change this to  /Lab_PC/ if that is possible.
Also remember to sett your environment variables:
I usually sett mine to something like the following
ZEPHYR_BASE                                  = C:\nsc\v1.3.0\zephyr
ZEPHYR_TOOLCHAIN_VARIANT     =  gnuarmemb
GNUARMEMB_TOOLCHAIN_PATH  = C:\gnuarmemb

in your case I guess it would be:
C:/Users/Lab_PC/Documents/Projects/zephyr
and C:/(where ever you have your gnu arm embed toolchain)

And change the Directories option in SEGGER under Tools>Options>nRF Connect
Here is a image of how I have done it:

Is there any benefit between using the sample projects form the "zephyr" folder or from the "nrf"

 The examples provided in the nrf folder is recommended as these are maintained by Nordic and for Nordic products. In most cases the zephyr folder examples will work just fine also, but if you  work on the latest development branch (master), then the nrf folder has a extra layer of quality control supported by Nordic Semi. 

Regards,
Jonathan

[Ryan Quinn]

Hi Jonathan,

Unfortunate changing the user folder name (which took some searching to find out how to change as this is not normally allowed) seem to have messed up the paths for other required installs for SEGGER such as cmake. Unless you have a better idea I guess my options are to either resolve each path issue caused by the name change individually, start over as a new windows user, or try my luck setting things up on Linux. If you think you have an easy fix for  the path issue let me know. Otherwise I will see if I can get things running on Linux. Thanks for the help and feedback on nrf vs zephyr examples.

[JONATHAN LL]

Hi Ryan,

I would try to uninstall SEGGER and re-install it first. This is probably faster and easier then to change all paths individually.  
Are you able to install everything directly under the C drive? I have experienced less issues when setting up a widows development machine this way. 


I assume you all ready have seen/used some of this but here are some handy links:
The getting started guide for nRF Connected SDK, it goes in quite detailed for all platforms
Nordics SEGGER page linking to SEGGER, it will take you to the latest version of SEGGER for download.
nRF Connect for Desktop has a nice toolchain manger  as well as other apps that are quite useful for different Nordic products.
The Command line tools, really nice if you want to use the command line to build and flash and use VS Code, Atom or some other IDE or text editor to work on your projects.


The process is quite similar on Linux and if you are following the Getting started guide it takes the same amount of time. I have experienced that Linux does build projects a bitt faster so that is something to consider, although it is not by much but it does add up over time.


Regards,
Jonathan