Components

Models and Frontends

The types of models which can be processed with MLonMCU are given by the implemented frontends. The Following Table shows the currently supported ones:

Frontend	Formats
TFLite	`.tflite`

Here is also a list of frontends with will probably implemented in the furture:

ONNX (onnx)
TensorFlow SavedModel (.pb)

While you can use your own models we also provide support for the following model zoos which can be cloned from GitHub:

Model Collection by EDA@TUM (tum-ei-eda/mlonmcu-models)
ARM Model Zoo (ARM-software/ML-zoo) ⚠️ Work in Progress ⚠️

Frameworks and Backends

For each framework supported by MLonMCU, a number of backends is implemented.

Framework	Backends
TenflowFlow Lite for Microcontrollers (`tflm`)	Default Interpreter (`tflmi`) Offline Compiler (`tflmc`) ⚠️ Work in Progress ⚠️
TVM (`tvm`)	AoT Executor (`tvmaot`) Graph Executor (`tvmrt`) Custom Codegenerator (`tvmcg`)

Platforms and Targets

While support for some targets (especially simulator based ones) is directly build into MLonMCU, a platform is used for more complivcated targets (e.g. real hardware) to reuse existing Flows for compiling and flashing

Platform	Targets
Default	RISC-V: ETISS/Pulpino (`etiss_pulpino`) Spike (`spike`) VPSimPlus (`ovpsim`) ARM: Corstone300 FVP (`corstone300`) x86: Host `host_x86`)
ESP IDF (`espidf`)	LX6: ESP32 (`esp32`) RISC-V: ESP32-C3 (`esp32c3`)

To extend the support of read hardware targets, it would be great if this list would be extended by some of the following platforms in the furture:

Arduino Excosystem
PlatformIO
ZephyrOS

Features

An extensive overview of the available features in TVM is given in the following table. The types of those features are denoted with a check mark in the respective column.

Feature	Setup	Frontend	Framework	Backend	Target	Platform/Compile
Debug Arena Usage (`debug_arena`)						✅
Validate Output Data (`validate`)		✅				✅
muRISCV-NN (`muriscvnn`)	✅		✅
CMSIS-NN (`cmsisnn`)	✅		✅
CMSIS-NN + TVM BYOC (`cmsisnnbyoc`)				✅
Fused TIling for TVM (`fusetile`)				✅
Custom TVM meory planner (`memplan`)				✅
Unified Static Memory Planner for TVM (`usmp`)				✅
V-Extension for RISC-V (`vext`)	✅				✅ (`spike`, `ovpsim`)
Debug Build (`debug`)	✅					✅
GDBServer (`gdbserver`)					✅
Debug ETISS VP (`etissdbg`)					✅ (`etiss_pulpino`)
Create Memory Trace (`trace`)					✅ (`etiss_pulpino`)
Unpacked API (`unpacked_api`)				✅ (`tvmaot`)
Autotune TVM Model (`autotune`)				✅
Use TVM Tuning Records (`autotuned`)				✅

Managed Dependencies

MLonMCU tries to either manage dependencies internally (hidden to the user) or rely on 3rd party platforms to install them.

The following list gives and overview of the set of dependencies which are currently managed:

Toolchains - RISC-V GCC Linux Toolchain - Download and extract - ARM GCC Linux Toolchain - Download and extract - LLVM - Download and extract
Targets/Simulators - ETISS - Clone Repository - Build ETISS - Install ETISS - Build bare_etiss_processor - Spike - Clone Repositories - Build Proxy Kernel - Build Simulator - Corstone-300 - Download and extract - Install FVP
Frameworks/Backends - TFLM - Clone Repository - Download 3rd party dependencies - TFLite Micro Compiler - Clone Repository - Build - TVM - Clone Repository (including 3rd party dependencies) - Configure & Build - uTVM Staticrt Codegen - Clone Repository - Build
Features - muRISCV-NN - Clone Repository - Build - CMSIS(-NN) - Clone Repository - Build

The following dependencies are intentionally NOT managed by MLonMCU:

OVPSimPlus: The simulator is closed source and needs an individual license for usage (free)
ESP-IDF: Make sure you provide a espidf.path with the required components installed

Components in Detail

Components: