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

Problem with 'Clone the nRF Connect SDK' Step in the 'Getting Started Assistant' Phase

I'm currently working with the nRF9160 DK and received it fresh from the box probably around 2 weeks and I successfully activated the SIM card from the Nordic Cloud and eager to start programming onto it.

I'm currently based out of New Jersey, USA

I downloaded the nRF Connect Application for Mac (Currently working from a 2015 Macbook Pro) and began with the 'Getting Started Assistant'

Step 1: Install the Toolchain (Success)
- Successfully managed to install 'Homebrew' and "Download and install version 8-2019-q3-update of the GNU ARM Embedded toolchain to be able to cross-compile for ARM targets"

Step 2: Clone the nRF Connect (Having difficulty)
- I successfully performed, 'pip3 install west'
- I'm having difficulty with the second part which says, "Initialize west and clone the nRF Connect SDK manifest repository nrf:"
- I created a folder in /Users/'myname'/ncs
- cd /Users/'myname'/ncs
- west init -m github.com/.../fw-nrfconnect-nrf
- However, after I run that command I receive, "FATAL ERROR: already initialized in /Users/'myname', aborting."
- Unfortunately, I cannot locate where this is currently initialized
- This is where I need the most help at this current stage of the setup.

Step 3: Download Segger Embedded Studio (Success)
- Successfully downloaded this application for coding

Any help would be greatly appreciated as I'm very eager to get this up and working. Thank you for your time in this.

Parents
  • Hello,

    I'm glad step 1 and step 3 was successful! 

    Step 2: Clone the nRF Connect (Having difficulty)
    - I successfully performed, 'pip3 install west'
    - I'm having difficulty with the second part which says, "Initialize west and clone the nRF Connect SDK manifest repository nrf:"
    - I created a folder in /Users/'myname'/ncs
    - cd /Users/'myname'/ncs
    - west init -m github.com/.../fw-nrfconnect-nrf
    - However, after I run that command I receive, "FATAL ERROR: already initialized in /Users/'myname', aborting."
    - Unfortunately, I cannot locate where this is currently initialized
    - This is where I need the most help at this current stage of the setup.

    In your folder "/Users/'myname' " can you please show what is in this folder? A screenshot from terminal or similar.

    Kind regards,
    Øyvind

  • You can see that the 'ncs' folder that I created is empty where I want to place the github manifest. 

  • OK, so what happens if you delete that folder and try one more time? 

    Can you make a folder with another name i.e. NCS12, and then try one more time inside of this folder? Can you take a screenshot of the result in the terminal?

    Kind regards,
    Øyvind


  • Last login: Thu Mar 26 10:23:10 on ttys000
    Joels-MBP:~ Joel$ cd /Users/'myname'
    Joels-MBP:~ Joel$ mkdir NCS12
    Joels-MBP:~ Joel$ cd NCS12
    Joels-MBP:NCS12 Joel$ west init -m https://github.com/NordicPlayground/fw-nrfconnect-nrf
    FATAL ERROR: already initialized in /Users/'myname', aborting.
     
    
    

    Unfortunately I get the same error. I even deleted the older folder 'ncs' from /Users/Joel 

  • On a Linux computer, you would get something like: 

    $ west init -m https://github.com/NordicPlayground/fw-nrfconnect-nrf
    FATAL ERROR: already initialized in /opt/ncs, aborting.
    Note:
        In your environment, ZEPHYR_BASE is set to:
        /opt/ncs/zephyr
    
     
    
        This forces west to search for an installation there.
        Try unsetting ZEPHYR_BASE and re-running this command.
     


    Are you getting the same? Have you edited the variables in Getting Started Assistant?


  • As of now my variables are:

    GnuArmEmb_path: /Users/'myname'/Documents/gcc-arm-none-eabi-8-2019-q3-update

    sourcecode_root: /Users/'myname'

    ncs_tag: v1.2.0

    Could it be something with the way I set my variables in 'Getting Started Assistant'? I wasn't sure what the sourcecode_root variable was suppose to be set to when I first began this process. Hopefully the location of these variables can shed more light. 

Reply
  • As of now my variables are:

    GnuArmEmb_path: /Users/'myname'/Documents/gcc-arm-none-eabi-8-2019-q3-update

    sourcecode_root: /Users/'myname'

    ncs_tag: v1.2.0

    Could it be something with the way I set my variables in 'Getting Started Assistant'? I wasn't sure what the sourcecode_root variable was suppose to be set to when I first began this process. Hopefully the location of these variables can shed more light. 

Children
Related