A framework for generic HW/SW communication using remote method invocation

Abstract

Implementation of communication between different tasks of a concurrent embedded system is a challenging problem. The aim of our work is to support the refinement and relocation of tasks onto different execution units, such as processors running different operating system or even dedicated hardware. For this purpose communication should be transparent and as independent as possible from the underlying middleware or embedded operating system. Moreover, communication should also be transparent accros the HW/SW boundary.In this work we present a generic framework for seamless communication of (software) tasks with shared resources, called Shared Objects. Communication is implemented using a method-based interface realizing a Remote Method Invocation (RMI) protocol. Our shared communication resources can either be implemented as dedicated hardware, as shared memory or local tasks. The presented framework is a first step towards the unification of shared resource access based on embedded Linux. The effectiveness of our approach is be evaluated with different task mappings and shared resource access implementation styles.

Automatic synthesis of communication and concurrency for exploring component-based system implementations considering UML channel semantics

“…In the SystemC context, [3] presents a generic framework for HW/SW communication of functional tasks with shared resources. Communication is implemented using a method-based interface implementing a RMI protocol.…”

“…For this purpose, the approach starts by requiring a complete description of the system in UML/MARTE. Following this standard profile, the system is described as a set of components requiring and providing services, in a client-server structure 3 . Additionally, the user must also specify HW platform details, selecting HW resource allocations.…”

Hybrid distributed application in banking transaction using remote method invocation

“…Therefore, we are going to used three-tier application [3] because three-tier applications support deployment of distributed-based applications [4] component. In distributed applications it takes a remote method call, then we are going to used Remote Method Invocation [5] to develop this system.…”