CMSIS-Pack Development Tools and Libraries

This repository contains the source code of the CMSIS-Toolbox. This toolbox provides command line tools for processing software packs that are provided in Open-CMSIS-Pack format.

This repository provides the C++ source code of most CMSIS-Toolbox components and contains build and test configurations for Windows, Linux and macOS host platforms.

Open-CMSIS-Pack defines a delivery mechanism for software components, device parameters, and evaluation board support. The XML-based package description (*.PDSC) file contains the meta information of a software pack which is a collection of files including:

• Source code, header files, and software libraries
• Documentation and source code templates
• Device parameters along with startup code and programming algorithms
• Example projects

The complete file collection along with the *.PDSC file is called software pack and distributed as a zip archive using the file extension *.pack.

The goal of this project is to provide a consistent and compliant set of command-line tools for software packs that covers the complete lifecycle including:

• creation and maintenance of software packs.
• distribution and installation of software packs.
• project build with interfaces to various compilation tools.
• interfaces for flash programming and debugging tools.

Repository toplevel structure

    📦
    ┣ 📂cmake       local cmake functions and configuration files
    ┣ 📂docs        documentation shared by all components
    ┣ 📂external    3rd party components loaded as submodules
    ┣ 📂libs        reusable C++ library component source code shared by tools
    ┣ 📂scripts     scripts used by validation, build and test actions
    ┣ 📂test        test related files shared across tool and library components
    ┗ 📂tools       command line tool source code

Building the tools locally

This section contains steps to generate native makefiles and workspaces that can be used in the compiler environment of your choice.

The instructions contain a complete guide to get you the project build on your local machine for development and testing purposes.

Prerequisites

The following applications are required to be installed on your machine to allow components in this repository to be built and run.

Note that some of the required tools are platform dependent:

• Git
• GNU Arm Embedded Toolchain (version 10-2020-q4-major)
• A toolchain for your platform

  • Windows:

    • GIT Bash
    • Visual Studio 2019 with "Desktop development with C++"
    • CMake (minimum recommended version 3.18)
    • optional make or Ninja

    ☑️ Make sure 'git' and 'bash' paths are listed under the PATH environment
        variable and set the git bash priority higher in the path.
    
    ☑️ GCC/Clang on Windows:
        Currently GCC and Clang (MSYS2/MinGW distribution) compilers do not work
        on Windows. The included libc++ has a known issue in std::filesystem,
        see [MSYS2 GitHub issue #1937](https://github.com/msys2/MSYS2-packages/issues/1937).

  • Linux:

    • GNU Bash (minimum recommended version 4.3)
    • GNU Compiler (minimum recommended version 8.1)
    • alternatively LLVM/Clang Compiler (minimum recommended version 8)
    • CMake (minimum recommended version 3.18)
    • make or Ninja

  • MacOS:

    • GNU Bash (minimum recommended version 4.3)
    • XCode/AppleClang (minimum recommended version 11)
    • CMake (minimum recommended version 3.18)

    ☑️ For Apple Silicon (M1/M2 series):
        Currently the pre-installed bsdtar and apple gzip in macOS may cause some unexpected issues in CbuildIntegTests, like:
          curl: (23) Failure writing output to destination
          tar: Option --wildcards is not supported
        So please use gnu-tar and gzip:
          brew install gnu-tar
          brew install gzip
        And make sure they are added in $PATH.

Clone repository

Clone github repository to create a local copy on your computer to make it easier to develop and test. Cloning of repository can be done by following the below git command:

git clone [email protected]:Open-CMSIS-Pack/devtools.git

Build components

This is a three step process:

1. Download third party software components specified as git submodules.
2. Generate configuration files for a build system
3. Run build

Download third party software components

• Go to <path>/<to>/devtools and run git command:

  git submodule update --init --recursive

• Create and switch to the build directory

  mkdir build
  cd build

Generate configuration files

As usual, the actual build steps vary by platform.

• Linux/MacOS amd64:
  On Linux or MacOS use the following commands：

  Note: If DCMAKE_BUILD_TYPE is not selected, the binaries shall build with Release configuration:

  cmake -DCMAKE_BUILD_TYPE=<Debug/Release> ..

  for e.g.

  cmake -DCMAKE_BUILD_TYPE=Debug ..

• Linux cross-compiling aarch64:
  For cross-compiling aarch64 you need to generate with -DCMAKE_TOOLCHAIN_FILE=../cmake/TC-linux-aarch64.cmake:

  cmake -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_TOOLCHAIN_FILE=../cmake/TC-linux-aarch64.cmake ..

• Windows:
  On Windows system use the following command to generate the complete workspace:

  cmake -A x64 ..

Run build

One can trigger a build for all CMake targets or specific targets from the command line.

☑️ Note:
    The flag `--config` is optional. If it is not specified in the command, depending on
    the platform the binaries shall build in default configurations.
        - Windows: Debug
        - Linux/macOS: Release

Follow the respective commands:

• Build all CMake targets

  cmake --build . --config <Debug/Release>

  for e.g.

  cmake --build . --config Debug

• Users can build specific target of their choice:

  • Get the list of valid CMake generated targets

    cat ./targets

  • Select the target

  • Build the selected target and run command

    cmake --build . --config <Debug/Release> --target <target_name>

    for e.g.

    cmake --build . --config Debug --target CbuildUnitTests

Run Tests

Test Prerequisites

• Ensure that the above applicable prerequistes are fulfilled.

• Test environment setup:
  In order to run the tests, the test environment should know about

  • Path to CMSIS-Pack Root Directory
  • Installation path of toolchains (AC6, GCC)
  • Path to GNU Arm Embedded compiler binary

  Users can configure the test environment by setting the environment variables mentioned below.
  Note: When the variables are already set, User doesn't need to set them again.

  • CMSIS_PACK_ROOT:

    • Follow the details here.
    • When it is pointing to an empty directory. The test scripts shall make this directory ready to be
      used, by initializing (creating subfolder .Download, .Local, .Web and placing a copy of the index
      file under .Web/index) this directory as a pack root directory and automatically downloading all the
      packs required by test projects using cpackget tool.

  • GCC_TOOLCHAIN_ROOT:
    This variable should point to the installation path of GNU Arm Embedded Toolchain.

    • When the variable is not set. Tests shall try to find the toolchain under default path.

      Platform	Default path
      Linux	${HOME}/gcc-arm-11.2-2022.02-x86_64-arm-none-eabi/bin
      Windows	${PROGRAMFILES} (x86)/Arm GNU Toolchain arm-none-eabi/11.2 2022.02/bin
      MacOS	${HOME}/gcc-arm-11.2-2022.02-x86_64-arm-none-eabi/bin
      WSL_Windows	${PROGRAMFILES} (x86)/Arm GNU Toolchain arm-none-eabi/11.2 2022.02/bin

  • AC6_TOOLCHAIN_ROOT:
    This variable should point to the installation path of Arm Compiler 6.

    • When the variable is not set. Tests shall try to find the toolchain under default path.

      Platform	Default path
      Linux	${HOME}/ArmCompilerforEmbedded6.18/bin
      Windows	${PROGRAMFILES}/ArmCompilerforEmbedded6.18/bin
      MacOS	${HOME}/ArmCompilerforEmbedded6.18/bin
      WSL_Windows	${PROGRAMFILES}/ArmCompilerforEmbedded6.18/bin

  • CC:
    This variable should point to the full qualified path to GNU Arm Embedded compiler binary (arm-noneabi-gcc)

    • If the variable is not set packgen tests shall fail.

Set the environment variables

  for e.g.
    $export CMSIS_PACK_ROOT=/path/to/Pack/Root
    $export GCC_TOOLCHAIN_ROOT=/path/to/GCC/toolchain
    $export AC6_TOOLCHAIN_ROOT=/path/to/AC6/toolchain
    $export CC=/path/to/arm-noneabi-gcc

One can directly run the tests from command line.

• Using ctest:
  Use the command below to trigger the tests.

  • ctest -C <config> : Run all registered tests (Note: Running all the tests can take a while)
  • ctest -R <regex> -C <config>: Run all tests matching the regex

  for e.g.

  ctest -C Debug
      or
  ctest -R CbuildUnitTests -C Debug

• Using test executable:

  • Go to root build directory

    cd <root>

  • Run the executable

    ./<path_to_executable>/<executable_name>

    for e.g.

    cd build
    ./tools/buildmgr/test/integrationtests/windows64/Debug/CbuildIntegTests.exe

Note

• On running the tests, all required packs shall get downloaded automatically by test scripts
  under configured pack repository.

• By default, few special tests are skipped from execution as they are dependent on specific
  environment configuration or other dependencies.

  1. CI dependent tests :
     These tests are designed to work only in CI (Continuous Integration) environment
     • InstallerTests
     • DebPkgTests
  2. AC6 toolchain test :
     The below listed tests depend on a valid AC6 toolchain installed and can be run in
     the local environment on the installation of valid Arm Compiler 6.
     • CBuildAC6Tests
     • MultiTargetAC6Tests

  Make sure you have the proper Arm Compilers licenses.

Code coverage

Users can generate coverage reports locally using a GNU tool lcov.

Prerequisite

Coverage reports can only be generated on linux platform.

• Ensure that the linux prerequisite are fulfilled.

• Install lcov

  sudo apt-get install lcov

Generate coverage report

• Create and switch to build directory

  mkdir build
  cd build

  ☑️ Ensure that the build tree is clean and doesn't have any existing coverage data i.e. .gcda or .gcno files

• Generate configuration files with coverage flag ON

  cmake -DCMAKE_BUILD_TYPE=Debug -DCOVERAGE=ON ..

• Build target tests

  cmake --build . --config Debug --target <target_name>

  for e.g.

  cmake --build . --config Debug --target CbuildUnitTests

• Run tests

  ctest -R <regex> -C Debug

  for e.g.

  ctest -R CbuildUnitTests -C Debug

• Collect coverage data

  lcov -c --directory <path_to_user_space> --output-file <cov_out_file>

  for e.g.

  lcov -c --directory ./tools/buildmgr --output-file full_coverage.info

• Extract coverage data from file

  ☑️ By default, lcov collects coverage data also from the currently running Linux
      kernel. Specify -e option to extract data from files matching PATTERN from file

  lcov -e <input_file> '<PATTERN>' -o <out_file>

  for e.g.

  lcov -e full_coverage.info '/tools/buildmgr/cbuild/*' '*/tools/buildmgr/cbuildgen/*' '*/tools/buildmgr/cbuild/*' -o coverage.info

• Generate html coverage report

  genhtml <cov_file> --output-directory <report_out_dir>

  for e.g.

  genhtml coverage.info --output-directory coverage

The coverage report i.e. index.html is generated into the specified directory.

Build Documentation

Some components provide Doxygen-based documentation which needs to be generated before it can be viewed and published. There are specific build targets for these generated documentations, see build target suffix -docs.

☑️ Note:
   The *-docs build targets require doxygen to be available. If CMake fails to
   detect the correct version of doxygen a warning message appears and the build
   targets are skipped.

To build the documentation for a specific component run the following in the CMake build directory:

cmake --build . --target buildmgr-docs

The documentation is generated into the CMake binary directory of the enclosing component.

License

Open-CMSIS-Pack is licensed under Apache 2.0.

Contributions and Pull Requests

Contributions are accepted under Apache 2.0. Only submit contributions where you have authored all of the code.

Proposals, Reviews and Project

Please feel free to raise an issue on GitHub to start the discussion about your proposal.

We are in the early days and discuss proposals which we are dividing into 5 work streams with a dedicated label:

• Core Library Components - common libraries that are re-used across a range of tools. The PoC Tools are the first consumers, but the library components can also be used to create commercial derivatives or in-house tooling.
• Overall Project Concept - procedures to generate packs and application software. We shall consider complex applications such as multi-core processor systems or secure/non-secure partitions.
• PoC Tools - command line tools and utilities that implement the overall concepts and are intended to be used for open-source projects or even integrated into commercial software tools.
• Process Improvements - documentation and tools that help the software community to streamline and secure the software delivery to the user base.
• Resource Management - describes the data models used to manage and organized software packs and application projects.

These Issues are tracked inside the project board

Issues, Labels

Please feel free to raise an issue on GitHub to report misbehavior (i.e. bugs)

Issues are your best way to interact directly with the maintenance team and the community. We encourage you to append implementation suggestions as this helps to decrease the workload of the very limited maintenance team.

We shall be monitoring and responding to issues as best we can. Please attempt to avoid filing duplicates of open or closed items when possible. In the spirit of openness we shall be tagging issues with the following:

• bug – We consider this issue to be a bug that shall be investigated.
• wontfix - We appreciate this issue but decided not to change the current behavior.
• out-of-scope - We consider this issue loosely related to CMSIS. It might be implemented outside of CMSIS. Let us know about your work.
• question – We have further questions about this issue. Please review and provide feedback.
• documentation - This issue is a documentation flaw that shall be improved in the future.
• DONE - We consider this issue as resolved - please review and close it. In case of no further activity, these issues shall be closed after a week.
• duplicate - This issue is already addressed elsewhere, see a comment with provided references.