nRF9131 EK
Overview
The nRF9131 EK (PCA10165) is a single-board evaluation kit for the nRF9131 SiP
for DECT NR+ and LTE-M/NB-IoT with GNSS.
The nrf9131ek/nrf9131 board configuration provides support for the Nordic Semiconductor nRF9131 ARM
Cortex-M33F CPU with ARMv8-M Security Extension and the following devices:
ADC
CLOCK
FLASH
GPIO
I2C
MPU
NVIC
PWM
RTC
Segger RTT (RTT Console)
SPI
UARTE
WDT
IDAU
The Nordic Semiconductor TechDocs [2] will soon contain the processor’s information and the datasheet.
Hardware
nRF9131 EK 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 nrf9131ek 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 |
|
ARM architecture |
on-chip |
Nordic EGU (Event Generator Unit)6 |
|
on-chip |
Nordic KMU (Key Management Unit)1 |
||
on-chip |
Nordic nRF family CTRL-AP (Control Access Port)1 |
||
on-chip |
Nordic SPU (System Protection Unit)1 |
||
on-chip |
Nordic UICR (User Information Configuration Registers)1 |
||
Audio |
on-chip |
Nordic PDM (Pulse Density Modulation interface)1 |
|
Clock control |
on-chip |
Nordic nRF clock control node1 |
|
Counter |
on-chip |
Nordic nRF timer node3 |
|
Cryptographic accelerator |
on-chip |
ARM TrustZone CryptoCell 3101 |
|
Flash controller |
on-chip |
Nordic NVMC (Non-Volatile Memory Controller)1 |
|
GPIO & Headers |
on-chip |
NRF5 GPIO1 |
|
on-chip |
|||
I2C |
on-chip |
||
I2S |
on-chip |
Nordic I2S (Inter-IC sound interface)1 |
|
Input |
on-board |
Group of GPIO-bound input keys1 |
|
Interrupt controller |
on-chip |
ARMv8-M NVIC (Nested Vectored Interrupt Controller)1 |
|
IPC |
on-chip |
Nordic nRF family IPC (Interprocessor Communication)1 |
|
LED |
on-board |
Group of GPIO-controlled LEDs1 |
|
on-board |
Group of PWM-controlled LEDs1 |
||
Multi-Function Device |
on-board |
Nordic nPM13001 |
|
Miscellaneous |
on-chip |
Nordic DPPIC (Distributed Programmable Peripheral Interconnect Controller)1 |
|
on-chip |
Nordic FICR (Factory Information Configuration Registers)1 |
||
MMU / MPU |
on-chip |
ARMv8-M MPU (Memory Protection Unit)1 |
|
MTD |
on-chip |
Flash node1 |
|
on-chip |
Fixed partitions of a flash (or other non-volatile storage) memory1 |
||
on-board |
Properties supporting Zephyr spi-nor flash driver (over the Zephyr SPI API) control of serial flash memories using the standard M25P80-based command set1 |
||
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 VMC (Volatile Memory Controller)1 |
|
on-chip |
Nordic nRF power control node1 |
||
PWM |
on-chip |
||
on-chip |
nRFx S/W PWM1 |
||
Regulator |
on-chip |
Nordic REGULATORS (voltage regulators control module) on nRF91X1 |
|
on-board |
Nordic nPM1300 PMIC1 |
||
Retained memory |
on-chip |
Nordic GPREGRET (General Purpose Register Retention) device2 |
|
RTC |
on-chip |
Nordic nRF RTC (Real-Time Counter)2 |
|
Sensors |
on-board |
NPM1300 PMIC Charger1 |
|
Serial controller |
on-chip |
||
SPI |
on-chip |
||
SRAM |
on-chip |
Generic on-chip SRAM description1 |
|
Timer |
on-chip |
ARMv8-M System Tick1 |
|
Watchdog |
on-chip |
Nordic nRF family WDT (Watchdog Timer)1 |
Connections and IOs
LED
LED (red) = P0.29
LED (green) = P0.30
LED (blue) = P0.31
Security components
Programming and Debugging
nrf9131ek/nrf9131 supports the Armv8m Security Extension, and by default boots
in the Secure state.
Building Secure/Non-Secure Zephyr applications with Arm® TrustZone®
Applications on the nRF9131 may contain a Secure and a Non-Secure firmware image. The Secure image can be built using either Zephyr or Trusted Firmware M [3] (TF-M). Non-Secure firmware images are always built using Zephyr. The two alternatives are described below.
Note
By default the Secure image for nRF9131 is built using TF-M.
Building the Secure firmware using Zephyr
The process requires the following steps:
Build the Secure Zephyr application using
-DBOARD=nrf9131ek/nrf9131andCONFIG_TRUSTED_EXECUTION_SECURE=yin the application project configuration file.Build the Non-Secure Zephyr application using
-DBOARD=nrf9131ek/nrf9131/ns.Merge the two binaries together.
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 action:
Build the Non-Secure Zephyr application using
-DBOARD=nrf9131ek/nrf9131/ns. To invoke the building of TF-M the Zephyr build system requires the Kconfig optionBUILD_WITH_TFMto 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 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.
When building a Secure/Non-Secure application, 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=nrf9131ek/nrf9131.
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 build and flash applications as usual (see Building an Application and Run an Application for more details).
Here is an example for the Hello World application.
First, run your favorite terminal program to listen for output.
$ minicom -D <tty_device> -b 115200
Replace <tty_device> with the port where the nRF9131 EK
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 nrf9131ek/nrf9131 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.