entering command-line environment

RE: entering command-line environment

Marte Myrvold — Fri, 17 Jun 2022 09:02:35 GMT

Hi,

The toolchain was changed in nRF Connect SDK v2.0.0 to be the Zephyr SDK. and not GNU Arm Embedded Toolchain as in previous versions, so running git-bash.exe will not set up gnuarmemb. It should still set up the environment variables for the new toolchain. If this is not the case, please open a new ticket, as the original issue in this ticket has been solved. Thank you!

Best regards,

Marte

RE: entering command-line environment

abkirchhoff — Thu, 16 Jun 2022 20:01:22 GMT

The solution in the suggested answer to simply run "git-bash.exe" in the toolchain folder works great for SDK v1.9.1. However, for SDK v2.0.0, the git-bash.exe file was moved to a separate "toolchains/v2.0.0" folder and running "git-bash.exe" in this folder does not load the correct environment. Any suggestions?

I would like to be able to directly launch a Git Bash with the SDK v2.0.0 environment without using the option in Toolchain Manager. Using Toolchain Manager, the "Open bash" option works just fine.

Thanks!

RE: entering command-line environment

Yaron Shragai — Wed, 16 Mar 2022 15:48:18 GMT

Hi,

Thanks - your reply helped me to find the solution.
tl;dr: I should launch Git bash by running the git-bash.exe executable in the SDK's toolchain dir, not my "regular" Git bash, and everything will be set up automagically.

Git Bash:

The root dir (the "/" dir) in Git Bash is: The directory of the git-bash.exe executable that was launched.

When I launch Git bash on my system the "normal" way, it launches my regular git-bash.exe executable from C:\Program Files\Git - and so that is root.

The Toolchain Manager, otoh, uses the git-bash.exe executable in the SDK's toolchain dir - and so that is root.

Next, Git bash executes /etc/profile (off of whatever root is). The SDK's /etc/profile executes everything in the profile.d subdir. In particular, profile.d/ncs-env.sh sets up the proper SDK environment.

So, if I execute the git-bash.exe executable in the SDK's toolchain dir, I don't need to do anything else.

Windows Command Shell:

To launch the Windows Command Shell, the Toolchain Manager executes the git-cmd.cmd script in the SDK's toolchain dir. All this script does, really, is execute cmd\env.cmd. Simply bringing up the "regular" Windows command shell and running either git-cmd.cmd or cmd\env.cmd accomplishes the same thing - which is why what I did previously with the Windows command shell worked.

Windows Power Shell:

The SDK does not have a pre-packaged way to bring up a Windows Power Shell environment, so, I will not use it.

Hope this helps 😉

Thanks!

RE: entering command-line environment

Marte Myrvold — Wed, 16 Mar 2022 14:15:06 GMT

Hi,

When you open bash or command prompt using the buttons in the Toolchain Manager you are actually just running the files git-bash.exe or git-cmd.cmd located in the toolchain folder. What these do is to set up the environment correctly before running bash and command prompt. You can see that by opening git-cmd.cmd and cmd/env.cmd in a text editor. So the issue is not the root dir, but that the environment variables are not correctly set. If you do not run env.cmd you need to make sure that all environment variables set by that file is set in your path instead.

As for Windows Power Shell it seems like it is using the incorrect Python path. I should have mentioned in my last reply that you will also need to add the correct Python path to your environment variables. You can also find this in env.cmd.

Best regards,

Marte

RE: entering command-line environment

Yaron Shragai — Tue, 15 Mar 2022 17:25:02 GMT

Hi,

I think we're getting closer.

Some good news: I tried it out on Windows command prompt (not Power Shell), and found that after just running env.cmd, I could run west and build an example with it!

As for Git Bash:

To the steps I described before, I added:

export PATH=$PATH:`pwd`/toolchain/opt/bin:`pwd`/toolchain/opt/bin/Scripts

Now if I execute "which west", I get (correctly):

/c/Users/yaron.shragai/ncs/v1.9.1/toolchain/opt/bin/Scripts/west

But if I try to run west, regardless of options, it just returns without doing anything and with no screen output.

By the way: It looks like the Git Bash environment spawned by the Toolchain Manager sets the root dir (the "/" dir) to the SDK's directory. In my setup, the root dir is still Git Bash's default root dir (which is C:\Program Files\Git). I tried to search the web for how to change Git Bash's root dir, but came up empty; but that is clearly something that the Toolchain Manager does when it spawns a Bash shell - so if you can tell me how to do that, it just might resolve this.

And as for Windows Power Shell:

After executing env.cmd, I navigated to the toolchain\opt\bin dir and executed:

$env:path += ";" + $pwd

Then I navigated down to Scripts and did the same.

I verified that $env:path now includes those dirs.

When I executed west, I got:

Traceback (most recent call last):
File "C:\Users\yaron.shragai\AppData\Local\Programs\Python\Python37\lib\runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "C:\Users\yaron.shragai\AppData\Local\Programs\Python\Python37\lib\runpy.py", line 85, in _run_code
exec(code, run_globals)
File "C:\Users\yaron.shragai\ncs\v1.9.1\toolchain\opt\bin\Scripts\west.exe\__main__.py", line 4, in <module>
ModuleNotFoundError: No module named 'west'

So, it seems like west.exe is trying to set off some Python code which is not working.

RE: entering command-line environment

Marte Myrvold — Tue, 15 Mar 2022 14:57:00 GMT

Hi,

Try to adding the path to toolchain/opt/bin and toolchain/opt/bin/Scripts to your system path.

Best regards,

Marte

RE: entering command-line environment

Yaron Shragai — Tue, 15 Mar 2022 14:45:32 GMT

Hi,

Thanks for the response.

I brought up Windows PowerShell, navigated to my SDK dir (ncs\v1.9.1), then down to toolchain\cmd, and executed env.cmd.
Then I tried running west, and it wasn't a recognized command.

Similarly, I brought up Git Bash, navigated to my SDK dir (ncs\v1.9.1), and did the following:

source zephyr/zephyr-env.sh
export ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb
export GNUARMEMB_TOOLCHAIN_PATH=`pwd`/toolchain/opt

Then I tried running west, and it wasn't a recognized command.

What am I missing?

Thanks!

RE: entering command-line environment

Marte Myrvold — Tue, 15 Mar 2022 13:23:54 GMT

Hi,

Running zephyr-env.sh does not set ZEPHYR_TOOLCHAIN_VARIANT and GNUARMEMB_TOOLCHAIN_PATH. You need to run env.cmd located in toolchain/cmd from the command line you are going to use.

Alternatively, you can set ZEPHYR_TOOLCHAIN_VARIANT and GNUARMEMB_TOOLCHAIN_PATH in your system environment variables as you would do if you installed nRF Connect SDK manually instead of with the Toolchain Manager. In that case you need to set the following:

ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb
GNUARMEMB_TOOLCHAIN_PATH=c:\ncs\v1.9.1\toolchain\opt

Make sure that the path you set GNUARMEMB_TOOLCHAIN_PATH to is the path to your nRF Connect SDK installation and where your toolchain folder is.

Best regards,

Marte