2007 Design, Automation &Amp; Test in Europe Conference &Amp; Exhibition 2007
DOI: 10.1109/date.2007.364483
|View full text |Cite
|
Sign up to set email alerts
|

Interrupt and Low-level Programming Support for Expanding the Application Domain of Statically-Scheduled Horizontal-Microcoded Architectures in Embedded Systems

Abstract: The

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2008
2008
2021
2021

Publication Types

Select...
4
1

Relationship

1
4

Authors

Journals

citations
Cited by 5 publications
(3 citation statements)
references
References 12 publications
0
3
0
Order By: Relevance
“…Hierarchical modules have been described using netlist description using Generic Netlist Representation (GNR), which is a formal architecture description language (ADL) [17]. Pre-bound functions [18] have been used in order to achieve efficient utilization of resources and accurate execution timing. Different computational operations that can be executed in the same clock cycle have been merged to the same pre-bound function to maximize the exploitation of hardware resources and time.…”
Section: Results and Comparisonmentioning
confidence: 99%
“…Hierarchical modules have been described using netlist description using Generic Netlist Representation (GNR), which is a formal architecture description language (ADL) [17]. Pre-bound functions [18] have been used in order to achieve efficient utilization of resources and accurate execution timing. Different computational operations that can be executed in the same clock cycle have been merged to the same pre-bound function to maximize the exploitation of hardware resources and time.…”
Section: Results and Comparisonmentioning
confidence: 99%
“…Also, automatic tools can be used to generate NISC architectures customized for one or more applications Gorjiara 2007;Trajkovic et al 2006]. NISC customization can be done in three ways: (1) by changing number and type of components and their interconnectivity; (2) by adding custom functional units (ranging from simple bitwise operations to complex multi-operand operations); [Reshadi et al 2008] (3) by adding one or more external accelerators [Reshadi and Gajski 2007;Reshadi 2007], which may be custom NISCs themselves. The difference between (2) and (3) is that in (2) compiler schedules the communication between the custom unit and the rest of the datapath, while in (3) the software should explicitly define the communication.…”
Section: Overview Of Nisc Technologymentioning
confidence: 99%
“…In this context, the typical direct compilation of C codes describing the functionality using the NISC tool set gives inefficient hardware results. In order to achieve high performance and efficient resource utilization, the direct control of hardware resources is devised using pre-bound functions, which are C-like functions mapped by the compiler to specific hardware resources [22]. For a specific module, a pre-bound function is defined by declaring the proper control values and the utilized input/output ports.…”
Section: Adopted Design Flowmentioning
confidence: 99%