2019
DOI: 10.3390/electronics8020211
|View full text |Cite
|
Sign up to set email alerts
|

Hardware RTOS: Custom Scheduler Implementation Based on Multiple Pipeline Registers and MIPS32 Architecture

Abstract: The task context switch operation, the inter-task synchronization and communication mechanisms, as well as the jitter occurred in treating aperiodic events, are crucial factors in implementing real-time operating systems (RTOS). In practice and literature, several solutions can be identified for improving the response speed and performance of real-time systems. Software implementations of RTOS-specific functions can generate significant delays, adversely affecting the deadlines required for certain application… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2

Citation Types

0
11
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
6
2

Relationship

2
6

Authors

Journals

citations
Cited by 11 publications
(11 citation statements)
references
References 24 publications
0
11
0
Order By: Relevance
“…The remarkability of the architecture is reflected in the name itself by specifying that the pipelined registers are multiplied, which allows the hardware context of the thread being executed to be saved, making it easier to stop an instance of the pipeline at any time and to change the context in a single clock cycle. The multiplication of hardware resources is (partly) illustrated in [ 7 ].…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…The remarkability of the architecture is reflected in the name itself by specifying that the pipelined registers are multiplied, which allows the hardware context of the thread being executed to be saved, making it easier to stop an instance of the pipeline at any time and to change the context in a single clock cycle. The multiplication of hardware resources is (partly) illustrated in [ 7 ].…”
Section: Related Workmentioning
confidence: 99%
“…Only one nMPRA hardware instance is active at any given time. An instance of nMPRA execution contains logical combinational blocks of the five pipeline stages (IF, ID, EXECUTE (EX), DATA MEMORY (MEM), and WRITE BACK (WB)), which are common resources shared by all nMPRA instances, as well as those from the private hardware resources associated with the software thread that is being instantiated (GPR, pipeline, and PC; status and control register file; flag file; work registers and/or counters [ 7 ]). A more detailed description of the architecture can be found in [ 6 ] with the appropriate terms that represent the architecture at that time.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Zagan et al [12] presented scheduling of tasks via the use of a hardware architecture as opposed to a software-based RTOS.…”
Section: Introductionmentioning
confidence: 99%
“…An alternative solution for this project could be the nMPRA (Multi Pipeline Register Architecture) processor implementation [25]. Using this processor with functions implemented in the hardware would add extra performance to the system, as well as superior energy efficiency.…”
mentioning
confidence: 99%