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

Zephyr where can i download this ?

To build my own application or to programm the nRF9160 DK i have to work with SEGGER Embedded Studio, which i have already installed.

In the next step i have to do the following steps: 

To import a project into SES, you must specify the following information:

  • CMakeLists.txt - the location of the CMakeLists.txt project file of the sample that you want to work with
    i.e. C:\Users\ZIEGER\ncs\v1.3.1\zephyr\samples\basic\blinky\CMakeLists.txt
  • Board Directory - the location of the board description of the board for which to build the project
    i.e. C:\Users\ZIEGER\ncs\v1.3.1\zephyr\boards\arm\nrf9160_pca10090
  • Board Name - the board name (select from the list that is populated based on the board directory)
    i.e. nrf9160_pca10090
  • Build Directory - the directory in which to run the build (automatically filled based on the board name, but you can specify a different directory)
    i.e. C:\Users\ZIEGER\ncs\v1.3.1\zephyr\samples\basic\blinky\build_nrf9160_pca10090
  • Clean Build Directory - select this option to ensure that you are not building with an outdated build cache

I dont know where i can find CMakeList.txt, where can i find it ? 

What are those steps important for ? 

What do i have to download ? 

  • No, i does not work 

    C:\Users\ZIEGER\ncs\v1.3.1>west update
    FATAL ERROR: can't load west manifest
    no "manifest.path" config option is set

    what else can we do ? 

  • Hi, 

    Ok, what about "west init --local nrf"? And then "west update", does that work? 

    Edit: I have been told this is a unzipping-issue, rather than a downloading issue. You could try to unzip and install the SDK manually. To do this you need to find the folder named "downloads" inside the folder named "sdk", this folder should contain a zip-file named "ncs-toolchain-v1.3.1-..."  

    Here are the instructions for unzipping and installing the sdk manually: 
    Follow these instructions to install the nRF Connect SDK:
    
    1.  Create a folder in which you want to install the nRF Connect SDK.
        In the following instructions, we will refer to this folder as <NCS>.
    
    2.  Unzip the ncs-toolchain zip into the folder you created by right-clicking
        the .zip file and selecting 'Extract All'.
        This will create the following folder: <NCS>/<ncs-toolchain>
    
    3.  Navigate to the <NCS>/<ncs-toolchain> folder.
    
    4.  Double-click `git-bash.exe` to open a command line window from which you
        can install the nRF Connect SDK.
    
    5.  To clone and update the nRF Connect SDK GitHub repositories, type the following
        command and press enter:
    
        ncsmgr init-ncs
    
    6.  Double-click `SEGGER Embedded Studio.cmd` to open SEGGER Embedded Studio.
    
    7.  In SEGGER Embedded Studio, go to 'Tools' > 'Options' and select the 'nRF Connect' tab.
        Set the locations of the GNU ARM Embedded Toolchain and Zephyr.
        Use the 'Browse' button to select the following folders:
    
        GNU ARM Embedded Toolchain Directory: <NCS>/<ncs-toolchain>/opt
        Zephyr Base:                          <NCS>/zephyr
    
    8.  Click 'File' > 'Open nRF Connect SDK Project' to open a sample application.
        For example, to open the Asset Tracker application, select the following values:
    
        CMakeLists.txt:  <NCS>/nrf/applications/asset_tracker/CMakeLists.txt
        Board directory: <NCS>/zephyr/boards/arm/nrf9160_pca10090
        Board name:      nrf9160_pca10090ns
        Build directory: <NCS>/nrf/applications/asset_tracker/build_nrf9160_pca10090ns
    
    9.  Click 'Build' > 'Build' to build the application.
        If the application builds without errors, your installation was successful.
    
    
    You can now start developing your own application!
    /Edit
    Best regards 
    Robin 
  • Hi Robin, 

    thanks for your help so far.

    Some of your steps work very well. For example i could give the directory for: 

    GNU ARM Embedded Toolchain Directory:  <NCS>/<ncs-toolchain>/opt
    Zephyr Base:                                                 <NCS>/zephyr

    But there is still something missing by following your recent steps. 

    Some problems start at step 8 ...

    I finally got the CMakeLists.txt file which i could specify: 

    C:/Users/ZIEGER/nrf/applications/asset_tracker/CMakeLists.txt // Done ! 

    I was also able to get a zephyr folder by installing everything manually. 

    2. Unzip the ncs-toolchain zip into the folder ...

    3. Navigate to the ...

    4. ...

    5. ... // Done ! 

    etc...

    The problem is, that the zephyr folder only includes one single file. The file name is "module.yml" thats it. 

    So i cant give the correct directory for the board directory.  Board directory: <NCS>/zephyr/boards/arm/nrf9160_pca10090

    Also the file "build_nrf9160_pca10090nsdoes not exist!

    Build directory: <NCS>/nrf/applications/asset_tracker/build_nrf9160_pca10090ns //Thats what i was supposed to do. But there is no build_nrf9160_pca10090ns in the asset_tracker folder ... 

    What can i do now ? 

    Thank you Robin ! 

  • Hi 

    Looks like your missing a part of the file structure. The "zephyr" folder inside the nrf folder should only contain that one file.

    chris97 said:

    I finally got the CMakeLists.txt file which i could specify: 

    C:/Users/ZIEGER/nrf/applications/asset_tracker/CMakeLists.txt // Done ! 

    From this it looks like you've only installed the nrf folder within the ncs, is this the only files that was installed when using the manual process? 

    It's another Zephyr folder that's referred to in SEGGER embedded studio, this folder should be located at: 

    C:/Users/USERNAME/ncs/v1.3.1/zephyr

    that's the same folder as the nrf-folder should be in. So the zephyr folder you want is not the one inside the nrf folder but should be one step up in the directory. 

    You also have to edit the links so that <THESE> corresponds with your file structure, but I guess you got that already. 

    Best regards 

    Robin

Related