CMSIS-Toolbox

This contains the executable tools of the CMSIS-Toolbox that provides a set of command-line tools to work with software packs in Open-CMSIS-Pack format.

Users Guide

The Users Guide provides detailed information.

Project Creation

The following tools support the creation of build information for embedded applications:

Tool	Description
cpackget	Pack Manager: install and manage software packs in the development environment.
cbuild	Build Invocation: orchestrate the build steps utilizing CMSIS tools and a CMake compilation process.
csolution	Project Manager: create build information for embedded applications that consist of one or more related projects.

Example Projects

Repository	Description
csolution-examples	Contains several Hello World examples that show single-core, multi-core, and TrustZone setup.
vscode-get-started	Contains the setup for a VS Code development environment including an example project.
github.com/Arm-Examples	Contains many examples that include CMSIS-Toolbox setup.

Software Pack Creation

The following tools support the creation of Software Packs in CMSIS-Pack format:

Tool	Description
packchk	Pack Validation: installs and manages software packs in the local development environment.
svdconv	SVD Check / Convert: validate and/or convert System View Description (SVD) files.

In addition several scripts are provided that simplify pack creation with desktop or cloud workflows. This is described in several hands-on tutorials:

Hands-on Tutorial	Description
SW-Pack-HandsOn	Explains the steps to create a simple software pack using the Open-CMSIS-Pack technology.
DFP-Pack-HandsOn	Explains the structure and creation of a Device Family Pack (DFP).
BSP-Pack-HandsOn	Explains the structure and creation of a Board Support Pack (BSP).

Report a Bug

Please report any issue you are facing while using CMSIS-Toolbox in the Issues tab on GitHub. Select the appropriate issue template, depending on the severity of the issue. Bugs (or deviations) from the defined behaviour that can be worked around shall be reported as "non-blocking bug". In turn, issues that prevent you from using a certain feature entirely, are considered a "blocking bug" and labelled as critical.