This section is not maintained, and the content can be outdated. Please see https://docs.nordicsemi.com/ for updated documentation and guides.

Getting Started with nRF9160 DK

Akash Patel

2020-08-04: The content of this guide is now covered in the documentation on Infocenter. For the most up-to-date Getting started guide with nRF9160 DK please follow this link. 

2020-03-09: Updated tutorial to support nRF Connect SDK (NCS) v1.2.0 (Screenshots may not be updated with the latest version number but the text is)

2019-07-31: Updated tutorial to support nRF Connect SDK (NCS) v1.0.0

2019-05-21: Updated tutorial to cover the changes in the nRF Connect SDK

  • in reply to Devang08

    Hi Devang,

    Can you click “OK” on the dialog message with the error? I believe it should then open Segger Embedded Studio. From there, can you please give the Segger Output for the error that you are receiving?

    Please take this information and post it as a ticket in the DevZone. You may have missed one of the dependencies and you should be able to spot that from the output.

    Regards,

    Akash

  • Nice Article, I have nRF9160-DK, trying to connect with network with sim card from another provider (They have CAT-M and NB-IoT coverage). I tried to connect module with LTE monitoring app, it always time out. When I tried with AT Client Application with these config and files. 

    but I am getting error, can be seen below.

    During the installation, I varified every steps and working fine. 

    Anybody has similar problem ? 

    Have a nice day..:) 

  • in reply to Harry Wei

    Hi Harry,

    If you want to use the verify steps here, you should set sourcecode_root on the right side of the window to the folder where you will be creating the ncs directory.

    For example, sourcecode_root being C:\Nordic_SDK means you will have the ncs directory at C:\Nordic_SDK\ncs

    Regards,

    Akash Patel

  • in reply to Harry Wei

    I have solved this problem.it is OK to set the path on the installation interface (upper right corner of the installation interface)

  • in reply to Harry Wei

    I have tried to regard "sourcecode_root" as a folder, but there are some errors.I guess sourcecode_root lacks some necessary descriptions

Terms of service