Hardware Objects for Java

Proceedings of the 12th International Workshop on Java Technologies for Real-Time and Embedded Systems

Dalsgaard

Hansen

et al. 2014

Self Cite

The Certifiable Java for Embedded Systems (CJ4ES) project aimed to develop a prototype development environment and platform for safety-critical software for embedded applications. There are three core constituents: A profile of the Java programming language that is tailored for safety-critical applications, a predictable Java processor built with FPGA technology, and an Eclipse based application development environment that binds the profile and the platform together and provides analyses that help to provide evidence that can be used as part of a safety case. This paper summarizes key contributions within these areas during the three-year project period. In the conclusion the overall result of the project is assessed.

Section: The Hardware Near Virtual Machinementioning

confidence: 99%

Certifiable Java for Embedded Systems

Proceedings of the 12th International Workshop on Java Technologies for Real-Time and Embedded Systems

Dalsgaard

Hansen

et al. 2014

Self Cite

“…We would have preferred a more object-oriented way, the so-called hardware objects [21], to access low-level IO registers and DMA memory. For the implementation of the SCJ style low-level device access we can either use native system methods or hardware object based arrays.…”

Section: Low-level Device Accessmentioning

confidence: 99%

Safety-critical Java on a Java processor

Proceedings of the 10th International Workshop on Java Technologies for Real-Time and Embedded Systems

Rios

2012

Self Cite

The safety-critical Java (SCJ) specification is developed within the Java Community Process under specification request number JSR 302. The specification is available as public draft, but details are still discussed by the expert group. In this stage of the specification we need prototype implementations of SCJ and first test applications that are written with SCJ, even when the specification is not finalized. The feedback from those prototype implementations is needed for final decisions. To help the SCJ expert group, a prototype implementation of SCJ on top of the Java optimized processor is developed and presented in this paper. This implementation raises issues in the SCJ specification and provides feedback to the expert group.

“…Applications provide handlers via objects that implements Runnable and register the object for a interrupt number. We reuse here the I/O Factory presented in [9]. Figure 2 shows a simple example of an interrupt handler implemented in Java.…”

Section: Interrupt Handlingmentioning

confidence: 99%

“…To perform this access efficiently, which is a requirement for interrupt handlers, we use hardware objects as defined in [9]. The hardware objects rs232 and interruptControl has been defined to fit the physical hardware platform and allows the interrupt handler to access appropriate device registers directly.…”

Section: Accessing Device Registersmentioning

confidence: 99%

Interrupt Handlers in Java

Korsholm

2008 11th IEEE International Symposium on Object and Component-Oriented Real-Time Distributed Computing (ISORC)

Ravn

2008

Self Cite

An important part of implementing device drivers is to control the interrupt facilities of the hardware platform and to program interrupt handlers. Current methods for handling interrupts in Java use a server thread waiting for the VM to signal an interrupt occurrence. It means that the interrupt is handled at a later time, which has some disadvantages. We present constructs that allow interrupts to be handled directly and not at a later point decided by a scheduler. A desirable feature of our approach is that we do not require a native middelware layer but can handle interrupts entirely with Java code. We have implemented our approach using an interpreter and a Java processor, and give an example demonstrating its use.