Page 43

EETE APR 2014

A42E_EETIMES2_37x10_87_Layout 1 3/6/14 9:37 AM the execution framework for the future hosted Features designed by 3rd parties Transformers and Inductors think PICO small! ...think... low profile from .18" ht. Over 5000 Std. Ultra Miniature Surface Mount (and Plug-In) Models Audio / 400Hz / Pulse Multiplex Data Bus / DC-DC Converter Transformers / Power & EMI Inductors See Pi c o’s fu ll Catalog immediate ly w w w. p i c o e l e c t ro n i c s . c o m PICO units manufactured and tested to MIL-PRF-27 requirements. QPL units are available. Delivery stock to one week for sample quantities. PICO Electronics,Inc. 143 Sparks Ave. Pelham, N.Y. 10803 E Mail: info@picoelectronics.com www.picoelectronics.com Pico Representatives Germany ELBV/Electra Bauemente Vertrieb E mail: info@elbv.de Phone: 49 089 460205442 Fax: 49 089 460205442 England Ginsbury Electronics Ltd E-mail: rbennett@ginsbury.co.uk Phone: 44 163 429800 Fax: 44 163 4290904 – see figure 3. The depicted architecture is called K&F (Kernel & Features) and aims at building a reliable eco-system: open architecture, modular and flexible, while guaranteeing reliability and robustness. K&F relies on a “Kernel” that is assumed to be reliable, and a set of application services, called “Features”, that can be dynamically loaded and unloaded in a reliable way at runtime. K&F identifies each Feature and its properties: this allows a reliable and secure resource access management based on every Feature’s ID. Because Features are considered as potentially non reliable software, the Kernel makes sure that if one of these is faulty, the others are not impacted. A bit of technology The Kernel is considered as reliable software (provided by the gateway manufacturer) Fig. 3: MicroEJ Hardware as a Service. and it can access the entire system without any restriction, including hardware resources and Features (as long as these Features are loaded). The Kernel relies on Feature IDs to rule the system access right policy: such a unique ID is associated to the three components of a Feature: the objects (dynamically allocated or not), the code of the classes, and the tasks (context dynamically allocated or not). A Feature is loaded as a binary entity and linked with the Kernel at runtime while other Features are running. Then, a task is created and the Feature starts in that task. For different reasons such as system integrity and reliability, a new Feature installation does not require any firmware modification and only relies on the virtual platform execution. To unload a Feature (user request, kill by the Kernel), all entities of that Feature are deleted: tasks are stopped, code is unlinked, and memory is freed. No stall reference, no zombie task, no phantom-code remains: the system is just as if the Feature had never been installed. The framework security relies on the standard java.lang.SecurityManager framework. Access rights are defined according to the eco-system requirements, using Feature IDs as a way to differentiate access rights and roles. The Kernel controls builtin resource usages such as CPU and memory usages. If a Feature exceeds its CPU quota or its memory space usage, it can be considered as an unreliable or unfriendly service, and various actions can be performed like unloading the Feature. MicroEJ Hardware as a Service MicroEJ® embedded Java platforms are optimized for design-to-cost embedded systems. With a full featured Java Virtual Machine core component as small as 30 Kbytes, it provides the embedded industries with the Java technology on low-cost and power efficient processors, from ARM Cortex-M (M0+/M3/M4) and Renesas RX, to more complex architectures such as ARM Cortex-A and MIPS based MPUs. The MicroEJ Hardware as a Service edition complies with the K&F architecture. With its built-in hypervisor, the Java platform memory footprint varies from 120 KBytes to 200 KBytes depending on the gateway complexity and system requirements, such as RTOS (μC/OS, RTX, FreeRTOS, Linux, VxWorks, Integrity, etc.), and system features (Ethernet, I2C, CAN, SPI, BT/BLE, USB, FileSystem, etc.). MicroEJ Hardware as a Service platform fits well with wearable gateways as it complies with its most important requirements: reliability, security and scalability. Its availability for a wide range of electronic systems makes it usable for embedded textile devices and also for wearable smart objects such as smartwatches. MicroEJ Hardware as a Service, with the K&F architecture, is a disruptive enabler to build an eco-system and defines new business models based on the monetization of data from the different sensors for various applications such as personal body care, mobile heath care and professional sport activities. www.electronics-eetimes.com Electronic Engineering Times Europe April 2014 43


EETE APR 2014
To see the actual publication please follow the link above