boards: Convert b_u585i_iot02a to HWM v2

Port the board to HWMv2.

Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>

boards/boards_legacy/arm/b_u585i_iot02a/Kconfig.board

@@ -1,8 +0,0 @@
-# B_U585I_IOT02A discovery kit configuration
-
-# Copyright (c) 2021 STMicroelectronics
-# SPDX-License-Identifier: Apache-2.0
-
-config BOARD_B_U585I_IOT02A
-	bool "STM32U585I IOT Discovery kit"
-	depends on SOC_STM32U585XX

boards/st/b_u585i_iot02a/Kconfig.b_u585i_iot02a

@@ -0,0 +1,5 @@
+# Copyright (c) 2021 STMicroelectronics
+# SPDX-License-Identifier: Apache-2.0
+
+config BOARD_B_U585I_IOT02A
+	select SOC_STM32U585XX

boards/st/b_u585i_iot02a/Kconfig.defconfig

@@ -5,9 +5,6 @@
 
 if BOARD_B_U585I_IOT02A
 
-config BOARD
-	default "b_u585i_iot02a"
-
 config SPI_STM32_INTERRUPT
 	default y
 	depends on SPI

boards/st/b_u585i_iot02a/b_u585i_iot02a_defconfig

@@ -1,8 +1,5 @@
 # SPDX-License-Identifier: Apache-2.0
 
-CONFIG_SOC_SERIES_STM32U5X=y
-CONFIG_SOC_STM32U585XX=y
-
 # enable uart driver
 CONFIG_SERIAL=y
 

boards/st/b_u585i_iot02a/b_u585i_iot02a_stm32u585xx_ns.yaml

@@ -1,4 +1,4 @@
-identifier: b_u585i_iot02a_ns
+identifier: b_u585i_iot02a/stm32u585xx/ns
 name: ST B_U585I_IOT02A Discovery kit non secure target
 type: mcu
 arch: arm

boards/st/b_u585i_iot02a/b_u585i_iot02a_stm32u585xx_ns_defconfig

@@ -1,8 +1,5 @@
 # SPDX-License-Identifier: Apache-2.0
 
-CONFIG_SOC_SERIES_STM32U5X=y
-CONFIG_SOC_STM32U585XX=y
-
 # enable uart driver
 CONFIG_SERIAL=y
 

boards/st/b_u585i_iot02a/board.yml

@@ -0,0 +1,7 @@
+board:
+  name: b_u585i_iot02a
+  vendor: st
+  socs:
+    - name: stm32u585xx
+      variants:
+        - name: ns

boards/st/b_u585i_iot02a/doc/index.rst

@@ -199,8 +199,7 @@ The Zephyr b_u585i_iot02a board configuration supports the following hardware fe
 +-----------+------------+-------------------------------------+
 
 The default configuration can be found in the defconfig file:
-
+:zephyr_file:`boards/st/b_u585i_iot02a/b_u585i_iot02a_defconfig`
-	``boards/arm/b_u585i_iot02a/b_u585i_iot02a_defconfig``
 
 Zephyr board options
 ====================
@@ -210,20 +209,20 @@ for building for both Secure and Non-Secure firmware.
 
 The BOARD options are summarized below:
 
-+----------------------+-----------------------------------------------+
++-------------------------------+-------------------------------------------+
-|   BOARD              | Description                                   |
+| BOARD                         | Description                               |
-+======================+===============================================+
++===============================+===========================================+
-| b_u585i_iot02a       | For building Secure (or Secure-only) firmware |
+| b_u585i_iot02a                | For building Trust Zone Disabled firmware |
-+----------------------+-----------------------------------------------+
++-------------------------------+-------------------------------------------+
-| b_u585i_iot02a_ns    | For building Non-Secure firmware              |
+| b_u585i_iot02a/stm32u585xx/ns | For building Non-Secure firmware          |
-+----------------------+-----------------------------------------------+
++-------------------------------+-------------------------------------------+
 
 Here are the instructions to build Zephyr with a non-secure configuration,
 using `tfm_ipc_` sample:
 
    .. code-block:: bash
 
-      $ west build -b b_u585i_iot02a_ns samples/tfm_integration/tfm_ipc/
+      $ west build -b b_u585i_iot02a/stm32u585xx/ns samples/tfm_integration/tfm_ipc/
 
 Once done, before flashing, you need to first run a generated script that
 will set platform option bytes config and erase platform (among others,
@@ -342,11 +341,11 @@ Building a secure/non-secure with Arm |reg| TrustZone |reg|
 The TF-M applications can be run on this board, thanks to its Arm |reg| TrustZone |reg|
 support.
 In TF-M configuration, Zephyr is run on the non-secure domain. A non-secure image
-can be generated using ``b_u585i_iot02a_ns`` as build target.
+can be generated using ``b_u585i_iot02a/stm32u585xx/ns`` as build target.
 
 .. code-block:: bash
 
-   $ west build -b b_u585i_iot02a_ns path/to/source/directory
+   $ west build -b b_u585i_iot02a/stm32u585xx/ns path/to/source/directory
 
 Note: When building the ``*_ns`` image with TF-M, ``build/tfm/api_ns/postbuild.sh`` bash script
 is run automatically in a post-build step to make some required flash layout changes.