2004
DOI: 10.1109/tse.2004.64
|View full text |Cite
|
Sign up to set email alerts
|

Deadline analysis of interrupt-driven software

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
5

Citation Types

0
9
0

Year Published

2012
2012
2018
2018

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 18 publications
(9 citation statements)
references
References 31 publications
0
9
0
Order By: Relevance
“…There has also been some research on using program analysis techniques for interrupt‐driven software . For example, Schlich et al use model checking of assembly code software for microcontrollers; however, this approach does not check temporal properties of the software.…”
Section: Related Workmentioning
confidence: 99%
“…There has also been some research on using program analysis techniques for interrupt‐driven software . For example, Schlich et al use model checking of assembly code software for microcontrollers; however, this approach does not check temporal properties of the software.…”
Section: Related Workmentioning
confidence: 99%
“…Analysis of interrupt-driven programs. In the literature, there are a few work on analyzing and verifying IDPs [3,4,20,21]. Brylow et al [3] propose a static analysis method for interrupt-driven Z86-based software.…”
Section: Related Workmentioning
confidence: 99%
“…Researchers attempted to apply different formal methods to interrupts. Palsberg et al [17], [18], [19], [20] performed a series of studies on interrupt-driven Z86-based software. They proposed a typed interrupt calculus, and developed a tool to analyze interrupt latencies, stack sizes, deadlines, and verify fundamental properties.…”
Section: Related Workmentioning
confidence: 99%