boards: arm: nrf9151dk_nrf9151: Convert to v2

Converts the board to hwmv2

Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
This commit is contained in:
Jamie McCrae
2024-02-02 11:38:17 +00:00
committed by Carles Cufi
parent fba98a1763
commit c860f205de
19 changed files with 33 additions and 44 deletions

View File

@@ -1,14 +0,0 @@
# nRF9151 DK NRF9151 board configuration
# Copyright (c) 2023 Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0
if SOC_NRF9151_LACA
config BOARD_NRF9151DK_NRF9151
bool "nRF9151 DK NRF9151"
config BOARD_NRF9151DK_NRF9151_NS
bool "nRF9151 DK NRF9151 non-secure"
endif # SOC_NRF9151_LACA

View File

@@ -5,9 +5,6 @@
if BOARD_NRF9151DK_NRF9151 || BOARD_NRF9151DK_NRF9151_NS
config BOARD
default "nrf9151dk_nrf9151"
# For the secure version of the board the firmware is linked at the beginning
# of the flash, or into the code-partition defined in DT if it is intended to
# be loaded by MCUboot. If the secure firmware is to be combined with a non-

View File

@@ -0,0 +1,7 @@
# nRF9151 DK NRF9151 board configuration
# Copyright (c) 2023 Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0
config BOARD_NRF9151DK
select SOC_NRF9151_LACA

View File

@@ -0,0 +1,7 @@
board:
name: nrf9151dk
vendor: Nordic Semiconductor
socs:
- name: nrf9151
variants:
- name: 'ns'

View File

@@ -7,7 +7,7 @@ Overview
********
The nRF9151 DK (PCA10171) is a single-board development kit for evaluation and
development on the nRF9151 SiP for DECT NR+ and LTE-M/NB-IoT with GNSS. The nrf9151dk_nrf9151
development on the nRF9151 SiP for DECT NR+ and LTE-M/NB-IoT with GNSS. The ``nrf9151dk/nrf9151``
board configuration provides support for the Nordic Semiconductor nRF9151 ARM
Cortex-M33F CPU with ARMv8-M Security Extension and the following devices:
@@ -41,7 +41,7 @@ is 32 MHz.
Supported Features
==================
The nrf9151dk_nrf9151 board configuration supports the following
The ``nrf9151dk/nrf9151`` board configuration supports the following
hardware features:
+-----------+------------+----------------------+
@@ -120,7 +120,7 @@ Security components
Programming and Debugging
*************************
nrf9151dk_nrf9151 supports the Armv8m Security Extension, and by default boots
``nrf9151dk/nrf9151`` supports the Armv8m Security Extension, and by default boots
in the Secure state.
Building Secure/Non-Secure Zephyr applications with Arm |reg| TrustZone |reg|
@@ -128,9 +128,9 @@ Building Secure/Non-Secure Zephyr applications with Arm |reg| TrustZone |reg|
The process requires the following steps:
1. Build the Secure Zephyr application using ``-DBOARD=nrf9151dk_nrf9151`` and
1. Build the Secure Zephyr application using ``-DBOARD=nrf9151dk/nrf9151`` and
``CONFIG_TRUSTED_EXECUTION_SECURE=y`` in the application project configuration file.
2. Build the Non-Secure Zephyr application using ``-DBOARD=nrf9151dk_nrf9151_ns``.
2. Build the Non-Secure Zephyr application using ``-DBOARD=nrf9151dk/nrf9151/ns``.
3. Merge the two binaries together.
When building a Secure/Non-Secure application, the Secure application will
@@ -142,7 +142,7 @@ Building a Secure only application
==================================
Build the Zephyr app in the usual way (see :ref:`build_an_application`
and :ref:`application_run`), using ``-DBOARD=nrf9151dk_nrf9151``.
and :ref:`application_run`), using ``-DBOARD=nrf9151dk/nrf9151``.
Flashing
========
@@ -168,7 +168,7 @@ Then build and flash the application in the usual way.
.. zephyr-app-commands::
:zephyr-app: samples/hello_world
:board: nrf9151dk_nrf9151
:board: nrf9151dk/nrf9151
:goals: build flash
Debugging
@@ -189,7 +189,7 @@ the board are working properly with Zephyr:
You can build and flash the examples to make sure Zephyr is running correctly on
your board. The button and LED definitions can be found in
:zephyr_file:`boards/arm/nrf9151dk_nrf9151/nrf9151dk_nrf9151_common.dtsi`.
:zephyr_file:`boards/nordic_nrf/nrf9151dk/nrf9151dk_nrf9151_common.dtsi`.
References
**********

View File

@@ -1,4 +1,4 @@
identifier: nrf9151dk_nrf9151
identifier: nrf9151dk/nrf9151
name: nRF9151-DK-NRF9151
type: mcu
arch: arm

View File

@@ -1,9 +1,5 @@
# SPDX-License-Identifier: Apache-2.0
CONFIG_SOC_SERIES_NRF91X=y
CONFIG_SOC_NRF9151_LACA=y
CONFIG_BOARD_NRF9151DK_NRF9151_NS=y
# Enable MPU
CONFIG_ARM_MPU=y
@@ -13,15 +9,12 @@ CONFIG_HW_STACK_PROTECTION=y
# Enable TrustZone-M
CONFIG_ARM_TRUSTZONE_M=y
# This Board implies building Non-Secure firmware
CONFIG_TRUSTED_EXECUTION_NONSECURE=y
# enable GPIO
# Enable GPIO
CONFIG_GPIO=y
# Enable uart driver
# Enable UART driver
CONFIG_SERIAL=y
# enable console
# Enable console
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y

View File

@@ -1,4 +1,4 @@
identifier: nrf9151dk_nrf9151_ns
identifier: nrf9151dk/nrf9151/ns
name: nRF9151-DK-NRF9151-Non-Secure
type: mcu
arch: arm

View File

@@ -1,9 +1,5 @@
# SPDX-License-Identifier: Apache-2.0
CONFIG_SOC_SERIES_NRF91X=y
CONFIG_SOC_NRF9151_LACA=y
CONFIG_BOARD_NRF9151DK_NRF9151=y
# Enable MPU
CONFIG_ARM_MPU=y
@@ -13,12 +9,15 @@ CONFIG_HW_STACK_PROTECTION=y
# Enable TrustZone-M
CONFIG_ARM_TRUSTZONE_M=y
# enable GPIO
# This board implies building Non-Secure firmware
CONFIG_TRUSTED_EXECUTION_NONSECURE=y
# Enable GPIO
CONFIG_GPIO=y
# Enable uart driver
# Enable UART driver
CONFIG_SERIAL=y
# enable console
# Enable console
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y