The nRF52840 SoC on the nRF9160 DK (PCA10090) hardware provides support for the Nordic Semiconductor nRF52840 ARM Cortex-M4F CPU and the following devices:
- RADIO (Bluetooth Low Energy and 802.15.4)
- Segger RTT (RTT Console)
The nRF52840 SoC does not have any connection to the any of the LEDs, buttons, switches, and Arduino pin headers on the PCA10090 board. It is, however, possible to route some of the pins of the nRF52840 SoC to the nRF9160 SiP.
More information about the board can be found at the Nordic Low power cellular IoT  website. The Nordic Semiconductor documentation library  contains the processor’s information and the datasheet.
The nRF9160 DK has two external oscillators. The frequency of the slow clock is 32.768 kHz. The frequency of the main clock is 32 MHz.
The nrf52840_pca10090 board configuration supports the following hardware features:
Programming and Debugging¶
Make sure that the PROG/DEBUG switch on the DK is set to nRF52.
Follow the instructions in the Nordic nRF5x Segger J-Link page to install and configure all the necessary software. Further information can be found in Flashing. Then build and flash applications as usual (see Building an Application and Run an Application for more details).
Remember to set the PROG/DEBUG switch on the DK to nRF52.
See the following example for the Hello World application.
First, run your favorite terminal program to listen for output.
$ minicom -D <tty_device> -b 115200
<tty_device> with the port where the nRF52840 SoC is connected
to. Usually, under Linux it will be
port is connected to the nRF9160 SiP on the board.
Then build and flash the application in the usual way.
# From the root of the zephyr repository west build -b nrf52840_pca10090 samples/hello_world west flash
Board controller firmware¶
The board controller firmware is a small snippet of code that takes care of routing specific pins on nRF9160 SiP to different components on the board, such as LEDs, switches, and specific nRF52840 SoC pins.
When compiling a project for nrf52840_pca10090, the board controller firmware will be compiled and run automatically after the Kernel has been initialized.
By default, the board controller firmware will route the following:
|LEDs 1-4||physical LEDs|
|Buttons 1-2||physical buttons|
|Switches 1-2||physical switches|
|MCU Interface 0||Arduino pin headers|
|MCU Interface 1||Trace interface|
|MCU Interface 2||COEX interface|
It is possible to configure the behavior of the board controller firmware by using Kconfig and editing its options under “Board options”.