MicroEJ Glossary

Add-On Library
An Add-On Library is a pure managed code (Java) library. It runs over one or more Foundation Libraries.
Abstraction Layer
An Abstraction Layer is the C code that implements a Foundation Library’s low-level APIs over a board support package (BSP) or a C library.
Application

An Application is a software program that runs on a MICROEJ VEE.

Standalone Application
A Standalone Application is the main application that is executed by MICROEJ VEE. It is linked statically to produce a Mono-Sandbox Executable.
Sandboxed Application
A Sandboxed Application is an Application that can run over a Multi-Sandbox Executable. It is linked dynamically.
Kernel Application
A Kernel Application is a Standalone Application that implements the ability to be extended to produce a Multi-Sandbox Executable.
Architecture
An Architecture is a software package that includes the Core Engine port to a target instruction set and a C compiler, core Foundation Libraries ([EDC], [BON], [SNI], [KF]) and the Simulator. Architectures are distributed either as evaluation or production version.
Core Engine, also named “MEJ32”
The Core Engine, also named MEJ32, is a scalable 32-bit core for resource-constrained embedded devices. It is delivered in various flavors, mostly as a binary software package. The Core Engine allows applications written in various languages to run in a safe container.
Executable

An Executable is the result of the binary link of a Standalone Application with a VEE Port. It can be programmed into the flash memory of a device. (formerly called a Firmware)

Mono-Sandbox Executable
A Mono-Sandbox Executable is an Executable that implements an unmodifiable set of functions. (formerly called a Single-app Firmware)
Multi-Sandbox Executable
A Multi-Sandbox Executable is an Executable that implements the ability to be extended, by exposing a set of APIs and a memory space to link Sandboxed Applications. (formerly called a Multi-app Firmware)
Foundation Library
A Foundation Library is a library that provides core or hardware-dependent functionalities. A Foundation Library combines managed code (Java) and low-level APIs (C) implemented by one or more Abstraction Layers through a native interface (SNI).
MICROEJ SDK
MICROEJ SDK is a comprehensive tools suite for developers to build VEE Ports for their devices, create Applications, build Executable, and run Virtual Devices.
MICROEJ VEE
MICROEJ VEE is an applications container. VEE stands for Virtual Execution Environment, and refers to the first implementation that embeds a virtual 32-bit processor, hence the term “Virtual”. MICROEJ VEE runs on any OS/RTOS commonly used in embedded systems (FreeRTOS, QP/C, uc/OS, ThreadX, embOS, Mbed OS, Zephyr OS, VxWorks, PikeOS, Integrity, Linux, QNX, …) and can also run without RTOS (bare-metal) or proprietary RTOS. MICROEJ VEE includes the small MEJ32, along with a wide range of libraries (Add-On Libraries and Foundation Libraries).
Mock
A Mock is a mockup of a board support package (BSP) capability that mimics a hardware functionality for the Simulator.
Module Manager
MicroEJ Module Manager (MMM) downloads, installs and controls the consistency of all the dependencies and versions required to build and publish a MicroEJ asset. It is based on Semantic Versioning specification.
Simulator
The Simulator allows running Applications on a target hardware simulator on the developer’s desktop computer. The Simulator runs one or more Mock that mimics the hardware functionality. It enables developers to develop their Applications without the need of hardware.
VEE Port
A VEE Port is an implementation of MICROEJ VEE for a target device. It integrates an Architecture, one or more Foundation Libraries with their respective Abstraction Layers, and the board support package (BSP). It also includes associated Mocks for the Simulator. (formerly called Platform)
Virtual Device
A Virtual Device is a software package that includes the simulation part of an Executable: runtime, libraries and application(s). It can be run on any desktop computer without the need of the SDK.