Further improvements of this example project (#14)

HansSchneebauer · web-flow · commit 4e3de50337ef · 2026-05-06T16:53:08.000+02:00
* - added STM32H7B3I-DK board
- removed NXP FRDM-MCXN947 board
- added RTT debug configuration for STM32H7B3I-DK board
- corrected the README.md file which described two different csolution files

* Further improvements in the README.md file, and added a screenshot of the Zephyr Terminal in the video folder. Also updated the zephyr.csolution.yml file for a more precise Zephyr board selection

* Update VSCode settings and add STM32H7B3I-DK debug configuration files
diff --git a/.vscode/settings.json b/.vscode/settings.json
@@ -5,5 +5,13 @@
         "VIRTUAL_ENV": "$HOME/zephyrproject/.venv",
     },
     "debug.hideSlowPreLaunchWarning": true,
-    "debug.showInStatusBar": "never"
+    "debug.showInStatusBar": "never",
+    "memory-inspector.addressPadding": "32bit",
+    "memory-inspector.groupings.groupsPerRow": "Autofit",
+    "memory-inspector.groupings.MAUsPerGroup": 4,
+    "memory-inspector.scrollingBehavior": "Auto-Append",
+    "clangd.arguments": [
+        "--compile-commands-dir=c:\\Kunden\\RTT_Examples\\CMSIS-Zephyr\\out\\blinky\\STM32H7B3I-DK\\Debug"
+    ],
+    "cmsis-csolution.autoDebugLaunch": true
 }
diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
 # CMSIS-Zephyr
 
-This repository contains an exemplary CMSIS solution file that can be used to build two Zephyr basic examples on two
+This repository contains an exemplary CMSIS solution file that can be used to build two Zephyr basic examples on multiple
 different development boards. It can be easily adapted to other boards or examples. It uses Zephyr's `west` build
 system to create the executable file for an application and the
 [Arm CMSIS Debugger](https://marketplace.visualstudio.com/items?itemName=Arm.vscode-cmsis-debugger) to flash download
@@ -14,18 +14,23 @@ and run the image on the target hardware.
 
 - Clone this repository onto your machine.
 - Open it in VS Code. It should install required extensions automatically.
-- In the CMSIS view, click on **...**, use **Open Solution in Workspace**, and choose "zephyr".
 - Press the **Manage Solution Settings** button. In the dialog, select the target board and application.
 - Press the **Build solution** button to build the example.
 - Press the **Load & Debug application** button to start a debug session.
 
 > [!NOTE]
-> Check that the **Arm CMSIS Solution** extension is at least v1.66.0.
+> - Check that the **Arm CMSIS Solution** extension is at least v1.66.0.
+> - If you are working under Windows, you will get the error `exec: "west": executable file not found in %PATH%` because in this example the path to the west build system is set up for Linux/Mac. Open the settings of the **Arm CMSIS Solution** extension and change the `PATH` environment variable of the **Workspace** from `$HOME/zephyrproject/.venv/bin` to `$HOME/zephyrproject/.venv/Scripts`.
+
 
 ### Switch to a different board
 
-If you want to run the examples on a different board, simply edit the `Examples/Blinky/blinky.csolution.yml` or
-`Examples/Threads/threads.csolution.yml` files:
+If you want to run the examples on a different board, simply extend the `zephyr.csolution.yml` file:
+- Search for your [development board](https://www.keil.arm.com/boards/) and select it.
+- Follow the link to the **Device** and its **CMSIS Pack** (DFP) and copy the text in the **Add to CMSIS Solution** box into the 'zephyr.csolution.yml' file into the 'packs:' list.
+- Go back to the board page and follow the link to the **CMSIS Pack** (BSP). Again, copy the text in the **Add to CMSIS Solution** box into the 'zephyr.csolution.yml' below the DFP.
+- Add a new [Target Type](https://open-cmsis-pack.github.io/cmsis-toolbox/YML-Input-Format/#target-types) and specify the board name after the '- type' token.
+- Specify the board vendor and boardname as well as the device vendor and the device name. Use the names from the CMSIS board and device pages.
 
 ```yml
   # List the packs that define the device and/or board.
@@ -41,16 +46,15 @@ If you want to run the examples on a different board, simply edit the `Examples/
 ```
 
 If your development board's [CMSIS board name](https://www.keil.arm.com/boards/) and
-[Zephyr board name](https://docs.zephyrproject.org/latest/boards/index.html#) do not match, you need to add the correct
-Zephyr board name like this:
+[Zephyr board name](https://docs.zephyrproject.org/latest/boards/index.html#) do not match, you need to add the correct Zephyr board name with the variable `west-board:`. This variable may contain the `Board_Name`, or the `Board_Name/SoC_Name` or the `Board_Name/SoC_Name/Core_Name`, depending on the complexity of the board and SoC. See the paragraph **Supported Features** on the Zephyr board pages for more details.
 
 ```yml
   target-types:
     - type: B-L475-IOT01A
       board: STMicroelectronics::B-L475E-IOT01A
       device: STMicroelectronics::STM32L475VGTx
       variables:
-        - west-board: disco_l475_iot1
+        - west-board: disco_l475_iot1/stm32l475xx
 ```
 
 > [!NOTE]
@@ -59,6 +63,8 @@ Zephyr board name like this:
 
 ## Use the Zephyr Terminal in CMSIS View
 
+![ZephyrTerminal](video/ZephyrTerminal.png)
+
 Keil Studio includes a built-in **Zephyr Terminal** that runs `west` commands directly inside the IDE. When the terminal opens, it automatically sets the example build folder as the working directory and configures the Zephyr environment.
 
 Example `west` commands:
diff --git a/vcpkg-configuration.json b/vcpkg-configuration.json
@@ -11,6 +11,6 @@
         "arm:tools/kitware/cmake": "^3.31.5",
         "arm:tools/ninja-build/ninja": "^1.12.1",
         "arm:compilers/arm/arm-none-eabi-gcc": "^14.3.1",
-        "arm:tools/open-cmsis-pack/cmsis-toolbox": "2.12.0"
+        "arm:tools/open-cmsis-pack/cmsis-toolbox": "^2.13.0"
     }
 }
diff --git a/video/ZephyrTerminal.png b/video/ZephyrTerminal.png
diff --git a/zephyr.cbuild-pack.yml b/zephyr.cbuild-pack.yml
@@ -1,20 +1,26 @@
 cbuild-pack:
   resolved-packs:
+    - resolved-pack: Infineon::CAT1C_DFP@1.2.0
+      selected-by-pack:
+        - Infineon::CAT1C_DFP
+    - resolved-pack: Infineon::KIT_T2G-B-H_LITE_BSP@1.2.1
+      selected-by-pack:
+        - Infineon::KIT_T2G-B-H_LITE_BSP
     - resolved-pack: Keil::B-L475E-IOT01A_BSP@2.1.0
       selected-by-pack:
         - Keil::B-L475E-IOT01A_BSP
-    - resolved-pack: Keil::B-U585I-IOT02A_BSP@2.0.0
+    - resolved-pack: Keil::B-U585I-IOT02A_BSP@3.0.0
       selected-by-pack:
         - Keil::B-U585I-IOT02A_BSP
+    - resolved-pack: Keil::STM32H7B3I-DK_BSP@2.1.1
+      selected-by-pack:
+        - Keil::STM32H7B3I-DK_BSP
+    - resolved-pack: Keil::STM32H7xx_DFP@4.1.3
+      selected-by-pack:
+        - Keil::STM32H7xx_DFP
     - resolved-pack: Keil::STM32L4xx_DFP@3.1.0
       selected-by-pack:
         - Keil::STM32L4xx_DFP
-    - resolved-pack: Keil::STM32U5xx_DFP@3.0.0
+    - resolved-pack: Keil::STM32U5xx_DFP@3.2.0
       selected-by-pack:
         - Keil::STM32U5xx_DFP
-    - resolved-pack: NXP::FRDM-MCXN947_BSP@19.0.0
-      selected-by-pack:
-        - NXP::FRDM-MCXN947_BSP@19.0.0
-    - resolved-pack: NXP::MCXN947_DFP@19.0.0
-      selected-by-pack:
-        - NXP::MCXN947_DFP@19.0.0
diff --git a/zephyr.csolution.yml b/zephyr.csolution.yml
@@ -7,8 +7,8 @@ solution:
     - pack: Keil::B-L475E-IOT01A_BSP
     - pack: Keil::STM32U5xx_DFP
     - pack: Keil::B-U585I-IOT02A_BSP
-    - pack: NXP::MCXN947_DFP@19.0.0
-    - pack: NXP::FRDM-MCXN947_BSP@19.0.0
+    - pack: Keil::STM32H7xx_DFP
+    - pack: Keil::STM32H7B3I-DK_BSP
     - pack: Infineon::CAT1C_DFP
     - pack: Infineon::KIT_T2G-B-H_LITE_BSP
 
@@ -18,14 +18,13 @@ solution:
       board: STMicroelectronics::B-L475E-IOT01A
       device: STMicroelectronics::STM32L475VGTx
       variables:
-        - west-board: disco_l475_iot1
+        - west-board: disco_l475_iot1/stm32l475xx
       target-set:
         - set:
           images:
             - project-context: blinky.Debug
           debugger:
             name: ST-Link@pyOCD
-            port: 3333
             protocol: swd
             clock: 4000000
     - type: B-U585I-IOT02A
@@ -35,17 +34,27 @@ solution:
         - set:
           images:
             - project-context: threads.Debug
-
-    - type: FRDM-MCXN947
-      board: NXP::FRDM-MCXN947
-      device: NXP::MCXN947VDF:cm33_core0
+    - type: STM32H7B3I-DK
+      board: STMicroelectronics::STM32H7B3I-DK
+      device: STMicroelectronics::STM32H7B3LIHxQ
       variables:
-        - west-board: frdm_mcxn947/mcxn947/cpu0
+        - west-board: stm32h7b3i_dk/stm32h7b3xx
       target-set:
         - set:
+          debugger:
+            name: ST-Link@pyOCD
+            clock: 10000000
+            protocol: swd
+            rtt:
+              - channel:
+                  - number: 0
+                    mode: stdio
+                  - number: 1
+                    mode: systemview
+            telnet:
+              - mode: console
           images:
             - project-context: blinky.Debug
-
     - type: IFX_T2G_B_H
       board: KIT_T2G-B-H_LITE
       device: CYT4BF8CDS:Cortex-M0p
@@ -64,6 +73,13 @@ solution:
         - CONFIG_DEBUG_THREAD_INFO: y
         - CONFIG_THREAD_STACK_INFO: n
         - CONFIG_DEBUG_OPTIMIZATIONS: y
+      # uncomment the following lines to enable RTT console and SystemView tracing
+      #  - CONFIG_USE_SEGGER_RTT: y
+      #  - CONFIG_RTT_CONSOLE: y
+      #  - CONFIG_UART_CONSOLE: n
+      #  - CONFIG_TRACING: y
+      #  - CONFIG_SEGGER_SYSTEMVIEW: y
+      #  - CONFIG_SEGGER_SYSVIEW_RTT_CHANNEL: 1
     - type: Release
       west-defs:
         - CONFIG_SIZE_OPTIMIZATIONS: y

Original file line number	Diff line number	Diff line change
`@@ -11,6 +11,6 @@`
`11`	`11`	`"arm:tools/kitware/cmake": "^3.31.5",`
`12`	`12`	`"arm:tools/ninja-build/ninja": "^1.12.1",`
`13`	`13`	`"arm:compilers/arm/arm-none-eabi-gcc": "^14.3.1",`
`14`		`- "arm:tools/open-cmsis-pack/cmsis-toolbox": "2.12.0"`
	`14`	`+ "arm:tools/open-cmsis-pack/cmsis-toolbox": "^2.13.0"`
`15`	`15`	`}`
`16`	`16`	`}`