Startup Troubles on Dev Kit

[SteveHx]

I was able one time to power up the nRF9160 dev kit and see it connect to the cellular network and to nRF Cloud. Since then, it will only blink LED3, which indicates that it can't connect. I would like to re-flash the firmware, but I'm totally lost in all the circular links in the documentation. I have used the nRF52832 dev kit extensively so I'm quite familiar with the process, but it appears the nRF9160 dev kti adds several more layers of complexity. I would like to be able to load a simple "hello world" application, and then build on that with my application source code. Please guide me to some concise documentation.

[SteveHx]

I understand what it's asking for. What I need to know is where to get the GNU ARM toolchain - I don't think I have that installed. In any case, I always allow published installers to install to their default directories, because I've found way too many whose developers didn't bother to check what happens if the user uses a different directory - it often breaks the product. Where should I get the GNU ARM toolchain, in a version compatible with this toolchain?

[Didrik Rokhaug]

Sorry, I misunderstood what you were asking for. In the Getting Started Assistant there are two links at the bottom of step 1 "Install the toolchain":

Windows 32-bit Installer (Signed for Windows 7 and later)

Windows 32-bit Installer (Unsigned)

We recommend to install the toolchain into the c:\gnuarmemb folder

[SteveHx]

David Martin stepped in to help, but he's traveling today so asked that I come back to this ticket. So here's the update. We went back and started over with the Getting Started Assistant. Step 1 of the 4 steps is complete and appears successful. In step 2 "Clone the nRF Connect SDK", the first 3 subparts are complete. In the 4th part, installing Python modules, the very first install command is

pip3 install -r zephyr\scripts\requirements.txt

That results in an error message that David was unable to handle immediately. Here's the screen dump from the command box:

11:39:42.08 d:\296\FW\ncs> pip3 install -r zephyr\scripts\requirements.txt
Collecting wheel==0.30.0 (from -r zephyr\scripts\requirements.txt (line 1))
  Using cached https://files.pythonhosted.org/packages/0c/80/16a85b47702a1f47a63c104c91abdd0a6704ee8ae3b4ce4afc49bc39f9d9/wheel-0.30.0-py2.py3-none-any.whl
Collecting breathe==4.9.1 (from -r zephyr\scripts\requirements.txt (line 2))
  Using cached https://files.pythonhosted.org/packages/2c/a5/040234179dc9140be4a1cb4350af362327d001d0ca7e5bba4d580916ceb4/breathe-4.9.1-py2.py3-none-any.whl
Collecting sphinx==1.7.5 (from -r zephyr\scripts\requirements.txt (line 3))
  Using cached https://files.pythonhosted.org/packages/1b/9f/98d67201c5a6e1aececed03a44a819d0e32adba81414081e303cfaf8c54c/Sphinx-1.7.5-py2.py3-none-any.whl
Collecting docutils==0.14 (from -r zephyr\scripts\requirements.txt (line 4))
  Using cached https://files.pythonhosted.org/packages/36/fa/08e9e6e0e3cbd1d362c3bbee8d01d0aedb2155c4ac112b19ef3cae8eed8d/docutils-0.14-py3-none-any.whl
Collecting sphinx_rtd_theme (from -r zephyr\scripts\requirements.txt (line 5))
  Using cached https://files.pythonhosted.org/packages/60/b4/4df37087a1d36755e3a3bfd2a30263f358d2dea21938240fa02313d45f51/sphinx_rtd_theme-0.4.3-py2.py3-none-an
y.whl
Collecting sphinxcontrib-svg2pdfconverter (from -r zephyr\scripts\requirements.txt (line 6))
  Using cached https://files.pythonhosted.org/packages/79/83/d712a25303429570c641caa113d1282c27012bbd4157417d07829947a549/sphinxcontrib_svg2pdfconverter-1.0.1-p
y3-none-any.whl
Collecting junit2html (from -r zephyr\scripts\requirements.txt (line 7))
  Using cached https://files.pythonhosted.org/packages/69/93/f2ccef1136dba078dada0513c324bad9ffd2be9236229d09bce71e1338a8/junit2html-022.tar.gz
Requirement already satisfied: PyYAML>=3.13 in c:\python37\lib\site-packages (from -r zephyr\scripts\requirements.txt (line 8)) (4.2b4)
Collecting ply==3.10 (from -r zephyr\scripts\requirements.txt (line 9))
  Using cached https://files.pythonhosted.org/packages/ce/3d/1f9ca69192025046f02a02ffc61bfbac2731aab06325a218370fd93e18df/ply-3.10.tar.gz
Collecting hub==2.0 (from -r zephyr\scripts\requirements.txt (line 10))
  ERROR: Could not find a version that satisfies the requirement hub==2.0 (from -r zephyr\scripts\requirements.txt (line 10)) (from versions: 0.0.1, 0.1.0, 0.1.
1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.2, 0.2.0.1, 0.2.0.3, 0.2.0.4)
ERROR: No matching distribution found for hub==2.0 (from -r zephyr\scripts\requirements.txt (line 10))

11:40:06.99 d:\296\FW\ncs>

Your serve...... ;-)

[Didrik Rokhaug]

That is a known problem and has been fixed on the master branch.

What has happened is this:

The hub python module that is used by Zephyr has changed the name to git-spindle. Then, a new module was created with the name hub. If you edit the name of the package in the requirements file to "git-spindle", it should work.

Sadly, bugfixes like this have not been backported to the v1.0.0 release.

[SteveHx]

Do I need to just go back and start over? Your message above was not very clear, but I replaced "hub" in Requirements.txt in the Zephyr directory and it seems to be a little happier. However, there's still a red error message (boldface below) in the resulting text:

Requirement already satisfied: asn1crypto>=0.21.0 in c:\python37\lib\site-packages (from cryptography>=1.5->jwcrypto>=0.5.0->github3.py>=0.8.2->git-spindle==2.0
->-r zephyr\scripts\requirements.txt (line 10)) (0.24.0)
Requirement already satisfied: pycparser in c:\python37\lib\site-packages (from cffi!=1.11.3,>=1.8->cryptography>=1.5->jwcrypto>=0.5.0->github3.py>=0.8.2->git-s
pindle==2.0->-r zephyr\scripts\requirements.txt (line 10)) (2.19)
ERROR: pyocd 0.19.0 has requirement pyyaml<6.0,>=5.1, but you'll have pyyaml 4.2b4 which is incompatible.
Installing collected packages: wheel, docutils, sphinxcontrib-websupport, sphinx, breathe, sphinx-rtd-theme, sphinxcontrib-svg2pdfconverter, junit2html, ply, jw
crypto, uritemplate, github3.py, whelk, git-spindle, arrow, gitlint, pyelftools, websocket-client, sortedcontainers, intervaltree, pyusb, pywinusb, pyocd, windo
ws-curses, Pillow, more-itertools, zipp, importlib-metadata, pluggy, wcwidth, py, atomicwrites, pytest
  Found existing installation: docutils 0.15.2
    Uninstalling docutils-0.15.2:
      Successfully uninstalled docutils-0.15.2
  Found existing installation: Sphinx 2.2.0
    Uninstalling Sphinx-2.2.0:
      Successfully uninstalled Sphinx-2.2.0
  Running setup.py install for junit2html ... done
  Running setup.py install for ply ... done
  Running setup.py install for whelk ... done
  Running setup.py install for git-spindle ... done
  Running setup.py install for pyelftools ... done
  Running setup.py install for intervaltree ... done
  Running setup.py install for pyusb ... done
  Running setup.py install for pywinusb ... done
  Running setup.py install for pyocd ... done
Successfully installed Pillow-6.1.0 arrow-0.14.2 atomicwrites-1.3.0 breathe-4.9.1 docutils-0.14 git-spindle-2.0 github3.py-1.3.0 gitlint-0.12.0 importlib-metada
ta-0.23 intervaltree-3.0.2 junit2html-22 jwcrypto-0.6.0 more-itertools-7.2.0 pluggy-0.13.0 ply-3.10 py-1.8.0 pyelftools-0.24 pyocd-0.19.0 pytest-5.1.3 pyusb-1.0
.2 pywinusb-0.4.2 sortedcontainers-2.1.0 sphinx-1.7.5 sphinx-rtd-theme-0.4.3 sphinxcontrib-svg2pdfconverter-1.0.1 sphinxcontrib-websupport-1.1.2 uritemplate-3.0
.0 wcwidth-0.1.7 websocket-client-0.56.0 wheel-0.30.0 whelk-2.7.1 windows-curses-2.0.1 zipp-0.6.0

10:17:04.11 d:\296\FW\ncs>

[Didrik Rokhaug]

Sorry for being unclear. It is not necessary to start over. Just change "hub==2.0" to "git-spindle==2.0" (as I believe you did), and rerun the pip3 command.

Regarding the pyocd error, you can safely ignore it.

[SteveHx]

Okay, I've jumped thru all the hoops to reinstall the package. Now I'm uto the same place I was a week ago. When I attempt to open the Asset Tracker project, I get this error box:

Here's te option box, exactly as the tools auto-filled it:

[Didrik Rokhaug]

It still looks like the "GNU ARM Embedded Toolchain Directory" option is wrong. Can you confirm that the content of the folder you have provided in that option contains the same as:

Also, when building an application which uses the modem on the nRF91, you must build the application as non-secure. The board name should be "nrf9160_pca10090ns", notice the "ns" at the end.

[SteveHx]

I cannot find any directory that looks like your picture. I presume we're talking about where I unzipped EmbeddedStudio_ARM_Nordic_v420a_win_x64.zip. Per your suggestion, I unzipped it directly to C:\ (which seems to me like a bad idea to begin with, but you're the expert). I have tried setting the path in SES to both C:\ and c:\arm_segger_embedded_studio_v420a_win_x64_nordic, same result.

[Didrik Rokhaug]

I am not talking about the unzipped SES folder, but the ARM Embedded toolchain (arm-none-eabi-*). You should have installed it as the last step on page 1 of the Getting Started Assistant ("Install the toolchain"). If you did not, here are the links:

• Windows 32-bit Installer (Signed for Windows 7 and later)

• Windows 32-bit Installer (Unsigned)

The default install folder from the installer is: C:\Program Files (x86)\GNU Tools Arm Embedded\7 2018-q2-update.

The install folder for the ARM Embedded toolchain should have the same contents the picture from my last comment.

[SteveHx]

The ....2018-q2-update directory was already there, and looks as you showed except for the uninstaller. I have reinstalled that and now it looks just like yours.

When I open emStudio, I always get the dialog box shown below. I've tried answering both yes and no different times, and I still always get this. I suspect it indicates I'm still missing some critical step in this absurdly over-complicated setup process:

I have stopped at its first ocurrance this time, pending your answer as to the next step.

[Didrik Rokhaug]

That path is not in c:\arm_segger_embedded_studio_v420a_win_x64_nordic, and I cannot find the mentioned package in my folder.

Do you have another SES version installed?

If so, make sure that you are using the correct version (run the executable emStudio in the c:\arm_segger_embedded_studio_v420a_win_x64_nordic\bin folder).

If that does not help, you might be able to solve the issue by running the other SES version and fixing the problem there, or by uninstalling the other SES version.