2007
DOI: 10.1109/dac.2007.375291
|View full text |Cite
|
Sign up to set email alerts
|

Automatic Verification of External Interrupt Behaviors for Microprocessor Design

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2018
2018
2018
2018

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 0 publications
0
1
0
Order By: Relevance
“…In order to verify the functionality of the DUV, it is also necessary to tests the core while handling interrupts, instruction and data bus delays (e.g., due to contention in multi-master bus or cache misses) along with the Software (SW) exceptions and normal instructions. Such events cannot be triggered using only instructions; therefore, external devices are involved to stimulate those conditions [31]. For this reason, a hardware implementation of the perturbation module has been designed to provide interrupt requests and bus stalls during RTL simulations.…”
Section: Figure 2 Ri5cy Architecturementioning
confidence: 99%
“…In order to verify the functionality of the DUV, it is also necessary to tests the core while handling interrupts, instruction and data bus delays (e.g., due to contention in multi-master bus or cache misses) along with the Software (SW) exceptions and normal instructions. Such events cannot be triggered using only instructions; therefore, external devices are involved to stimulate those conditions [31]. For this reason, a hardware implementation of the perturbation module has been designed to provide interrupt requests and bus stalls during RTL simulations.…”
Section: Figure 2 Ri5cy Architecturementioning
confidence: 99%