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]

We are going in circles. I am right back where I was two weeks ago.

I have confirmed only one emStudio installed, via Windows Control Panel Programs and Features. I am running exactly that emStudio, in the recommended installation directory. Every time I open it, I get that same dialog box shown two messages above. Whether I answer yes or no, I then get the request to activate. I activate tho Nordic license (corrupting my legal company name because the box won't accept a comma in the company name), and the next time I open emStudio, I'm right back at the beginning of this paragraph.

My client is getting impatient to see some results. So am I.

[Didrik Rokhaug]

I am still working on a solution to the outdated package problem. In the meantime, if you press "yes to all", are you then able to open and build a sample project?

That should make the license "stick", and there does not seem to be anything wrong with the hex files produced by SES after pressing "yes to all", so you would at least be able to start development while you are waiting for a permanent solution on the outdated package.

[SteveHx]

Still doesn't work. I'm working with David Martin, and we're still getting this:

[SteveHx]

Another possible clue: I get this error box:

If I navigate to that specific file and dblclick, another instance of SES opens, and immediately gives me the same box again.

[Didrik Rokhaug]

It still looks like the "GNU ARM Embedded Toolchain Directory" is wrong. I recreated your issue on a Windows 10 VM, by setting it to the path of SES, instead of the path of the ARM embedded toolchain. See pictures:

If you change the "GNU ARM Embedded Toolchain Directory" option to the folder where you installed the ARM Embedded toolchain, then the error goes away, and you should be able to load and build the project. If you did not change the install directory in the ARM Embedded toolchain installer, the correct path should be C:\Program Files (x86)\GNU Tools Arm Embedded\7 2018-q2-update. I have attached pictures of the correct setup (on my VM), along with the content of the folder you should point to (when setting the path, only folders will be displayed, so you will not see the uninstaller):

If you still cannot get it to work, please send pictures of the SES options window, and the folder pointed to by the "GNU ARM Embedded Toolchain Directory" option.

Edit: Also, when opening a project, make sure that the "Clean Build Directory" checkbox is checked, to avoid risking using old settings.