Documentation: CMSIS-Build replaced by CMSIS-Toolbox
diff --git a/CMSIS/DoxyGen/Build/Build.dxy b/CMSIS/DoxyGen/Build/Build.dxy
index 4d6797d..5242305 100644
--- a/CMSIS/DoxyGen/Build/Build.dxy
+++ b/CMSIS/DoxyGen/Build/Build.dxy
@@ -755,8 +755,7 @@
# Note: If this tag is empty the current directory is searched.
INPUT = . \
- src/General.txt \
- src/CmdLineBuild.txt \
+ src/General.md \
src/cprj_schema.txt
# This tag can be used to specify the character encoding of the source files
diff --git a/CMSIS/DoxyGen/Build/src/General.md b/CMSIS/DoxyGen/Build/src/General.md
new file mode 100644
index 0000000..90c915a
--- /dev/null
+++ b/CMSIS/DoxyGen/Build/src/General.md
@@ -0,0 +1,39 @@
+\mainpage Overview
+
+CMSIS-Build is now replaced with the [**CMSIS-Toolbox**](https://github.com/Open-CMSIS-Pack/devtools/tree/main/tools) that is a set of tools for creating and building projects that are based on software packs. It also contains tools that help to create software packs.
+
+## Components of CMSIS-Toolbox
+The [**CMSIS-Toolbox**](https://github.com/Open-CMSIS-Pack/devtools/tree/main/tools) is developed under the [Linaro Open-CMSIS-Pack](https://www.open-cmsis-pack.org/) project and contains these tools:
+
+- **cpackget** download, add and remove software packs.
+- **csolution** to create and manage complex applications with user source files and content from software packs
+- **cbuild** controls the build process that translates a project to a executable binary image.
+- **packgen** to create a software pack from a CMake based software repository.
+- **packchk** to validate a software pack
+
+The [**CMSIS-Toolbox**](https://github.com/Open-CMSIS-Pack/devtools/tree/main/tools) can be used as stand-alone tools with command line interface (CLI) but will be integrated into several other Arm toolkits such as:
+
+- [**Arm Virtual Hardware**](https://www.arm.com/virtual-hardware) to manage the build process in CI workflows.
+- [**Keil Studio**](https://www.keil.arm.com) as integral part of the project management.
+- [**Keil MDK**](https://www.keil.com/mdk5/) to provide CLI tools for project generation.
+
+## Development Workflow
+
+The following diagram shows the development workflow using the CMSIS-Toolbox.
+
+
+
+A solution that manages several related projects and projects can be composed using an intuitive `*.yml` format. This solution and project files are then translated using **csolution** CLI tool to the `*.CPRJ` project file format.
+
+The individual `*.CPRJ` project files can be imported to an IDE or by using **cbuild** translated into executable binary images.
+
+The \ref cprjFormat_pg describes the `*.CPRJ` project file format that is used by **cbuild**.
+
+## Revision History
+
+Version | Description
+:-------------|:---------------------------------
+replaced by | [**CMSIS-Toolbox**](https://github.com/Open-CMSIS-Pack/devtools/tree/main/tools) now contains the **cbuild** (aka CMSIS-Build) CLI tool.
+0.10.0 (beta) | CMake back-end and support for more Cortex-M processors including ArmV8.1M architecture.
+0.9.0 (beta) | Support for multiple compilers and commands for layer management
+0.1.0 (alpha) | Release for alpha review
diff --git a/CMSIS/DoxyGen/Build/src/General.txt b/CMSIS/DoxyGen/Build/src/General.txt
deleted file mode 100644
index 63b820e..0000000
--- a/CMSIS/DoxyGen/Build/src/General.txt
+++ /dev/null
@@ -1,87 +0,0 @@
-/*=======0=========1=========2=========3=========4=========5=========6=========7=========8=========9=========0=========1====*/
-/**
-\mainpage Overview
-
-<b>CMSIS-Build</b> is a set of tools, software frameworks, and work flows that improve productivity:
-
- - \ref cprjFormat_pg "CPRJ" is a generic CMSIS-aware project file format that allows IDEs and command-line build tools to
- share the same projects.
- - A \ref CmdLineBuild "Continuous Integration (CI) work flow" for projects that are based on software components supplied
- in CMSIS-Pack format.
- - Software Layers enable code reuse across different targets. A software layer is a pre-configured software component
- selection and user source code.
- - <a href="../../Driver/html/group__vio__interface__gr.html"><b>CMSIS-Driver VIO</b></a> is a set of generic input/output
- functions for example and test code. It allows to fast migration from evaluation boards to production hardware.
-
-The figure below shows how the <b>CMSIS-Build</b> components may be used to create a IoT cloud application:
- - The <b>Board I/O</b> layer contains the drivers and device configuration for a specific evaluation board.
- - The <b>Cloud</b> layer implements the software components that are required to connect to a Cloud Service Provider (CSP).
- - The <b>Application Code</b> may start with a reference example and is expanded to application specific requirements that
- access specialized peripherals.
-
-\image html "Layer.png" "Software Layers and Virtual I/O"
-
-Software layers and Virtual I/O simplify these use cases:
-
-<b>Port software from evaluation board to custom hardware:</b><br>
-- Frequently, the software development starts on an evaluation board, for example because production hardware is not yet
- available. The <a href="../../Driver/html/group__vio__interface__gr.html"><b>VIO component</b></a> allows you to use the
- I/O capabilities of an evaluation kit and disconnect it when moving to production hardware. In case the production
- hardware uses a different device configuration or different I/O drivers, the <b>Board I/O</b> layer may be swapped.
-
-<b>Deliver reference examples for many different evaluation boards:</b><br>
-- Reference examples are a great way to demonstrate a software solution. It is however expensive to support many different
- evaluation boards. The VIO and CMSIS-Driver components give reference examples for a consistent interface to target
- hardware. When such a consistent set of components is available as a <b>Board I/O</b> layer for many different evaluation
- boards, it allows to run a <b>Cloud</b> layer together with a reference example. The tools for \ref CmdLineBuild allow to
- combine various different layers and allow in this way to generate several different reference examples on a range of
- evaluation boards.
-
-\section CB_Components Components of CMSIS-Build
-
-<b>Specification</b> of a generic project file format:
- - \ref cprjFormat_pg describes all XML elements that are available for the project description and how to use them.
-
-<b>Tools</b> that support \ref CmdLineBuild with software packs and the generic project file format:
- - \ref cbuildgen generates a standard CMakeLists.txt file and allows to manage software layers.
-*/
-
-
-/*=======0=========1=========2=========3=========4=========5=========6=========7=========8=========9=========0=========1====*/
-/**
-\page build_revisionHistory Revision history
-
-<table class="cmtable" summary="Revision History">
- <tr>
- <th>Version</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>0.10.0 (beta)</td>
- <td>Release for beta review:
- - new command line options: --update, --quiet, --log, --intdir, --outdir (see usage for more information).
- - building an executable always creates binaries in ELF, HEX and BIN format in output directory.
- - added build progress information to build output.
- - added makefile target 'rebuild' (clean + build).
- - added makefile self-dependency. Generated makefile is only written if the content changed.
- - added makefile target 'database' for generating a compilation database file.
- - added special handling for layer files (layer.\<layer name>.\<ext>) copied unconditionally along with the layer on extract, remove, compose and add commands of cbuildgen.
- - added special handling for layer markdown files (layer.\<layer name>.md) being concatenated into README.md on compose command of cbuildgen.
- - fixed: #970 Toolchain configuration files corrected to handle Cortex-M0+, Cortex-M35P, SC000, SC300 and ARMV81MML based devices.
- - fixed: #971 Unnecessary rebuild of libraries when using GCC toolchain.
- </td>
- </tr>
- <tr>
- <td>0.9.0 (beta)</td>
- <td>Release for beta review:
- - added layer description to project format specification.
- - added support for multiple compilers.
- - added commands for layer operations to cbuildgen.
- </td>
- </tr>
- <tr>
- <td>0.1.0</td>
- <td>Release for alpha review</td>
- </tr>
-</table>
-*/
diff --git a/CMSIS/DoxyGen/Build/src/cprj_schema.txt b/CMSIS/DoxyGen/Build/src/cprj_schema.txt
index 56d14e8..772201b 100644
--- a/CMSIS/DoxyGen/Build/src/cprj_schema.txt
+++ b/CMSIS/DoxyGen/Build/src/cprj_schema.txt
@@ -1,14 +1,14 @@
/*=======0=========1=========2=========3=========4=========5=========6=========7=========8=========9=========0=========1====*/
/**
-\page cprjFormat_pg Project Description (*.cprj) Format
+\page cprjFormat_pg *.CPRJ Project Format
\section section_overview Overview
-The CMSIS Project description format is unifying the specification for the build of a software project.
+The *.CPRJ project description format is unifying the specification for the build of a software project.
It is a public format to exchange project build information between tools that support the CMSIS-Pack based
Run-Time Environment. In addition the format facilitates the tool driven construction of projects from partial projects,
named project 'layers'. The project description is targeted to generate a single executable or library file.
-The specification of this CMSIS Project description format (*.cprj) is replacing the previous format (*.cpdsc).
+The specification of the *.CPRJ project format replaces the previous format (*.cpdsc).
The most significant differences are:
- a new format specification which is independent from the CMSIS-Pack schema.
- the scope of the description is limited to building a single application or library (no debugger setup).
@@ -43,8 +43,7 @@
See \subpage element_cprj "Project Description Root" for details about the description format..
-See \ref CmdLineBuild "CMSIS-Build" for further information how to build software based on the CMSIS Project description at
-the command line and how to create and manage projects using layers.
+See the <b>cbuild</b> documentation for further information how to build software based on the *.CPRJ project format.
See \subpage projectDescriptionSchema "Project Description Schema file" for validation of project files.
diff --git a/CMSIS/DoxyGen/Build/src/images/CMSIS-Toolbox.png b/CMSIS/DoxyGen/Build/src/images/CMSIS-Toolbox.png
new file mode 100644
index 0000000..adba9f9
--- /dev/null
+++ b/CMSIS/DoxyGen/Build/src/images/CMSIS-Toolbox.png
Binary files differ
