Model checking C source code for embedded systems

Schlich, Bastian; Kowalewski, Stefan

doi:10.1007/s10009-009-0106-5

Cited by 46 publications

(32 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…BLAST [7], BOOP [8]) [9] On the other hand, Lynette Millett sliced the Promela programming language, used to specify protocols for the Spin model checker [15]. A static program slice consists of the parts of a program that may affect or are affected by the value being computed at the point of interest.…”

Section: Related Workmentioning

confidence: 99%

Model Checking of Embedded Assembly Program Based on Simulation

Yamane

Konoshita

Kato

2017

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARY Embedded systems have been widely used. In addition, embedded systems have been gradually complicated. It is important to ensure the safety for embedded software by software model checking. We have developed a verification system for verifying embedded assembly programs. It generates exact Kripke structure by exhaustively and dynamically simulating assembly programs, and simultaneously verify it by model checking. In addition, we have introduced undefined values to reduce the number of states in order to avoid the state space explosion.

show abstract

Section: Related Workmentioning

confidence: 99%

Model Checking of Embedded Assembly Program Based on Simulation

Yamane

Konoshita

Kato

2017

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

show abstract

“…Furthermore, it will involve complex arithmetical computations, which typically make verification intractable for SAT based or OBDD based model checkers. See [9] for a survey on software model checking.…”

Section: Ivd Selecting a Model Checkermentioning

confidence: 99%

Model Checking Driven Simulation of Sat Procedures

Verzino¹,

Cavaliere²,

Mari

et al. 2012

SpaceOps 2012 Conference

View full text Add to dashboard Cite

A Satellite Operational Procedure (OP) consists of a set of instructions reading information from the satellite (telemetries, TM) and sending commands to it (telecommands, TC). An OP can be executed by a human or by a computer (on-board procedures). Typically OPs are mission critical systems since their failure may entail hardware damages, degradation of satellite services or costly human based recovery actions. For this reason OPs are typically thoroughly tested in order to have reasonable assurances about their correctness. Unfortunately, traditional simulation based verification of OPs is highly expensive, since it requires a high amount of time from highly skilled personnel and does not provide formal assurance about the correctness of the OP under verification.We show how a model checker (CMurphi) can be used to drive a satellite simulator (namely, SIMSAT). The proposed approach has the following benefits. First, it improves OP quality assurance by automatic exhaustive exploration of all possible simulation scenarios whereas a manually driven simulation campaign cannot offer any formal assurance on the coverage achieved by the simulation campaign. Second, it decreases OP verification costs by using a model checker to automatically drive (via fault injections) the simulator. The model checker will record the considered simulation scenarios and automatically generate fresh (i.e., not previously considered) scenarios automatically stopping when all meaningful scenarios have been considered. Third, our approach allows humans to focus on the design of disturbance models (e.g., how many faults it makes sense to consider, when such faults may occur, etc.) which are highly reusable across verification of similar OPs.We implemented a prototype system by interfacing the CMurphi model checker to the SIMSAT simulator. Our experimental results show the feasibility of the proposed approach.

show abstract

“…We tried to extend one of these C code model checkers to support all needed constructs, but we found out that the necessary changes were too costly [101,104]. Therefore, we propose another solution.…”

Section: Model Checking C Codementioning

confidence: 99%

Model Checking Software

Donaldson¹,

Parker²

2012

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Software of microcontrollers is getting more and more complex. It is mandatory to extensively analyze their software as errors can lead to severe failures or cause high costs. Model checking is a formal method used to verify whether a system satisfies certain properties.This thesis describes a new approach for model checking software for microcontrollers. In this approach, assembly code is used for model checking instead of an intermediate representation such as C code.The development of [mc]square, which is a microcontroller assembly code model checker implementing this approach, is detailed.[mc]square has a modular architecture to cope with the hardware dependency of this approach. The single steps of the model checking process are divided into separate packages. The creation of the states is conducted by a specific simulator, which is the only hardware-dependent package. Within the simulator, the different microcontrollers are modeled accurately.This work describes the modeling of the ATMEL ATmega16 microcontroller and details implemented abstraction techniques, which are used to tackle the stateexplosion problem. These abstraction techniques include lazy interrupt evaluation, lazy stack evaluation, delayed nondeterminism, dead variable reduction, and path reduction. Delayed nondeterminism introduces symbolic states, which represent a set of states, into [mc]square while still explicit model checking techniques are used. Thus, we successfully combined explicit and symbolic model checking techniques.A formal model of the simulator, which we developed to prove the correctness of abstraction techniques, is described. In this work, the formal model is used to show the correctness of delayed nondeterminism.To show the applicability of the approach, two case studies are described. In these case studies, we used programs of different sizes. All these programs were created by students in lab courses, during diploma theses, or in exercises without the intention to use them for model checking.

show abstract

Model checking C source code for embedded systems

Cited by 46 publications

References 30 publications

Model Checking of Embedded Assembly Program Based on Simulation

Model Checking of Embedded Assembly Program Based on Simulation

Model Checking Driven Simulation of Sat Procedures

Model Checking Software

Contact Info

Product

Resources

About