Device Driver Generation and Checking Approach

Towards a greater reliability of driver/device communication around the system life cycle through a contract‐based protocol specification

“…Although the current approach has only been validated in real hardware, there are already MDDC models in SystemC, on which experiments are also being carried out. The feasibility of this type of checking in high level models has been previously established in [9].…”

“…2, the front-end of this approach is a high-level specification written in a domain-specific language (DSL) called TDevC, which contains the interface descriptions and the communication protocol of the devices. This language has been under development since 2009 and has been extended to allow more complex specification of register access constraints as well as to allow sequences of register accesses, as observed in [9,10], including this current syntax and expression power.…”

Towards more reliable embedded systems through a mechanism for monitoring driver devices communication

“…The modules of the proposed monitoring mechanism are partially generated from a highlevel device specification in TDevC [4]. The SystemVerilog implementation of the generated modules can be synthesized in hardware (FPGA) and can be integrated with the complete system platform prototyped in FPGA.…”

“…As it can be seen in the Figure 1, the MDDC module captures the communication between the device controller and the driver; depending on the type of communication, the corresponding FSM checks if it will cause an incorrect behavior of the device and of the system. A first version of the monitoring mechanism has been proposed in [4].But this version was a very simple one and was able for verifying only reading and writing operations in a rather restrictive way.…”

“…The MDDC and FSM-set modules can be synthesized 978-1-4799-3946-6/14/$31.00 ©2014 IEEE 420 15th Int'l Symposium on Quality Electronic Design from a device specification in the TDevC [4] specification language together with platform information. The TDevC language is a domain specific language, which allows specifying, at a very high abstraction level, device and driver features that can be checked when executing the driver.…”