This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SEGGER Embedded Studio Project Setup Errors

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?

Parents
  • 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

Reply
  • 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

Children
No Data
Related