Developing with nRF9160 DK
The nRF9160 DK is a hardware development platform used to design and develop application firmware on the nRF9160 LTE Cat-M1 and Cat-NB1 System in Package (SiP). See the nRF9160 DK Hardware guide for detailed information about the nRF9160 DK hardware. To get started with the nRF9160 DK, follow the steps in the Getting started with nRF9160 DK section.
The nRF9160 DK contains an nRF52840 SoC that is used to route some of the nRF9160 SiP pins to different components on the DK, such as LEDs and buttons, and to specific pins of the nRF52840 SoC itself. For a complete list of all the routing options available, see the nRF9160 DK board control section in the nRF9160 DK User Guide.
The nRF52840 SoC on the DK comes preprogrammed with a firmware. If you need to restore the original firmware at some point, download the nRF9160 DK board controller firmware from the nRF9160 DK product page. To program the HEX file, use nrfjprog (which is part of the nRF Command Line Tools).
If you want to route some pins differently from what is done in the preprogrammed firmware, program the Hello World sample instead of the preprogrammed firmware.
Build the sample (located under
ncs/zephyr/samples/hello_world) for the nrf9160dk_nrf52840 board.
To change the routing options, enable or disable the corresponding devicetree nodes for that board as needed.
See Board controller firmware for detailed information.
When you wish to use nRF Cloud’s REST Application Programming Interface (API), the DK requires a valid security certificate. This means that you need to update the certificate stored on the DK. To do so, you need to download a new certificate and then provision it to your DK.
Complete the following steps to download the nRF Cloud certificate for your nRF9160 DK:
Go to nRF Cloud and sign in.
Click Device Management in the left pane and select Provision Devices.
In the page that opens up, click the gear icon near the upper right corner and select Create JITP Certificates.
The Create JITP Certificates dialog box opens.
Enter the following information:
Device ID: the device ID is composed of nrf- and the 15-digit International Mobile (Station) Equipment Identity (IMEI) number that is printed on the label of your nRF9160 DK. For example, nrf-123456789012345.
Ownership code: the ownership code is the PIN or the hardware ID of your DK, and it is found on the label of your nRF9160 DK.
If the label contains a PIN in addition to the IMEI number, enter this pin. If it does not contain a PIN, enter the Hardware ID (HWID) HEX code, with or without colons. For example, AA:BB:CC:DD:EE:FF or AABBCCDDEEFF.
The ownership code serves as a password and proves that you own the specific nRF9160 DK. Therefore, do not share it with anyone.
Click Download Certificate and save the
.cert.jsonfile to a folder of your choice.
The certificate contains all the information that is needed to connect your nRF9160 DK to nRF Cloud. Therefore, do not share it with anyone.
After downloading the certificate, you must provision it to your nRF9160 DK.
The application firmware on the nRF9160 DK must support long AT commands up to 3 kB to provision the certificate. If you have updated the application firmware, this requirement is fulfilled.
Complete the following steps to provision the certificate:
Open the LTE Link Monitor app from nRF Connect for Desktop.
In the Settings pane of the side panel, deselect the checkbox for Automatic requests if it is selected.
If you have already inserted the SIM card into your DK, remove it before you continue.
Connect the DK to the computer with a micro-USB cable, and turn it on.
Click Select device and select the DK from the drop-down list. You can identify the nRF9160 DK by the fact that it has three COM ports.
If the three COM ports are not visible, press
Ctrl+Rin Windows or
command+Rin macOS to restart the Programmer application.
The drop-down text changes to the type of the selected device, with the SEGGER ID below the name.
Click Terminal in the navigation bar to switch to the terminal view.
AT+CFUN=4in the text field for AT commands and click Send. This AT command puts the modem to offline state.
AT+CFUN?in the text field for AT commands and click Send. This AT command returns the state of the modem.
The command should return
+CFUN: 4, which indicates that the modem is in offline state. If it returns a different value, repeat the previous step.
Click Certificate manager in the navigation bar to switch to the certificate manager view.
Click Load from JSON and select the
*.cert.jsonfile that you downloaded from nRF Cloud. Alternatively, you can drag and drop the file onto the GUI.
Ensure that the Security tag is set to
16842753, which is the security tag for nRF Cloud credentials.
Click Update certificate.
The log message “Certificate update completed” indicates that the certificate was provisioned successfully. If you encounter any errors, switch to the terminal view and check the output of the AT commands that were sent to the nRF9160 DK modem.
If you have connected your nRF9160 DK to nRF Cloud before, you must delete the device there after provisioning the certificate. To do so, open the entry for your device from the Devices view, then click the gear icon to the right of the device’s name, and select Delete Device. Then, add the nRF9160 DK again as described in Connecting the DK to nRF Cloud
In Zephyr, nRF9160 DK is divided into two different build targets:
nrf9160dk_nrf9160for firmware in the secure domain
nrf9160dk_nrf9160_nsfor firmware in the non-secure domain
In nRF Connect SDK releases before v1.6.1, the build target
nrf9160dk_nrf9160_ns was named
Make sure to select a suitable build target when building your application.
You can program applications and samples on the nRF9160 DK after obtaining the corresponding firmware images.
Download the latest application and modem firmware from the nRF9160 DK Downloads page.
To program applications using the Programmer app from nRF Connect for Desktop, follow the instructions in Updating the application firmware.
In Step 2, set the switch to nRF91 or nRF52 as appropriate for the application or sample you are programming.
Likewise, in Step 7, choose the
.hex file for the application you are programming.
When you update the application firmware on an nRF9160 DK, you must also update the modem firmware as described in Updating the modem firmware.
See Building and programming an application for more information on building and programming samples on nRF9160 DK.
nRF9160 DK v0.14.0 and later has additional hardware features that are not available on earlier versions of the DK:
External flash memory
To make use of these features, specify the board revision when building your application.
You must specify the board revision only if you use features that are not available in all board revisions. If you do not specify a board revision, the firmware is built for the default revision (v0.7.0). Newer revisions are compatible with the default revision.
To specify the board revision, append it to the build target when building.
For example, when building a non-secure application for nRF9160 DK v1.0.0, use
firstname.lastname@example.org as build target.
When building with SEGGER Embedded Studio, specify the board revision as additional CMake option (see Providing CMake options for instructions). For example, for nRF9160 DK v1.0.0, add the following CMake option: