Embedded Java

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

Embedded Java at the Embedded World fair 2014 in Nuremberg
IS2T embedded Java solution at Embedded World exhibition 2014 in Nuremberg

Although in the past some differences existed between embedded Java and traditional PC based Java solutions, the only difference now is that embedded Java code in these embedded systems is mainly contained in constrained memory, such as flash memory. A complete convergence has taken place since 2010, and now Java software components running on large systems can run directly with no recompilation at all on design-to-cost mass-production devices (consumers, industrial, white goods, healthcare, metering, smart markets in general,...)

Recent developments in the field are

  • In 2014, EBV annonced JAKARTA : a hardware & software application Java platform ready for new areas of low cost Human Machine Interfaces based on FREESCALE KINETIS-L [1].
  • In October 2013, Renesas Electronics announced providing Embedded Java for RX Microcontrollers [2].
  • In January 2013, STMicroelectronics announced full Java support for STM32 F3/F4-series microcontrollers STM32 and stm32java.
  • In March 2013, MicroEJ product line from IS2T for ARM Cortex-M (all RTOS), ARM Cortex-A (Linux, Integrity, VxWorks), ARM7-TDMI (all RTOS), ARM9 (Linux, Integrity), AVR32 UC3 (all RTOS), V850 (all RTOS).
  • Before 2012, the Squawk Virtual Machine, a JVM developed by Sun Microsystems and deployed as part of Project Sun SPOT.

CORE embedded Java API for a unified Embedded Java ecosystem

The core Java API

In order for a software component to run on any Java system, it must target the core minimal API provided by the different providers of the embedded Java ecosystem. Companies such as Aplix, Google, IS2T, Myriad, Oracle, ... share the same eight packages of pre-written programs. The packages (java.lang, java.io, java.util, ... ) form the CORE Embedded Java API, which means that embedded programmers using the Java language can use them in order to make any worthwhile use of the Java language.

Java SE embedded API from ORACLE

Java SE embedded is based on desktop Java Platform, Standard Edition.[1] It is designed to be used on systems with at least 32 MB of RAM, and can work on Linux ARM, x86, or Power Architecture, and Windows XP and Windows XP Embedded architectures.

Java ME embedded API from ORACLE

Java ME embedded is based on the Connected Device Configuration subset of Java Platform, Micro Edition.[2] It is designed to be used on systems with at least 8 MB of RAM, and can work on Linux ARM, PowerPC, or MIPS architecture.

The offering of Java for embedded devices is growing fast with a large ecosystem of companies that provide Embedded Java virtual machines for ARM MCU based Cortex-M serie (ST, Freescale, Renesas, NXP, ... ), and MPU based solution (TI, Renesas, Freescale, ...).

Embedded Java minimal requirements starts at only 30KB of (internal) flash and less than 2KB of (internal) RAM. In order to save Bill Of Material, most Embedded Java engines execute code in place, which avoids copying the code in RAM.

Embedded Device Configuration API from E-S-R consortium

The Embedded Device Configuration specification defines the minimal embedded standard runtime environment for embedded Java devices. It defines all the default CORE API packages (138 classes/interfaces):

  • java.io
  • java.lang
  • java.lang.annotation
  • java.lang.ref
  • java.lang.reflect
  • java.util

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.

External links