This repository contains source code of embARC Machine Learning Inference Library (embARC MLI Library), its documentation and examples. The primary purpose of this library is to enable developers to efficiently implement and/or port data processing algorithms based on machine learning principles for DSP-enhanced ARC Processors.
Version 2.0
This release supports following functional primitives
Supported data layout:
Supported data format:
Slicing support: creation of sub-tenors and support for non-contiguous tensor data.
Supported platforms:
Toolchains support:
embARC MLI library API documentation for version 2.0 is available online starting from the release date.
It's sources are available in the /doc directory and can be built as described in the related readme file.
./bin - directory for embARC MLI library binary archive created during build
./obj - directory for all intermediate artifacts created during build
./cmake - contains CMake settings file
./make - contains common GNU make rules and settings
./doc - contains the API documentation of the embARC MLI library
./include - include files with API prototypes and types
./lib/src - source code of embARC MLI Library
./lib/gen - auxiliary generation scripts for LUT tables
./lib/make - makefiles for library and package
./user_tests - set of basic tests for library primitives
./examples - source code of examples (see Examples and Tests) section
./examples/auxiliary - source code of helper functions used for the examples
./hw - contains HW templates (*.tcf files). See related readme file
Quick start guide is not yet defined. If you don't want to read the whole readme, as a compromise you can proceed with the following steps, to first build the MLI library for x86 emulation:
As the next step, you can repeat this recipe for ARC processors:
Afterward you can continue with familiarizing yourself with the documentation, which contains all the necessary info and references.
Note that it is highly recommended to use DBG_MODE_DEBUG configuration option (see MLI_DEBUG_MODE) for early development of applications based on embARC MLI Library because it provides additional diagnostic output which can help you quickly track down misuse of the API.
The embARC MLI Library uses CMake as a backend for the platform independent project generation and GNU Make as a front end to invoke CMake and to run tests. Alternatively, after CMake configures the project for the desired platform, you can work with its output stored in obj folder as you may be used to.
Basic build requirements are the following:
A compatible version of gmake is also delivered with the MetaWare Development Tools 2020.12 and higher. All command examples in the repo readmes will use gmake, but you can replace it with your suitable and compatible one.
The embARC MLI front end Make infrastructure provides targets for easy configuration of the project for a desired platform and toolchain. It also can build from sources, run tests and examples.
General template of the build command looks like:
gmake <target> <options> Available <targets>:
build - configure project and build binaries. clean - delete binaries and object files for configured project.cleanall - delete all configured projects and binaries.Note that tests and example applications have separate makefiles with additional targets which aren't explained here. See Examples and Tests section for info and references
<options> are described in the Build Configuration Options section below. Here is a list of links for available options:
ROUND_MODETCF_FILEBUILDLIB_DIRMLI_BUILD_REFERENCEFULL_ACCUJOBSVERBOSEOPTMODEMLI_DEBUG_MODEDEBUG_BUILDRECONFIGUREGEN_EXAMPLESNote that tests and example applications are part of the same generated CMake build system as the library itself which behavior depends on build configuration options). Tests and examples also may be adjusted using their own configuration options not listed above. See Examples and Tests section for info and references.
The embARC MLI Library can be built for the following platforms:
Build for these platforms creates separate projects in obj directory and separate binaries in bin directory. Build process for supported platforms is defined below.
The embARC MLI Library can be built for host platform and used in compatible applications to ease early development or verification. x86 and x64 architectures are supported, but for simplicity only x86 will be mentioned within documentation. No optimization is applied for this platform. Depending on the MLI build configuration, calculation results on x86 platform can be bit exact with desired ARC processor within defined behavior of MLI Functions.
The x86 Host emulation of the library has been tested with the following toolchains:
To build embARC MLI library you need
gmake build ROUND_MODE=[UP|CONVERGENT] <Additional options>ROUND_MODE is a mandatory option for x86 host emulation target. TCF_FILE option must not be used (only empty value is allowed).
As a result of configuration and build you will find bin/native folder with the library binary file and obj/native directory with generated project for the default toolchain and IDE within the environment.
<Additional options> which are applicable for this mode are JOBS, VERBOSE, FULL_ACCU, MLI_DEBUG_MODE, RECONFIGURE, GEN_EXAMPLES.
<Additional options> which have no effect or do not make sense in this mode are BUILDLIB_DIR, MLI_BUILD_REFERENCE, OPTMODE, DEBUG_BUILD.
The first step is to open a command line and change working directory to the root of the embARC MLI repo. Afterward, you can use one of the following commands.
Build project to emulate ARC VPX platform:
gmake build ROUND_MODE=UP FULL_ACCU=OFF Build project to emulate ARC VPX platform with full debug checking of parameters and assertions in runtime. Use multithreaded build process (4 threads):
gmake build ROUND_MODE=UP FULL_ACCU=OFF JOBS=4 MLI_DEBUG_MODE=DBG_MODE_FULL Main target platforms for embARC MLI Library are ARC processors. The specific processor family is determined by *.tcf file provided for library configuration. It is highly recommended to use embARC MLI 2.0 for VPX processor only. EM/HS targets are not properly tested and optimized. You can use embARC MLI 1.1 instead.
embARC MLI Library build for ARC processors requires MetaWare Development Tools (MWDT) version 2021.03 and higher.
To build embARC MLI library you need
gmake build TCF_FILE=<path_to_tcf> [BUILDLIB_DIR=<path_to_target_rt_libs>] <Additional options>TCF_FILE is a mandatory option for ARC target.
In case you are going to compile and run tests or examples it is better to provide the path to a runtime library using the BUILDLIB_DIR option.
As a result of configuration and build you will find bin/arc folder with the MLI library and obj/arc directory with generated Makefile project configured to use MWDT toolchain. If you use MLI_BUILD_REFERENCE option, then artifacts will be created in bin/arc_ref and obj/arc_ref directories correspondingly.
<Additional options> which are applicable for this mode are
JOBS, VERBOSE,
MLI_BUILD_REFERENCE, MLI_DEBUG_MODE,
DEBUG_BUILD, RECONFIGURE, GEN_EXAMPLES,
OPTMODE.
<Additional options> which have no or limited effect in this mode are FULL_ACCU, ROUND_MODE. ROUND_MODE option is applicable only for ARC EMxD family.
The following commands assume usage of the recommended VPX configuration. TCF for this configuration you need to generate using tcfgen tool delivered with MetaWare Development tools, in order to ensure sufficient target memory to run all of the examples. The first step is to open a command line and change working directory to the root of the embARC MLI repo. Then use the following command to generate recommended tcf file taking default vpx5_integar_full configuration as basis:
tcfgen -o ./hw/vpx5_integer_full.tcf -tcf=vpx5_integer_full -iccm_size=0x80000 -dccm_size=0x40000Afterward, you can use one of the following commands to configure and build the package:
Build project for recommended ARC VPX evaluation target. BUILDLIB_DIR is mandatory for this, but default "vpx5_integer_full" pack delivered with MWDT tools can be used. Use multithreaded build process (4 threads):
gmake TCF_FILE=./hw/vpx5_integer_full.tcf BUILDLIB_DIR=vpx5_integer_full JOBS=4 build Build project for recommended ARC VPX evaluation target optimized for code size and with full debug checking of parameters and assertions in runtime. Use multithreaded build process (4 jobs):
gmake build TCF_FILE=./hw/vpx5_integer_full.tcf BUILDLIB_DIR=vpx5_integer_full \
OPTMODE=size MLI_DEBUG_MODE=DBG_MODE_FULL JOBS=4Build project for recommended ARC VPX evaluation target using reference code. It's unoptimized straightforward and expected to be bitwise with optimized one. Use multithreaded build process (4 jobs) and artifacts are stored in bin/arc_ref and obj/arc_ref:
gmake build TCF_FILE=./hw/vpx5_integer_full.tcf BUILDLIB_DIR=vpx5_integer_full \
MLI_BUILD_REFERENCE=ON JOBS=4ROUND_MODEDescription: Rounding mode for low level math on casting and shifting values.
Syntax: ROUND_MODE=[UP|CONVERGENT]
Values:
UP - Rounding half up to the bigger value CONVERGENT - Rounding to the even value. Default:
CONVERGENT is a default. Might be changed. UP is a default and the only option. Can't be changed. FULL_ACCUDescription: Usage of full or reduced accumulator bit depth during accumulation. This option is provided to emulate VPX specific low level optimization and can be used only for x86 platform, or together with MLI_BUILD_REFERENCE=ON option.
Syntax: FULL_ACCU=[ON|OFF]
Values:
ON - Use full accumulator bit depth. OFF - Use reduced accumulator bit depth. Default: ON
TCF_FILEDescription: Tool configuration file (TCF) file path.
The TCF file defines ARC target processor hardware configuration. You can supply your own TCF that aligns with your hardware configuration. If you don't have a specific tcf file, you can use the tcfgen util delivered with MetaWare Development tools. Basic _vpx5_integerfull template delivered with MetaWare Development tools might be a good starting point. The tcfgen tool is documented in Linker and Utils guide which is also delivered with MetaWare Development tools. This option is mandatory for ARC platform and must not be set for x86 host emulation.
Syntax: TCF_FILE=<tcf-file>
Values: one of two options:
Default: No default value.
BUILDLIB_DIRDescription: Path to runtime libraries for the ARC platform to link applications with.
Runtime Libraries are required for tests and example applications delivered with MLI Library package, but not needed for the library build.
While for some targets not setting this option is acceptable (EMxD), it's highly recommended to build libraries specifically for your target. It can be done using the buildlib util delivered with MetaWare Development tools. The buildlib tool is documented in Linker and Utils guide which is also delivered with MetaWare Development tools.
Alternatively, you can also pass the name of the runtime library delivered with MetaWare Development tools if it is compatible with your hardware configuration. For instance, together with TCF_FILE=hw\vpx5_integer_full.tcf you can use BUILDLIB_DIR=vpx5_integer_full to use compatible pre-built libraries within the Metaware distribution.
This option has no effect on x86 host emulation build.
Syntax: BUILDLIB_DIR=<target_rt_libs>
Values: one of two options:
Default: No default value. The MetaWare compiler choses a default library for the ARC platform, which could result in incompatibilities with the TCF-file you specified. In case you are going to compile and run tests or examples for the ARC platform, it's better to provide a runtime library path.
MLI_BUILD_REFERENCEDescription: Switch embARC MLI Library implementation between platform independent reference code and platform default code.
Reference code is a configurable straightforward unoptimized implementation. It's goal is to emulate desired ARC processor on the bit exact level within defined behavior of MLI Functions.
If this switch is turned on, artifacts will be generated into directory with _ref postfix (bin/arc_ref and obj/arc_ref for instance)
Syntax: MLI_BUILD_REFERENCE=[ON|OFF]
Values:
ON - Use reference implementation of the library. OFF - Use default implementation of the library for the platform (optimized for ARC and reference for x86). Default: OFF
JOBSDescription: Number of jobs (threads) used on workstation to build the MLI package. Increasing number of jobs can reduce build time.
Syntax: JOBS=<number of jobs>
Values: It is recommended to use value within [1; number of host logical cores] range.
Default: no default value (single thread)
VERBOSEDescription: Activates verbose output from CMake and build tools during build of the project.
Syntax: VERBOSE=[ON|OFF]
Values:
ON - Activates verbose output. OFF - Disables verbose output.Default: OFF
OPTMODEDescription: Define optimization mode of embARC MLI Library and all delivered examples and tests. This option has no effect on x86 host emulation build.
Syntax: OPTMODE=[speed|size]
Values:
speed - Build for optimal speed. size - Build for optimal code size.Default: speed
MLI_DEBUG_MODEDescription: Additional debug features mode.
To ease application debugging, additional debug features can be turned-on during build which includes:
stdout in case there is something wrong with function parameters. Assertions - halt execution in case some data assumptions are not met including function parameters and internal invariants.
For more info see Debug Mode section of MLI API Data chapter in the MLI API Documentation.
Note that it is highly recommended to use DBG_MODE_DEBUG configuration option for early development of applications based on embARC MLI Library because it provides additional diagnostic output which can help you quickly track down misuse of the API.
Syntax: MLI_DEBUG_MODE=DBG_MODE_[RELEASE|RET_CODES|ASSERT|DEBUG|FULL]
Values:
DBG_MODE_RELEASE - No debug. Messages:OFF; Assertions:OFF; ReturnCodes: Always OK.DBG_MODE_RET_CODES - Return codes mode. Messages:OFF; Assertions:OFF; ReturnCodes: Valid Return.DBG_MODE_ASSERT - Assert. Messages:OFF; Assertions:ON; Extra Assertions:OFF; ReturnCodes: Valid Return.DBG_MODE_DEBUG - Debug. Messages:ON; Assertions:ON; Extra Assertions:OFF; ReturnCodes: Valid Return.DBG_MODE_FULL - Full Debug. Messages:ON; Assertions:ON; Extra Assertions:ON; ReturnCodes: Valid Return. Default: DBG_MODE_RELEASE
DEBUG_BUILDDescription: Include debug information into binaries during build (-g flag). This option has no effect on x86 host emulation build.
Syntax: DEBUG_BUILD=[ON|OFF]
Values:
ON - Include debug information into binaries.OFF - Do not include debug information into binaries.Default: ON
RECONFIGUREDescription: Always executes the CMake configure step, even if a project has already been configured. It may cause unwanted rebuilds.
Syntax: RECONFIGURE=[ON|OFF]
Values:
ON - Reconfigure project.OFF - Do not reconfigure project.Default: OFF
GEN_EXAMPLESDescription: Include MLI Examples (./examples) into the generation and build process together with the library and tests.
Syntax: GEN_EXAMPLES=[1|0]
Values:
1 - Generate example projcets together with the library and tests.0 - Generate projects for the library and tests only.Default: 1
There are test and several examples supplied with embARC MLI Library. For information on how to build and run each example please go to the related directory and examine local README.
These are basic API level test applications to check that all the functions available at the API level work fine.
This example is a first step into API functions and data usage.
This example is a simple image classifier built on convolution, pooling and dense layers. It is based on standard Caffe tutorial for CIFAR-10 dataset.
LSTM Based Human Activity Recognition example. The model is intended to differentiate human activity between 6 classes based on inputs from embedded inertial sensors from waist-mounted smartphone.
More advanced but still compact face detection example. It shows how the slicing and data movement can be organised to efficiently use limited fast CCM memory.
This example shows how to convert EMNIST Tensorflow model into Tensorflow Lite Micro format and use it in application.
Q: I can not build and run example application for my Synopsys board (EMSK, IoTDK, etc), what I shall do?
A: It isn't supported at the moment. Currently we recommend only building for VPX and x86 emulation targets. You can use MLI 1.1 for EM/HS targets.
Q: Can I use ARC GNU tools to build embARC MLI library?
A: embARC MLI Library must be built by MetaWare Development Tools only.
Q: Can I use MetaWare Development Tools Lite to pre-build embARC MLI library and ARC GNU to build example application?
A: embARC MLI Library must be built by full version of MetaWare Development Tools. Binaries built with MWDT Lite are not compatible with ARC GNU Tools and full MetaWare Development Tools. Read the MWDT Lite documentation for details.