Getting Started Issues with the nRF9160, not connecting to LTE, Failed example builds

[AaronS]

Hey anyone,

Going through the 'getting started' process for the nRF 9160 DK I'm having some issues. 

I've followed the steps to install nRF connect etc. suggested in the nordic documentation as well as followed along in the unboxing instructional video provided by nordic (https://www.youtube.com/watch?v=rMvW3HXLErk).

However when I try to test the 'asset tracker' application to verify the LTE/GPS functionality it doesn't seem to work and I'm running into the following issue:

 - The reset button appears to have no impact when it is pressed

 - LED 3 and LED 4 never light up to indicate any action regarding the LTE connection process

 - I'm thus unable to add my device in the nRF cloud solution

I've also tried to build and run an example program in the segger embedded studio IDE (I've updated the modem firmware to the latest using the programmer tool and I'm using nrf connect sdk version 1.4.0, should I be using a newer one?) and even the example programs fail, getting the following terminal output:

Im extremely new to nordic devices and the nRF SDK etc. so any help is greatly appreciated!

[Marte Myrvold]

Hi,

You should be fine with using v1.4.0. The latest official release right now is v1.4.2, and if you want to, you can check out the release notes for v1.4.1 and v1.4.2 here and here to see the changes between the releases. You can also see a list of known issues in v1.4.0 here.

How did you install NCS? Did you do it manually, or with either the Toolchain Manager or Getting Started Assistant in nRF Connect for Desktop? Which example did you try to build?

Could you please download the LTE Link Monitor application in nRF Connect for Desktop and open your nRF9160 DK there? It should print the log from the device, as well as show you the status of the modem and LTE connection in the upper right corner.

Best regards,

Marte

[AaronS]

I installed it via the toolchain manager (idk if it matters but my current OS is windows 10). Also I don't remember why it stuck out to me when I was installing everything but I believe there was a popup for the segger J-link installation that didn't seem as seamless as the rest of the process, is it possible that this was installed improperly and could be causing the issues?

The example that I tried to build was the 'at.client' project.

The LTE link Monitor was another thing that was giving me issues. I've tried using it previously to see if it could provide any insight into what was wrong however

 - the modem status says power off

 - the terminal has nothing printed out to it even after I try to reset the device via the onboard reset button

 - all of the preset command buttons (ie AT, AT+CFUN?, etc. return a timed out error in the log.

Thanks,

Aaron

[Marte Myrvold]

Hi,

If you install it with the Toolchain Manager on Windows 10 it should work out of the box. How did you open SES (SEGGER Embedded Studio)? When you install it with the Toolchain Manager you have to open it there as well, using the "Open IDE" button.

Could you open the Asset Tracker application in SES and try to build it? Please make sure to select the correct configurations when you open the project, such as the board name, which should be nrf9160dk_nrf9160ns. If you're able to build it, please flash it to your board and see whether this affects anything.

You already mention that you've updated the modem firmware, and I assume you updated it to v1.2.3. NCS v1.4.0 has been tested with modem firmware v1.2.2, as you can see here, but it should work with v1.2.3 as well. You could also update to NCS v1.4.2, which has been tested with modem firmware v1.2.3.

Are you using the iBasis SIM card provided with the DK or are you using a SIM card from another provider? If the former, have you added the SIM card to your account in nRF Cloud?

Best regards,

Marte

[AaronS]

I've been opening SES through the toolchain manager via the Open IDE button.

I've been using v1.2.3 for the modem firmware however just tried updating the board with v1.2.2 to see if it would make a difference. When trying to build the asset tracker application the build still fails with the following terminal output

Also I am using the provided iBasis sim card and it has already been added to my account in the nRF Cloud

Thanks,

Aaron

[Marte Myrvold]

Hi Aaron,

This might be a problem with the path length, as I've seen several cases where a too long path might cause problems in Windows. I would recommend reinstalling the SDK under C:/ncs/ instead. You can change the default installation directory in the settings in Toolchain Manager, or you can choose another directory when installing. As I mentioned before, installing it with the Toolchain Manager should install all necessary tools, so you shouldn't be missing any. Another thing you can try is to update the toolchain by pressing the arrow facing down next to "Open IDE" and selecting "Update toolchain". Another option is to install the SDK manually. This does however require more work, but it's an option if you run into problems during the installation using Toolchain Manager, or for those who prefer to install it manually. I would recommend first trying the two Toolchain Manager options I mentioned, installing it in another location and updating toolchain, before installing it manually.

Since the modem says powered off in LTE Link Monitor and the terminal window doesn't print any logs, it's hard to say why you're unable to connect. With both Asset Tracker, which is what new nRF9160 DKs are programmed with, and AT Client, you should get some logs when the device starts up.

Since you're having problems building applications in SES, I have created some precompiled firmware images you can try to program to your device, so we can try to figure out why you're unable to connect to nRF Cloud. You can program them with the Programmer application in nRF Connect for Desktop. I've attached the AT Client sample and Asset Tracker application. Both of them are from v1.4.0 of NCS since that's what you said you've been using. If you want another version of NCS, please let me know and I'll share that as well.

5287.at_client_merged.hex

asset_tracker_merged.hex

If you're able to program these to your device and get logs in LTE Link Monitor, please share the logs. You can download the log file from LTE Link Monitor by clicking the "Open log file" button.

Best regards,

Marte