nRF9160DK

View API DocumentationView API documentation generated by Doxygen.

View on GitHubView this source code on GitHub.

Support for the nRF9160DK board

When using this board with RIOT, set the BOARD variable to nrf9160dk in your Makefile. If you follow the standard RIOT project structure, your Makefile should look like this:

# name of your application
APPLICATION = hello-world

# Change this to your board if you want to build for a different board
BOARD ?= nrf9160dk

# This has to be the absolute path to the RIOT base directory:
RIOTBASE ?= $(CURDIR)/RIOT

include $(RIOTBASE)/Makefile.include

Support for the nRF9160DK board

General information

The nRF9160DK is a devboard based on nRF9160 MCU which offers LTE-M and NB-IoT connectivity.

The board features four LEDs, four user buttons/switches and a reset button.

Flash the board

The board is flashed using JLink or nrfjprog software. Programs needs to be installed.

The process is automated in the usual make flash target.

Running as the TrustZone-M non-secure image

The nRF9160 implements ARM TrustZone-M. Selecting the trustzone_m_nonsecure module makes the shared nRF and Cortex-M code use the non-secure peripheral aliases, so that the application can run as the non-secure image.

USEMODULE += trustzone_m_nonsecure

Warning: The module on its own does not produce a working image. Without a secure image in flash that hands the peripherals over, the application faults at its first peripheral access.

A secure image has to be present in flash; the non-secure application does not boot on its own. The secure image configures which flash, RAM and peripherals are handed over to the non-secure world.

Accessing STDIO via UART

The STDIO is directly accessible via the USB port. On a Linux host, it’s generally mapped to /dev/ttyACM0.

Use the term target to connect to the board serial port

make BOARD=nrf9160dk -C examples/basic/hello-world term