nRF5340 DK
Overview
The nRF5340 DK (PCA10095) is a single-board development kit for evaluation and development on the Nordic nRF5340 System-on-Chip (SoC).
The nRF5340 is a dual-core SoC based on the Arm® Cortex®-M33 architecture, with:
a full-featured Arm Cortex-M33F core with DSP instructions, FPU, and Armv8-M Security Extension, running at up to 128 MHz, referred to as the application core
a secondary Arm Cortex-M33 core, with a reduced feature set, running at a fixed 64 MHz, referred to as the network core.
The nrf5340dk/nrf5340/cpuapp
build target provides support for the application
core on the nRF5340 SoC. The nrf5340dk/nrf5340/cpunet
build target provides
support for the network core on the nRF5340 SoC.
nRF5340 SoC provides support for the following devices:
ADC
CLOCK
FLASH
GPIO
IDAU
I2C
MPU
NVIC
PWM
RADIO (Bluetooth Low Energy and 802.15.4)
RTC
Segger RTT (RTT Console)
SPI
UARTE
USB
WDT
More information about the board can be found at the nRF5340 DK website [2]. The nRF5340 DK Product Specification [3] contains the processor’s information and the datasheet.
Hardware
nRF5340 DK has two external oscillators. The frequency of the slow clock is 32.768 kHz. The frequency of the main clock is 32 MHz.
Supported Features
The nrf5340dk
board supports the hardware features listed below.
- on-chip / on-board
- Feature integrated in the SoC / present on the board.
- 2 / 2
-
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files. -
vnd,foo
-
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.
Type |
Location |
Description |
Compatible |
---|---|---|---|
CPU |
on-chip |
ARM Cortex-M33F CPU1 |
|
ADC |
on-chip |
Nordic Semiconductor nRF family SAADC node1 |
|
on-board |
ADC channels exposed on Arduino Uno (R3) headers1 |
||
ARM architecture |
on-chip |
Nordic UICR (User Information Configuration Registers)1 |
|
on-chip |
Nordic nRF family DCNF (Domain Configuration)1 |
||
on-chip |
Nordic nRF family RESET (Reset Control)1 |
||
on-chip |
Nordic nRF family CTRL-AP (Control Access Port)1 |
||
on-chip |
Nordic EGU (Event Generator Unit)6 |
||
on-chip |
Nordic nRF family MUTEX (Mutual Exclusive Peripheral)1 |
||
on-chip |
Nordic KMU (Key Management Unit)1 |
||
on-chip |
Nordic SPU (System Protection Unit)1 |
||
Audio |
on-chip |
Nordic PDM (Pulse Density Modulation interface)1 |
|
Clock control |
on-chip |
Nordic nRF53X OSCILLATORS (Oscillator Control)1 |
|
on-chip |
Nordic nRF low-frequency crystal oscillator (nRF53 series)1 |
||
on-chip |
Nordic nRF high-frequency crystal oscillator (nRF53 series)1 |
||
on-chip |
Nordic nRF clock control node1 |
||
Comparator |
on-chip |
Nordic nRF COMP (analog COMParator)1 |
|
Counter |
on-chip |
Nordic nRF timer node3 |
|
Cryptographic accelerator |
on-chip |
ARM TrustZone CryptoCell 3121 |
|
Debug |
on-chip |
ARMv8 instrumentation trace macrocell1 |
|
Flash controller |
on-chip |
Properties defining the interface for the Nordic QSPI peripheral1 |
|
on-chip |
Nordic NVMC (Non-Volatile Memory Controller)1 |
||
GPIO & Headers |
on-chip |
NRF5 GPIO2 |
|
on-chip |
|||
on-board |
GPIO pins exposed on Arduino Uno (R3) headers1 |
||
on-board |
This is an abstract device responsible for forwarding pins between cores1 |
||
I2C |
on-chip |
||
I2S |
on-chip |
Nordic I2S (Inter-IC sound interface)1 |
|
IEEE 802.15.4 |
on-chip |
Nordic nRF IEEE 802.15.4 node1 |
|
Input |
on-board |
Group of GPIO-bound input keys1 |
|
Interrupt controller |
on-chip |
ARMv8-M NVIC (Nested Vectored Interrupt Controller)1 |
|
LED |
on-board |
Group of GPIO-controlled LEDs1 |
|
on-board |
Group of PWM-controlled LEDs1 |
||
Mailbox |
on-chip |
Nordic nRF family IPC (MBOX Interprocessor Communication)1 |
|
Miscellaneous |
on-chip |
Nordic FICR (Factory Information Configuration Registers)1 |
|
on-chip |
Nordic DPPIC (Distributed Programmable Peripheral Interconnect Controller)1 |
||
MMU / MPU |
on-chip |
ARMv8-M MPU (Memory Protection Unit)1 |
|
MTD |
on-board |
QSPI NOR flash supporting the JEDEC CFI interface1 |
|
on-chip |
Flash node1 |
||
on-chip |
Fixed partitions of a flash (or other non-volatile storage) memory1 |
||
Networking |
on-chip |
Nordic nRF family NFCT (Near Field Communication Tag)1 |
|
Pin control |
on-chip |
The nRF pin controller is a singleton node responsible for controlling pin function selection and pin properties1 |
|
Power management |
on-chip |
Nordic nRF power control node1 |
|
on-chip |
Nordic nRF family USBREG (USB Regulator Control)1 |
||
on-chip |
Nordic VMC (Volatile Memory Controller)1 |
||
PWM |
on-chip |
||
on-chip |
nRFx S/W PWM1 |
||
Regulator |
on-chip |
Nordic REGULATORS (voltage regulators control module) on nRF53X1 |
|
on-chip |
Nordic nRF5X regulator (fixed stage of the core supply)2 |
||
on-chip |
Nordic nRF53X regulator (high voltage stage of the main supply)1 |
||
Retained memory |
on-chip |
Nordic GPREGRET (General Purpose Register Retention) device2 |
|
RTC |
on-chip |
Nordic nRF RTC (Real-Time Counter)2 |
|
Sensors |
on-chip |
Nordic nRF quadrature decoder (QDEC) node2 |
|
Serial controller |
on-chip |
||
SPI |
on-chip |
||
SRAM |
on-chip |
Generic on-chip SRAM1 |
|
Timer |
on-chip |
ARMv8-M System Tick1 |
|
USB |
on-chip |
Nordic nRF52 USB device controller1 |
|
Watchdog |
on-chip |
See nRF5340 DK Product Specification [3] for a complete list of nRF5340 DK board hardware features.
Connections and IOs
LED
LED1 (green) = P0.28
LED2 (green) = P0.29
LED3 (green) = P0.30
LED4 (green) = P0.31
Security components
Implementation Defined Attribution Unit (IDAU [1]) on the application core. The IDAU is implemented with the System Protection Unit and is used to define secure and non-secure memory maps. By default, all of the memory space (Flash, SRAM, and peripheral address space) is defined to be secure accessible only.
Secure boot.
Programming and Debugging
The nrf5340dk
board supports the runners and associated west commands listed below.
flash | debug | rtt | attach | debugserver | |
---|---|---|---|---|---|
jlink | ✅ | ✅ (default) | ✅ | ✅ | ✅ |
nrfjprog | ✅ | ||||
nrfutil | ✅ (default) |
nRF5340 application core supports the Armv8-M Security Extension.
Applications built for the nrf5340dk/nrf5340/cpuapp
board by default
boot in the Secure state.
nRF5340 network core does not support the Armv8-M Security Extension. nRF5340 IDAU may configure bus accesses by the nRF5340 network core to have Secure attribute set; the latter allows to build and run Secure only applications on the nRF5340 SoC.
Building Secure/Non-Secure Zephyr applications with Arm® TrustZone®
Applications on the nRF5340 may contain a Secure and a Non-Secure firmware image for the application core. The Secure image can be built using either Zephyr or Trusted Firmware M [4] (TF-M). Non-Secure firmware images are always built using Zephyr. The two alternatives are described below.
Note
By default the Secure image for nRF5340 application core is built using TF-M.
Building the Secure firmware with TF-M
The process to build the Secure firmware image using TF-M and the Non-Secure firmware image using Zephyr requires the following steps:
Build the Non-Secure Zephyr application for the application core using
-DBOARD=nrf5340dk/nrf5340/cpuapp/ns
. To invoke the building of TF-M the Zephyr build system requires the Kconfig optionBUILD_WITH_TFM
to be enabled, which is done by default when building Zephyr as a Non-Secure application. The Zephyr build system will perform the following steps automatically:Build the Non-Secure firmware image as a regular Zephyr application
Build a TF-M (secure) firmware image
Merge the output image binaries together
Optionally build a bootloader image (MCUboot)
Note
Depending on the TF-M configuration, an application DTS overlay may be required, to adjust the Non-Secure image Flash and SRAM starting address and sizes.
Build the application firmware for the network core using
-DBOARD=nrf5340dk/nrf5340/cpunet
.
Building the Secure firmware using Zephyr
The process to build the Secure and the Non-Secure firmware images using Zephyr requires the following steps:
Build the Secure Zephyr application for the application core using
-DBOARD=nrf5340dk/nrf5340/cpuapp
andCONFIG_TRUSTED_EXECUTION_SECURE=y
andCONFIG_BUILD_WITH_TFM=n
in the application project configuration file.Build the Non-Secure Zephyr application for the application core using
-DBOARD=nrf5340dk/nrf5340/cpuapp/ns
.Merge the two binaries together.
Build the application firmware for the network core using
-DBOARD=nrf5340dk/nrf5340/cpunet
.
When building a Secure/Non-Secure application for the nRF5340 application core, the Secure application will have to set the IDAU (SPU) configuration to allow Non-Secure access to all CPU resources utilized by the Non-Secure application firmware. SPU configuration shall take place before jumping to the Non-Secure application.
Building a Secure only application
Build the Zephyr app in the usual way (see Building an Application
and Run an Application), using -DBOARD=nrf5340dk/nrf5340/cpuapp
for
the firmware running on the nRF5340 application core, and using
-DBOARD=nrf5340dk/nrf5340/cpunet
for the firmware running
on the nRF5340 network core.
Flashing
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 you can build and flash applications as usual (Building an Application and Run an Application for more details).
Warning
The nRF5340 has a flash read-back protection feature. When flash read-back
protection is active, you will need to recover the chip before reflashing.
If you are flashing with west, run
this command for more details on the related --recover
option:
west flash -H -r nrfutil --skip-rebuild
Note
Flashing and debugging applications on the nRF5340 DK requires upgrading the nRF Command Line Tools to version 10.12.0. Further information on how to install the nRF Command Line Tools can be found in Flashing.
Here is an example for the Hello World application running on the nRF5340 application core.
First, run your favorite terminal program to listen for output.
$ minicom -D <tty_device> -b 115200
Replace <tty_device>
with the port where the board nRF5340 DK
can be found. For example, under Linux, /dev/ttyACM0
.
Then build and flash the application in the usual way.
# From the root of the zephyr repository
west build -b nrf5340dk/nrf5340/cpuapp samples/hello_world
west flash
Debugging
Refer to the Nordic nRF5x Segger J-Link page to learn about debugging Nordic boards with a Segger IC.