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.

[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.