Clone the nRF Connect SDK

RE: Clone the nRF Connect SDK

Øyvind — Tue, 10 Sep 2019 07:34:44 GMT

Hello Matt,

Could you please register a new support case here? Please include information on what version of Getting Started Assistant you are using.

Kind regards,
Øyvind

RE: Clone the nRF Connect SDK

Mattchew — Mon, 09 Sep 2019 16:31:47 GMT

Hello,

I am stuck on the "Getting Started Assistant" at "pip3 install west"

"west" installed correctly but will not verify. Also, the document never says to cd c:\.

11:25:06.011

'west' is not recognized as an internal or external command, operable program or batch file.

11:25:06.025

nrf_connect_sdk-0.1.4-0 verification failed

Thanks,

Matt

RE: Clone the nRF Connect SDK

Øyvind — Tue, 02 Jul 2019 12:46:50 GMT

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

RE: Clone the nRF Connect SDK

Øyvind — Tue, 02 Jul 2019 12:46:01 GMT

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

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

RE: Clone the nRF Connect SDK

Sim1 — Sat, 29 Jun 2019 08:17:59 GMT

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

RE: Clone the nRF Connect SDK

Sim1 — Sat, 29 Jun 2019 08:15:44 GMT

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?

RE: Clone the nRF Connect SDK

Sim1 — Fri, 28 Jun 2019 19:57:17 GMT

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.

RE: Clone the nRF Connect SDK

Einar Thorsrud — Fri, 28 Jun 2019 11:00:48 GMT

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.