2009 14th IEEE International Conference on Engineering of Complex Computer Systems 2009
DOI: 10.1109/iceccs.2009.31
|View full text |Cite
|
Sign up to set email alerts
|

ASIIST: Application Specific I/O Integration Support Tool for Real-Time Bus Architecture Designs

Abstract: In hard real-time systems such as avionics, computer board level designs are typically customized to meet specific reliability and real time requirements. This paper focuses on computer-aided application-specific design of I/O architecture using PCI as an example. We have built a tool (ASIIST) that will enable engineers to explore design spaces at the I/O bus architecture level, performing analysis that incorporates bus protocols, to provide guarantees of real-time properties.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
7
0

Year Published

2009
2009
2016
2016

Publication Types

Select...
5
1
1

Relationship

3
4

Authors

Journals

citations
Cited by 20 publications
(7 citation statements)
references
References 12 publications
0
7
0
Order By: Relevance
“…The I/O bus is another example. When a new task is invoked, the I/O bus can carry the information of a previous task [16]. In this case, timing delay can be used to complete the previous task.…”
Section: Security and Schedulingmentioning
confidence: 99%
“…The I/O bus is another example. When a new task is invoked, the I/O bus can carry the information of a previous task [16]. In this case, timing delay can be used to complete the previous task.…”
Section: Security and Schedulingmentioning
confidence: 99%
“…Modeling complex COTS interconnections and estimating delay and buffer requirements for peripheral flows can be done in an AADL-based environment [11]. An eventbased model may be used to estimate delay for both computation and communication activities in a multicore systemon-chip [18].…”
Section: Related Workmentioning
confidence: 99%
“…Due to the lack of real-time prioritization, data I/O transactions travelling through the COTS bus into or out of main memory can suffer unpredictable delay and cause deadline misses [11]. Unfortunately, end-to-end real-time guarantees can not be achieved unless both tasks and I/O data transactions are properly processed in a prioritized manner.…”
Section: Introductionmentioning
confidence: 99%
“…Before reaching main memory, peripheral requests are typically buffered in the interconnection. Therefore, all peripheral requests coming from the same interconnection are aggregated (see [4] for details) into a single buffered flow α * i (t): for any interval of length t, α * i (t) is the maximum amount of time required by the aggregated peripheral to perform DMA operations in main memory. Each core P E i is characterized by a parameter C i , which is the time interval (assumed to be fixed) needed to service a memory request.…”
Section: Introductionmentioning
confidence: 99%