• State Not Answered
  • Replies 8 replies
  • Subscribers 67 subscribers
  • Views 4481 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 231654
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Clone the nRF Connect SDK

Sim1

Hi, I'm struggeling with this stage on the "getting started assistant"

"Clone the nRF Connect SDK"

Is there any step by step video to help me do this, I have probably not saved files in the correct places.
Can anyone push me in the right direction?

Wrong PATH? git is installed.

Thank you.

  • 0

    Hi,

    I recommend you use nRF Connect Getting started, which is an app for nRF Connect for desktop. That has detailed instructions for how to get started, including how to clone the nRF Connect SDK using west. I also help you install all the required tools.

    That said, you can continue as you have done, but you need to read the error messages and make the appropriate adjustments. Let's take them one by one.

    As the error text tells you, this fails because you are not in a west installation. You cannot use "west update" before successfully using "west init", as that is what creates the west installation.

    <sourcecode_root> is a placeholder that is supposed to be replaced by the path to your actual source code root.

    The error message states that git is not in your path. Therefore it cannot be used even if it is installed. You need to add it to your path.

    This is caused by the same problem as before: there is no west installation to update since you have never successfully called west init.

    By the way, why are you placing your ncs folder within C:\Windows\System32\? It should not be a problem, but it does not seem very clean to put your user data amongst the OS files.

    PS: Please copy-paste text from the terminal using Insert -> Code instead of using a screenshot next time, as that makes it easier to search and read.

  • 0 in reply to Einar Thorsrud

    Thank you!
    I'll try and fix it. And keep you posted.

    C:\Windows\System32\?:

    It was placed there by itself, i haven't placed it anywhere yet.



    Okey, i will remember that. Thank you.

  • 0 in reply to Einar Thorsrud

    now i've really messed up:

    C:\WINDOWS\system32>west init
    'west' is not recognized as an internal or external command,
    operable program or batch file.

    Now my cmd won't recognize the west file at all.
    What have i done wrong?

  • 0 in reply to Sim1 

    C:\WINDOWS\system32>west init
'west' is not recognized as an internal or external command,
operable program or batch file.

  • 0

    Hello, 

    I'll be taking over you support case as Einar is on vacation.

    My initial question is; how familiar are you with the embedded environment? Are you familiar with the Windows Command Line? I recommend that you start by getting an understanding of basic Windows functionality. Have a look at this tutorial. 

    Keep in mind that nRF9160 is an advanced product. I recommend reading thoroughly through the following tutorials: Getting Started with the nRF9160 DK and nRF Connect SDK tutorial. What usage are you planning with nRF9160?

    When you start the Windows Command Line, depending on your setup, it will default to:

    C:\WINDOWS\system32>

    You should not do anything in this folder and must move to C:\ before starting with anything in the Getting Started Assistant. This is done using the following command:

    cd C:\

    Standing in C:\ you can add the folder NCS and start with the Getting Started Assistant.

    mkdir NCS
cd NCS

    What steps have you done so far in the Getting Started Assistant? I recommend reading about the toolchain that you are installing, so you know what you are working with. There are plenty of holes to fall into if you do not know what you are doing. 

    Let me know what you have done so far, and what you plan to do, and we'll take it from there.

    Kind regards,
    Øyvind

Related