Arm® ML embedded evaluation kit

Table of Contents


  • Arm® and Cortex® are registered trademarks of Arm® Limited (or its subsidiaries) in the US and/or elsewhere.
  • Arm® and Ethos™ are registered trademarks or trademarks of Arm® Limited (or its subsidiaries) in the US and/or elsewhere.
  • Arm® and Corstone™ are registered trademarks or trademarks of Arm® Limited (or its subsidiaries) in the US and/or elsewhere.
  • TensorFlow™, the TensorFlow logo and any related marks are trademarks of Google Inc.


Before starting the setup process, please make sure that you have:

Additional reading

This document contains information that is specific to Arm® Ethos™-U55 products. See the following documents for other relevant information:

See for access to Arm documentation.

Repository structure

The repository has the following structure:

├── dependencies
├── docs
├── scripts
   └── ...
├── source
   ├── application
    ├── hal
    ├── main
    └── tensorflow-lite-micro
   └── use_case
     └── <usecase_name>
│          ├── include
│          ├── src
│          └── usecase.cmake
├── tests
   └── ...
└── CMakeLists.txt


  • dependencies: contains all the third party dependencies for this project.

  • docs: contains the documentation for this ML applications.

  • scripts: contains build related and source generation scripts.

  • source: contains C/C++ sources for the platform and ML applications. Common code related to the Ethos-U55 NPU software framework resides in application sub-folder with the following structure:

    • application: contains all the sources that form the core of the application. The use case part of the sources depend on sources here.

      • hal: contains hardware abstraction layer sources providing a platform agnostic API to access hardware platform specific functions.

      • main: contains the main function and calls to platform initialization logic to set things up before launching the main loop. It also contains sources common to all use case implementations.

      • tensorflow-lite-micro: contains abstraction around TensorFlow Lite Micro API implementing common functions to initialize a neural network model, run an inference, and access inference results.

    • use_case: contains the ML use-case specific logic. Having this as a separate sub-folder isolates ML specific application logic with the assumption that the application will do all the required set up for logic here to run. It also makes it easier to add a new use case block.

    • tests: contains the x86 tests for the use case applications.

Hardware abstraction layer has the following structure:

├── hal.c
├── include
│   └── ...
└── platforms
    ├── bare-metal
    │   ├── bsp
    │   │   ├── bsp-core
    │   │   │   └── include
    │   │   ├── bsp-packs
    │   │   │   └── mps3
    │   │   ├── cmsis-device
    │   │   ├── include
    │   │   └── mem_layout
    │   ├── data_acquisition
    │   ├── data_presentation
    │   │   ├── data_psn.c
    │   │   └── lcd
    │   │       └── include
    │   ├── images
    │   ├── timer
    │   └── utils
    └── native
  • include and hal.c: contains the hardware abstraction layer (HAL) top level platform API and data acquisition, data presentation and timer interfaces.

    Note: the files here and lower in the hierarchy have been written in C and this layer is a clean C/C++ boundary in the sources.

  • platforms/bare-metal/data_acquisition
    platforms/bare-metal/utils: contains bare metal HAL support layer and platform initialisation helpers. Function calls are routed to platform specific logic at this level. For example, for data presentation, an lcd module has been used. This wraps the LCD driver calls for the actual hardware (for example MPS3).

  • platforms/bare-metal/bsp/bsp-packs: contains the core low-level drivers (written in C) for the platform reside. For supplied examples this happens to be an MPS3 board, but support could be added here for other platforms too. The functions defined in this space are wired to the higher level functions under HAL (as those in platforms/bare-metal/ level).

  • platforms/bare-metal/bsp/bsp-packs/mps3/include
    platforms/bare-metal/bsp/bsp-packs/mps3: contains the peripheral (LCD, UART and timer) drivers specific to MPS3 board.

  • platforms/bare-metal/bsp/bsp-core
    platforms/bare-metal/bsp/include: contains the BSP core sources common to all BSPs. These include a UART header (only the implementation of this is platform specific, but the API is common) and "re-targeting" of the standard output and error streams to the UART block.

  • platforms/bare-metal/bsp/cmsis-device: contains the CMSIS template implementation for the CPU and also device initialisation routines. It is also where the system interrupts are set up and handlers are overridden. The main entry point of a bare metal application will most likely reside in this space. This entry point is responsible for setting up before calling the user defined "main" function in the higher level application logic.

  • platforms/bare-metal/bsp/mem_layout: contains the platform specific linker scripts.

Models and resources

The models used in the use cases implemented in this project can be downloaded from Arm ML-Zoo.

When using Ethos-U55 NPU backend, the NN model is assumed to be optimized by Vela compiler. However, even if not, it will fall back on the CPU and execute, if supported by TensorFlow Lite Micro.

Vela compiler

The Vela compiler is a tool that can optimize a neural network model into a version that can run on an embedded system containing Ethos-U55 NPU.

The optimized model will contain custom operators for sub-graphs of the model that can be accelerated by Ethos-U55 NPU, the remaining layers that cannot be accelerated are left unchanged and will run on the CPU using optimized (CMSIS-NN) or reference kernels provided by the inference engine.

For detailed information see Optimize model with Vela compiler.


This section describes how to build the code sample applications from sources - illustrating the build options and the process.

The project can be built for MPS3 FPGA and FVP emulating MPS3. Default values for configuration parameters will build executable models with Ethos-U55 NPU support. See:


This section describes how to deploy the code sample applications on the Fixed Virtual Platform or the MPS3 board. See:

Running code samples applications

This section covers the process for getting started with pre-built binaries for the code samples. See Running applications.

Implementing custom ML application

This section describes how to implement a custom Machine Learning application running on a platform supported by the repository (Fixed Virtual Platform or an MPS3 board).

Cortex-M55 CPU and Ethos-U55 NPU Code Samples software project offers a simple way to incorporate additional use-case code into the existing infrastructure and provides a build system that automatically picks up added functionality and produces corresponding executable for each use-case.


Testing and benchmarking

See Testing and benchmarking.

Memory Considerations

See Memory considerations



Contribution guidelines

Contributions are only accepted under the following conditions:

  • The contribution have certified origin and give us your permission. To manage this process we use Developer Certificate of Origin (DCO) V1.1. To indicate that contributors agree to the the terms of the DCO, it's neccessary "sign off" the contribution by adding a line with name and e-mail address to every git commit message:

    Signed-off-by: John Doe <>

    This can be done automatically by adding the -s option to your git commit command. You must use your real name, no pseudonyms or anonymous contributions are accepted.

  • You give permission according to the Apache License 2.0.

    In each source file, include the following copyright notice:

    * Copyright (c) <years additions were made to project> <your name>, Arm Limited. All rights reserved.
    * SPDX-License-Identifier: Apache-2.0
    * Licensed under the Apache License, Version 2.0 (the "License");
    * you may not use this file except in compliance with the License.
    * You may obtain a copy of the License at
    * Unless required by applicable law or agreed to in writing, software
    * distributed under the License is distributed on an "AS IS" BASIS,
    * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    * See the License for the specific language governing permissions and
    * limitations under the License.

Coding standards and guidelines

This repository follows a set of guidelines, best practices, programming styles and conventions, see:

Code Reviews

Contributions must go through code review. Code reviews are performed through the Gerrit server. Contributors need to signup to this Gerrit server with their GitHub account credentials. In order to be merged a patch needs to:

  • get a "+1 Verified" from the pre-commit job.
  • get a "+2 Code-review" from a reviewer, it means the patch has the final approval.


Prior to submitting a patch for review please make sure that all build variants works and unit tests pass. Contributions go through testing at the continuous integration system. All builds, tests and checks must pass before a contribution gets merged to the master branch.


Please, if you want to start public discussion, raise any issues or questions related to this repository, use forum.


The ML Embedded applications samples are provided under the Apache 2.0 license, see License Apache 2.0.

Application input data sample files are provided under their original license:

Automatic Speech Recognition SamplesCreative Commons Attribution 4.0 International Public License
Image Classification SamplesCreative Commons Attribution 1.0
Keyword Spotting SamplesCreative Commons Attribution 4.0 International Public License
Keyword Spotting and Automatic Speech Recognition SamplesCreative Commons Attribution 4.0 International Public License