New nRF9160 DK, and I'm unable to create the build environment and open the application sample in Segger.

RE: New nRF9160 DK, and I'm unable to create the build environment and open the application sample in Segger.

Simon — Wed, 27 Nov 2019 22:53:39 GMT

[quote user="jkase"]I copied the six.py and the dist directory over to the ~/Library/Python/3.7/lib/python/site-package directory, and SES can now open the project![/quote]

I would recommend you to only have one Python/3.7 folder or only include the path to /Library/Python/3.7 into your system variables, such that when you use the commands pip3 and west it will run from /Library/Python/3.7. Then when you use SES, it will find the packages.

[quote user="jkase"]The resulting presentation of code is very different from what I'm used to with SES 4.18. Also, the opening screen indicates that there's a newer version of SES available (4.30b). When I download that version, it finds the License key from the 4.18 version and seems "normal" -- however, it does NOT have the Open nRF Connect SDK Project menu item.[/quote]

I suspect that you are using the original version of SES. Not the Nordic Edition. Take a look at the cases below for clarity:

Best regards,

Simon

RE: New nRF9160 DK, and I'm unable to create the build environment and open the application sample in Segger.

jkase — Wed, 27 Nov 2019 18:37:51 GMT

I copied the six.py and the dist directory over to the ~/Library/Python/3.7/lib/python/site-package directory, and SES can now open the project!

The resulting presentation of code is very different from what I'm used to with SES 4.18. Also, the opening screen indicates that there's a newer version of SES available (4.30b). When I download that version, it finds the License key from the 4.18 version and seems "normal" -- however, it does NOT have the Open nRF Connect SDK Project menu item.

So, is this menu option available in the SES 4.18 or 4.30b versions? Does development of this product require a non-standard version of SES?

Thanks,

--jeff

RE: New nRF9160 DK, and I'm unable to create the build environment and open the application sample in Segger.

jkase — Wed, 27 Nov 2019 15:14:08 GMT

Yes, I'm using the latest version.

when I re-run pip3 install west, the output says:

Requirement already satisfied: six in /Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/site-packages (from configobj->west) (1.12.0)

I'm a long time Xcode developer, so it makes sense that there's python in the Xcode toolchain.

As part of this installation, there is also a python 3.7 installation in

/Users/jeffkase/Library/Python/3.7/lib/python/site-package

And, that may be where SES is looking for six (it doesn't exist in that location).

What path does python use for finding scripts/tools?

--jeff

RE: New nRF9160 DK, and I'm unable to create the build environment and open the application sample in Segger.

Simon — Wed, 27 Nov 2019 14:53:53 GMT

I did not see your first comment on this post, my apologies for that. But I'll try to address your inquiries.

[quote user="jkase"]I get that this is a very new product, and that we're on the bleeding edge, here. But, this is one of the worst out of the box experiences I've had in 35 years of programming.[/quote]

I am really sorry you feel this way, but I will make sure, step by step, that you get NCS up and running. Then we can look at the problems you've met along the way, and see if there is any way the Getting Started guide can be improved to avoid this in the future.

[quote user="jkase"]Also, let's not lose track of the license key that has to be re-installed every time I open the newer version of SES.[/quote]

Could you create a new case where you address this? Then we can keep it more organized and focus on getting NCS up and running in this thread.

[quote user="jkase"]If you have a macOS system, I'd be happy starting over with the installation process if there was an accurate set of steps that would solve these issues.[/quote]

I don't have a mac at hand at the moment, but I don't think I necessarily need it for your specific issues. If we meet a wall, I'll get hold of one.

[quote user="jkase"]Still no luck. Same error modal, with the same error log, re. "import six".[/quote]

This module should be installed when calling pip3 install west. Try running it again and see if that solves your issues.

I think it is strange that you are getting that many errors along the way. Are you following the newest version of the Getting Started App in nRF Connect for Desktop?

Best regards,

Simon

RE: New nRF9160 DK, and I'm unable to create the build environment and open the application sample in Segger.

jkase — Tue, 26 Nov 2019 14:05:17 GMT

Still no luck. Same error modal, with the same error log, re. "import six".

The git checkout master had failed, so I started with a fresh ncs installation, including the script updates.

The zephyr script had the following error, but did not indicate failure:

Requirement already satisfied: cffi>=1.6.0 in /Users/jeffkase/Library/Python/3.7/lib/python/site-packages (from milksnake>=0.1.2->cmsis-pack-manager>=0.2.7->pyocd==0.21.0->-r zephyr/scripts/requirements.txt (line 15)) (1.13.2)
Requirement already satisfied: pycparser in /Users/jeffkase/Library/Python/3.7/lib/python/site-packages (from cffi>=1.6.0->milksnake>=0.1.2->cmsis-pack-manager>=0.2.7->pyocd==0.21.0->-r zephyr/scripts/requirements.txt (line 15)) (2.19)
pyocd 0.21.0 has requirement pyyaml<6.0,>=5.1, but you'll have pyyaml 4.2b4 which is incompatible.
Installing collected packages: pyocd
Found existing installation: pyocd 0.19.0
Uninstalling pyocd-0.19.0:
Successfully uninstalled pyocd-0.19.0
Successfully installed pyocd-0.21.0

--jeff

RE: New nRF9160 DK, and I'm unable to create the build environment and open the application sample in Segger.

Simon — Tue, 26 Nov 2019 09:18:08 GMT

Open the command line in <..>/ncs/nrf and type in these commands:

git checkout master

git pull

git checkout v1.1.0

west update

Then delete the build folder and try to build the example again.

Best regards,

Simon

RE: New nRF9160 DK, and I'm unable to create the build environment and open the application sample in Segger.

jkase — Tue, 26 Nov 2019 03:38:42 GMT

Here is the error log from SES:

Loading solution asset_tracker.emProject
Executing load commands
/usr/local/bin/cmake -GNinja -DBOARD=nrf9160_pca10090ns -DBOARD_DIR=/Volumes/SilentOne/Nordic/ncs/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=/opt/gnuarmemb -B/Volumes/SilentOne/Nordic/ncs/nrf/applications/asset_tracker/build_nrf9160_pca10090ns -H/Volumes/SilentOne/Nordic/ncs/nrf/applications/asset_tracker -DPYTHON_EXECUTABLE=/usr/local/bin/python3 -DCMAKE_MAKE_PROGRAM=/usr/local/bin/ninja -DDTC=/usr/local/bin/dtc -D WEST=~/Library/Python/3.7/bin/west -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=/Applications/arm_segger_embedded_studio_v420a_macos_x64_nordic/html/configure_nordic_project_menuconfig.py
-- Using application from '/Volumes/SilentOne/Nordic/ncs/nrf/applications/asset_tracker'
Zephyr version: 1.14.99
-- Selected BOARD nrf9160_pca10090ns
-- Found west: /Users/jeffkase/Library/Python/3.7/bin/west (found suitable version "0.6.3", minimum required is "0.5.6")
CMake Error at /Volumes/SilentOne/Nordic/ncs/zephyr/cmake/zephyr_module.cmake:45 (message):
  Traceback (most recent call last):

    File "/Volumes/SilentOne/Nordic/ncs/zephyr/scripts/zephyr_module.py", line 19, in 
      import pykwalify.core
    File "/Users/jeffkase/Library/Python/3.7/lib/python/site-packages/pykwalify/core.py", line 25, in 
      from dateutil.parser import parse
    File "/Users/jeffkase/Library/Python/3.7/lib/python/site-packages/dateutil/parser/__init__.py", line 2, in 
      from ._parser import parse, parser, parserinfo, ParserError
    File "/Users/jeffkase/Library/Python/3.7/lib/python/site-packages/dateutil/parser/_parser.py", line 42, in 
      import six

  ModuleNotFoundError: No module named 'six'

Call Stack (most recent call first):
  /Volumes/SilentOne/Nordic/ncs/zephyr/cmake/app/boilerplate.cmake:252 (include)
  CMakeLists.txt:11 (include)


-- Configuring incomplete, errors occurred!
Project load failed
Reported error: solution load command failed (1)

RE: New nRF9160 DK, and I'm unable to create the build environment and open the application sample in Segger.

jkase — Tue, 26 Nov 2019 03:34:21 GMT

Just on a whim, I tried again to run the "pip3 install --user -r nrf/scripts/requirements.txt" command -- which succeeded! In the process, it install pygit2. The third pip3 installation also worked. That's the good news.

However, after launching SES 4.20a (and acquiring and installing yet another free license), Open nRF Connect SDK Project failed again. The error list is quite long:

and then:

So, still no luck opening the samples.

--jeff

RE: New nRF9160 DK, and I'm unable to create the build environment and open the application sample in Segger.

jkase — Tue, 26 Nov 2019 03:10:55 GMT

I followed your link, which took me to the page for installing the two tools on a unix system. I found a link for installing on macOS, which involved installing libgit2, then pygit2. The first step worked fine:

brew install libgit2

The second step, for installing pygit2 with:

pip3 install pygit2

leads to an error:

    Installing collected packages: pygit2
    Could not install packages due to an EnvironmentError: [Errno 13] Permission denied: '/Library/Python/3.7'
    Consider using the `--user` option or check the permissions.

Python 3.7 is not installed on my system, although Python 2.7 was installed as part of the multi-step process of installing the tools for your product.

Any other guesses on how to install the tools on my system, which is running macOS Catalina 10.15.1?

I get that this is a very new product, and that we're on the bleeding edge, here. But, this is one of the worst out of the box experiences I've had in 35 years of programming. We have customers that want to purchase your products, assuming we can integrate our software solution. First, it would be great to be able to build the sample code from your SDK.

Also, let's not lose track of the license key that has to be re-installed every time I open the newer version of SES. I've been using the SEGGER Embedded Studio for ARM 4.18 with our nRF52840 DK and Dongles. It was necessary to install the SEGGER Embedded Studio for ARM 4.20a, since the previous version did not have the Open nRF Connect SDK Project menu item. I currently have both installed, and likely there's a conflict. Will one version suffice for both development efforts?

If you have a macOS system, I'd be happy starting over with the installation process if there was an accurate set of steps that would solve these issues.

Thanks, again.

--jeff

RE: New nRF9160 DK, and I'm unable to create the build environment and open the application sample in Segger.

Simon — Mon, 25 Nov 2019 22:43:34 GMT

Try installing pygit2, as explained here.

Best regards,

Simon