Board names
The following tables list all boards and corresponding board targets for Nordic Semiconductor’s hardware platforms.
The board targets follow Zephyr’s Board terminology scheme and are used mostly when Configuring and building an application.
For example, the board target nrf54l15pdk@0.2.1/nrf54l15/cpuapp can be read as made of the following elements:
nrf54l15pdk |
@0.2.1 |
/nrf54l15 |
/cpuapp |
|
|---|---|---|---|---|
Board name |
Board revision |
Board qualifier for SoC |
Board qualifier for CPU cluster |
Board qualifier for variant (empty in this case) |
While the board name is always present, other elements, such as the board revision or the board qualifiers, are optional:
Board revision - You can use the board_name@board_revision board target to get extra devicetree overlays with new features available for a specific board version. The board version is printed on the label of your DK, just below the PCA number. For example, building for the
nRF9160dk@1.0.0/nrf9160board target adds the external flash on the nRF9160 DK that was available since board version v0.14.0.System on Chip (SoC) - When you choose a board target with this qualifier, you build for this specific SoC on this board. For example, building for the
thingy53/nrf5340/cpuappboard target builds the application core firmware for the nRF5340 SoC on the Nordic Thingy:53 prototyping platform.CPU cluster - You can use this board qualifier to build for a group of one or more CPU cores, all executing the same image within the same address space and in a symmetrical (SMP) configuration. The CPU cluster board qualifier varies depending on the SoC and SoC Series. For example, building for the
thingy53/nrf5340/cpunetboard target builds the network core firmware for Nordic Thingy:53, building fornrf54h20dk/nrf54h20/cpuappbuilds the application core firmware for the nRF54H20 DK, building fornrf54h20dk/nrf54h20/cpuradbuilds the radio core firmware for the nRF54H20 DK, and so on. Check the Product Specification of the given SoC for more information about the available CPU clusters.Variant - You can use this board qualifier to build for a particular type or configuration of a build for a combination of SoC and CPU cluster. In the nRF Connect SDK, variants are used for indicating the usage of Cortex-M Security Extensions (CMSE):
Entries without
*/ns- When you choose this target, you build the application core firmware as a single execution environment that does not use CMSE (Trusted Firmware-M (TF-M)).Entries with
*/ns(for example,cpuapp/ns) - When you choose this target, you build the application with CMSE. The application core firmware is placed in Non-Secure Processing Environment (NSPE) and uses Secure Processing Environment (SPE) for security features. By default, the build system automatically includes Trusted Firmware-M (TF-M) in SPE and merges it with NSPE.
Read more about separation of processing environments on the Processing environments page.
Note
This board name scheme was introduced in the nRF Connect SDK before the v2.7.0 release following changes in Zephyr v3.6.0. Read Migrating to the current hardware model, Zephyr’s Transition to the current hardware model, and refer to the conversion example Pull Request in Zephyr upstream if you have to port a board to the new model.
Boards included in sdk-zephyr
The following boards are defined in the zephyr/boards/nordic/ folder.
Also see the Supported Boards section in the Zephyr documentation.
Note
Despite being supported in Zephyr, the nRF Connect SDK does not support Nordic Thingy:52.
Hardware platform |
PCA number |
Board name |
Board targets |
|---|---|---|---|
nRF9161 DK |
PCA10153 |
|
|
nRF9160 DK |
PCA10090 |
|
|
|
|||
nRF9151 DK |
PCA10171 |
|
|
nRF9131 EK |
PCA10165 |
|
|
nRF54H20 DK |
PCA10175 |
|
|
nRF54L15 PDK |
PCA10156 |
|
|
nRF5340 DK |
PCA10095 |
|
|
nRF5340 Audio |
PCA10121 |
|
|
Thingy:53 |
PCA20053 |
|
|
nRF52840 DK |
PCA10056 |
|
|
|
|||
nRF52840 Dongle |
PCA10059 |
|
|
nRF52833 DK |
PCA10100 |
|
|
|
|||
nRF52 DK (nRF52832) |
PCA10040 |
|
|
|
|||
|
|||
nRF21540 DK |
PCA10112 |
|
Note
In nRF Connect SDK releases before v1.6.1:
The board target
nrf9160dk/nrf9160/nswas namednrf9160dk_nrf9160ns.The board target
nrf5340dk/nrf5340/cpuapp/nswas namednrf5340dk_nrf5340_cpuappns.
Boards included in sdk-nrf
The following boards are defined in the nrf/boards/nordic/ folder.
Hardware platform |
PCA number |
Board name |
Board targets |
|---|---|---|---|
nRF Desktop Gaming Mouse |
PCA20041 |
|
|
nRF Desktop Mouse |
PCA20044 |
|
|
nRF Desktop Mouse |
PCA20045 |
|
|
nRF Desktop Keyboard |
PCA20037 |
|
|
nRF Desktop Dongle |
PCA10111 |
|
|
nRF Desktop Dongle |
PCA10114 |
|
|
Thingy:91 |
PCA20035 |
|
|
|
|||
nRF7002 DK |
PCA10143 |
|
Shields included in sdk-nrf
The following shields are defined in the nrf/boards/shields folder.
Hardware platform |
PCA number |
Board name |
Board targets |
|---|---|---|---|
nRF7002 Evaluation Kit (EK) |
PCA63556 |
|
|
nRF7002 EK with emulated support for the nRF7001 IC |
PCA63556 |
|
|
nRF7002 EK with emulated support for the nRF7000 IC |
PCA63556 |
|
|
nRF7002 Expansion Board (EB) |
PCA63561 |
|
|
nRF21540 EK |
PCA63550 |
|