Merge Docu-2.12 in to main branch (#443)

## Changes
Documentation CMSIS-Toolbox update for version 2.12.0
## Checklist
<!-- Put an `x` in the boxes. All tasks must be completed and boxes
checked before merging. -->
- [x] 🤖 This change is covered by unit tests (if applicable).
- [x] 🤹 Manual testing has been performed (if necessary).
- [x] 🛡️ Security impacts have been considered (if relevant).
- [x] 📖 Documentation updates are complete (if required).
- [x] 🧠 Third-party dependencies and TPIP updated (if required).

---------

authored-by: Reinhard Keil <ReinhardKeil@users.noreply.github.com>

Author: brondani

docs/ReferenceApplications.md

@@ -572,7 +572,7 @@ Refer to [Header File Structure](#header-file-structure) for more information.
 
 #include "stm32u5xx_hal.h"
 #include "GPIO_STM32U5xx.h"
-#include "Driver_I2C.h"          // ToDo are these headers included in CMSIS_target_header?
+#include "Driver_I2C.h"
 #include "Driver_SPI.h"
 #include "Driver_USART.h"
 

docs/Troubleshooting.md

@@ -124,6 +124,9 @@ project:
 
 When a `type: hex` file is generated for AC6, the CMSIS-Toolbox configures this file in the `*.cbuild-run.yml` file with `load: image` and the `type: elf` file with `load: symbols`. This bypasses the GDB loader issue.
 
+!!! Note
+The HEX file should be generated using the Arm Compiler 6 `fromelf` tool during the build process of the application. Using a HEX conversation tool for a different toolchain may generate unpredictable results.
+
 ## Layer Search Fails
 
 The `cbuild setup` command does not find compatible layers.

docs/YML-CBuild-Format.md

@@ -52,7 +52,7 @@ A typical directory structure of a `csolution` based application that uses commo
  ┣  ┣ 📂 mypro2\Target\Debug
  ┣  ┣  ┣  mypro2.cbuild.Debug+Target.yml   # file references are relative to directory out\mypro2\Target\Debug
 
- ```
+```
 
 ## Lock Pack Versions
 
@@ -121,7 +121,7 @@ The `<solution-name>.cbuild-idx.yml` file is generated for the *csolution projec
 &nbsp;&nbsp;&nbsp; `csolution:`                               | Relative path and name of the [`*.csolution.yml`](YML-Input-Format.md#solution) input file used to generate this application.
 &nbsp;&nbsp;&nbsp; [`configurations:`](#configurations)       | For reference applications with undefined layers: list of potential project configurations for a reference application with undefined layers
 &nbsp;&nbsp;&nbsp; [`cprojects:`](#cprojects)                 | List of `*.cproject.yml` and `*.clayer.yml` input files used to generate this application.
-&nbsp;&nbsp;&nbsp; [`cbuilds:`](#cbuilds)                     | List of `*.cbuild.yml` output files that are generated for this application.
+&nbsp;&nbsp;&nbsp; [`cbuilds:`](#cbuilds)                     | List of `*.cbuild.yml` output files that are generated by `*.cproject.yml` files for this application.
 &nbsp;&nbsp;&nbsp; [`select-compiler:`](#select-compiler)     | For projects with unspecified compiler: list of available compilers for selection
 
 **Example:**
@@ -152,6 +152,11 @@ build-idx:
     - cbuild: out/MassStorage/B-U585I-IOT02A/Release/MassStorage.Release+B-U585I-IOT02A.cbuild.yml
       project: MassStorage
       configuration: .Release+B-U585I-IOT02A
+    - cbuild: out/hello_world/B-U585I-IOT02A/Release/hello_world.Release+B-U585I-IOT02A.cbuild.yml
+      west: true
+      project: hello_world
+      configuration: .Release+B-U585I-IOT02A
+
   errors: true                  # indicates error
   packs-missing:                # lists missing packs
     - pack: ARM::CMSIS-RTX      # with unspecified version
@@ -637,6 +642,30 @@ Each different license that is used in a project context has a separate section.
         :
 ```
 
+#### `west:`
+
+For each west build context a node `west:` is created in *.cbuild.yml
+
+`west:`                                                   |              | Content
+:---------------------------------------------------------|:-------------|:------------------------------------
+&nbsp;&nbsp;&nbsp; `app-path:`                            | **Required** | Path to the application source directory.
+&nbsp;&nbsp;&nbsp; `project-id:`                          | **Required** | Project identifier
+&nbsp;&nbsp;&nbsp; `board:`                               | **Required** | Board name used for west build invocation.
+&nbsp;&nbsp;&nbsp; `device:`                              |   Optional   | Specify the processor core for execution of the generated image (used in `*.cbuild-run.yml`).
+&nbsp;&nbsp;&nbsp; `west-defs:`                           |   Optional   | Defines in `CMake` format. The `west-defs:` from build and target-type are added.
+&nbsp;&nbsp;&nbsp; `west-opt:`                            |   Optional   | Options for the `west` tool (default: empty).
+
+**Example:**
+
+```yml
+  west:
+    project-id: hello_world
+    app-path: ../../../../hello_world
+    board: stm32h7b3i_dk 
+    west-defs:
+      - CONFIG_BUILD_OUTPUT_HEX=y
+```
+
 ## Generator Information Files
 
 The `csolution run` command generates the following build information files in the [`intdir:`](YML-Input-Format.md#output-dirs) of the related `context`. These files are the input to a generator and provide information about the *csolution project* to the generator.  The files are generated in the [`tmp` directory](build-overview.md#output-directory-structure) of the project and contain absolute paths.
@@ -710,7 +739,7 @@ The `*.cgen.yml` file lists the generated *csolution project* part and starts wi
 
 ## Run and Debug Management
 
-The CMSIS-Toolbox build system manages software packs that contain information about device, board, and software components. It controls the build output (typically ELF/DWARF files), and has provisions for HEX, BIN and post-processing. The [`target-set:`](build-overview.md#run-and-debug-configuration) node configures the application images and the debugger for a [target-type](build-overview.md#project-setup-for-related-projects).
+The CMSIS-Toolbox build system manages software packs that contain information about device, board, and software components. It controls the build output (typically ELF/DWARF files), and has provisions for HEX, BIN and post-processing. The [`target-set:`](build-overview.md#run-and-debug-configuration) node configures the application images and the debugger for a [target-type](build-overview.md#configure-related-projects).
 
 The software packs contain information that is the basis for debug and run settings:
 
@@ -810,8 +839,8 @@ The following describes the overall structure of the `*.cbuild-run.yml` file.  W
 
 #### `output:`
 
-This node contains information about the images that should be loaded. The images that are generated by the *csolution project* are typically configured [using a context set](build-overview.md#working-with-context-set).
-Use the [`images:`](YML-Input-Format.md#images) node in the `*.csolution.yml` file to add other output files.
+This node contains information about the images that should be loaded. The images that are generated by the *csolution project* are typically configured [using a target-set](build-overview.md#working-with-target-set). The `output:` node includes also image files that are generated with a [West Build](YML-Input-Format.md#west-build) specification.
+The `output:` node also contains other required files that are added with [`images:`](YML-Input-Format.md#images) in the `*.csolution.yml` file.
 
 `output:`                                                 |             | Content
 :---------------------------------------------------------|-------------|:------------------------------------