treewide: bring HWMv2

This brings HWMv2 (Hardware Model Version 2) into NCS. All boards have been ported, and samples/documentation/build system adjusted accordingly. Signed-off-by: Gerard Marull-Paretas <[email protected]> Signed-off-by: Jamie McCrae <[email protected]> Signed-off-by: Torsten Rasmussen <[email protected]>
michalek-no · Apr 30, 2024 · d7a19af · d7a19af
1 parent 287b1e6
commit d7a19af
Show file tree

Hide file tree

Showing 713 changed files with 4,900 additions and 5,760 deletions.
diff --git a/.github/test-spec.yml b/.github/test-spec.yml
@@ -266,10 +266,9 @@
 
 "CI-desktop-test":
   - "applications/nrf_desktop/**/*"
-  - "boards/arm/*dmouse*/**/*"
-  - "boards/arm/*kbd*/**/*"
-  - "boards/arm/*dongle*/**/*"
-  - "boards/arm/*gmouse*/**/*"
+  - "boards/nordic/*mouse/**/*"
+  - "boards/nordic/*kbd/**/*"
+  - "boards/nordic/*dongle/**/*"
   - "cmake/*"
   - "drivers/sensor/pmw3360/**/*"
   - "drivers/sensor/paw3212/**/*"

diff --git a/applications/asset_tracker_v2/Kconfig.sysbuild b/applications/asset_tracker_v2/Kconfig.sysbuild
@@ -5,9 +5,9 @@
 #
 
 config SECURE_BOOT
-	default y if $(BOARD) = "nrf9160dk_nrf9160_ns"
+	default y if BOARD_NRF9160DK_NRF9160_NS
 
 config SECURE_BOOT_APPCORE
-	default y if $(BOARD) = "nrf9160dk_nrf9160_ns"
+	default y if BOARD_NRF9160DK_NRF9160_NS
 
 source "${ZEPHYR_BASE}/share/sysbuild/Kconfig"
diff --git a/applications/asset_tracker_v2/doc/asset_tracker_v2_description.rst b/applications/asset_tracker_v2/doc/asset_tracker_v2_description.rst
@@ -107,7 +107,7 @@ The application provides predefined configuration files for typical use cases.
 Following are the available configuration files:
 
 * :file:`prj.conf` - Configuration file for all build targets.
-* :file:`boards/<BOARD>.conf` - Configuration file specific for a build target specified with **<BOARD>**, where **<BOARD>** is the build target, for example ``nrf9161dk_nrf9161_ns``.
+* :file:`boards/<BOARD>.conf` - Configuration file specific for a build target specified with **<BOARD>**, where **<BOARD>** is the build target, for example ``nrf9161dk/nrf9161/ns``.
   This file is automatically merged with the :file:`prj.conf` file when you build for that target.
 
 The :file:`include/<BOARD>/led_state_def.h` header file describes the LED behavior of the CAF LEDs module.

diff --git a/applications/asset_tracker_v2/doc/cloud_module.rst b/applications/asset_tracker_v2/doc/cloud_module.rst
@@ -99,7 +99,7 @@ This application implements full modem FOTA for the nRF91x1 DKs and for the nRF9
 To enable full modem FOTA, add the ``-DEXTRA_CONF_FILE=overlay-full_modem_fota.conf`` parameter to your build command.
 
 Also, specify your development kit version by appending it to the board name.
-For example, if your development kit version is 1.0.1, use the board name ``nrf9160dk_nrf9160_ns@1_0_1`` in your build command.
+For example, if your development kit version is 1.0.1, use the board name ``[email protected]/nrf9160/ns`` in your build command.
 
 Connection awareness
 ====================

diff --git a/...lude/nrf9151dk_nrf9151_ns/led_state_def.h → ...cker_v2/include/nrf9151dk/led_state_def.h b/...lude/nrf9151dk_nrf9151_ns/led_state_def.h → ...cker_v2/include/nrf9151dk/led_state_def.h
diff --git a/...lude/nrf9160dk_nrf9160_ns/led_state_def.h → ...cker_v2/include/nrf9160dk/led_state_def.h b/...lude/nrf9160dk_nrf9160_ns/led_state_def.h → ...cker_v2/include/nrf9160dk/led_state_def.h
diff --git a/...lude/nrf9161dk_nrf9161_ns/led_state_def.h → ...cker_v2/include/nrf9161dk/led_state_def.h b/...lude/nrf9161dk_nrf9161_ns/led_state_def.h → ...cker_v2/include/nrf9161dk/led_state_def.h
diff --git a/...clude/thingy91_nrf9160_ns/led_state_def.h → ...acker_v2/include/thingy91/led_state_def.h b/...clude/thingy91_nrf9160_ns/led_state_def.h → ...acker_v2/include/thingy91/led_state_def.h
diff --git a/...lude/thingy91x_nrf9151_ns/led_state_def.h → ...cker_v2/include/thingy91x/led_state_def.h b/...lude/thingy91x_nrf9151_ns/led_state_def.h → ...cker_v2/include/thingy91x/led_state_def.h