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

issue with nRF connect getting started and Embedded Studio

Hello,

I have installed Embedded Studio and acquired a Nordic license. However the Tools/Options... nRF Connect menu option does not appear. I tried creating a dummy Nordic project but that didn't fix the problem. Here are the instructions from the Getting Started guide. What did I miss?  

BTW, I submitted this as a Segger support issue and they sent me back here.

Navigate to the folder where you extracted SEGGER Embedded Studio. Double-click SEGGER Embedded Studio for ARM.app.

Click Tools > Options and select the nRF Connect tab.

To load and build a project in SES, you must specify the following information:

  • Additional CMake Options - -D WEST=<path to west executable>, for example -D WEST=~/Library/Python/3.7/bin/west

  • Zephyr Base - the location of your cloned Zephyr repository (the full path to ncs/zephyr)

  • GNU ARM Embedded Toolchain Directory - the location of your GNU ARM Embedded Toolchain installation (for example, /opt/gnuarmemb)

  • CMake - the path is /usr/local/bin/cmake by default

  • DTC - the path is /usr/local/bin/dtc by default

  • Ninja - the path is /usr/local/bin/ninja by default

  • Python - the path is /usr/local/bin/python3 by default
Mark done
  • Well, this is interesting.

    The link you provided definitely specified "nordic" in the URL. If you go to the Embedded Studio Downloads page on Segger.com, these links are not available. You must follow the tutorial or getting started guides to download the right version. Since that is the case and the Mac OS download link was not provided in the Getting Started guide, I was a clever developer and went to Segger and downloaded SES for Mac. (Please remember to add the link to the Linux version too. Most of my development is done in Linux. I work natively in MacOS when possible.)

    I am sorry but it was not obvious to me that this was a special SES version for Nordic. Running the non-Nordic specialized version still gives you the option to download an activation key from Nordic. Having the wrong version installed was not apparent until the options were missing in the GUI.

    Thanks

  • It appears that this version is only required for the new "nRF Connect SDK"? 

    I have used the non-Nordic specific version of SES to work with SDK 15.x examples. 

  • Allen said:
    It appears that this version is only required for the new "nRF Connect SDK"? 

     Yes, this is correct. The Nordic Edition of SES is intended to be used with the nRF Connect SDK. If you are working with the SDK 15.x examples, you should use the version of SES that is available for download on https://www.segger.com/downloads/embedded-studio.

    However, I talked to another colleague, and he said that the Getting Started Assistant App should automatically detect the operating system and provide the appropriate download links. Could you double check this once more? Try opening the newest version of nRF Connect and the Getting Started Assistant on your Mac and check what download links shows up. If it's only the windows versions, there is a bug with the app and I will report it.

    Best regards,

    Simon

  • Verified that the Mac version is downloaded when installing from the Getting Started application.

    Thanks

  • I have the same problem - on Linux

    I don't see easy way to associate .emProject with SES.

    I can't make SES to be part of "installed apps".

    Every time I start SES - it asks for "request free licenses", it overwrites some ~/Nordic directory files.

    It exits if I do not request a license so I have to do it over and over.

    If I go to "Manage licenses" I see the old license and I have to enter duplicate.

    Please provide some instructions/ways to avoid this hassle.

    File, env.var, whatever...to store the license and activate it properly.

    I am grateful to Nordic that it invested in SES licensing - it is great benefit, I truly appreciate it.

    I had to switch from Windows to Mac to VM to Ubuntu - a lot of time spent with the license.

    Thank you

Related