1993
DOI: 10.1109/2.247650
|View full text |Cite
|
Sign up to set email alerts
|

A framework for hardware/software codesign

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
17
0

Year Published

1996
1996
2002
2002

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 62 publications
(17 citation statements)
references
References 4 publications
0
17
0
Order By: Relevance
“…Thus, there exists a strong relationship between the models used for capturing system functionality and the abstraction level at which the partitioning is carried out. The partitioning procedure presented in this section attempts to perform a division of functionality at the level of operations specified in the hardware description language and is not a substitute for partitioning usually carried out at higher levels of abstractions such as "conceptual" or architectural-level [35] or configuration-level [36] where the authors consider architectural partitioning for multiple processors. The problem of partitioning here refers specifically to a partition of the system functionality represented by a flow graph model.…”
Section: Partitioningmentioning
confidence: 99%
“…Thus, there exists a strong relationship between the models used for capturing system functionality and the abstraction level at which the partitioning is carried out. The partitioning procedure presented in this section attempts to perform a division of functionality at the level of operations specified in the hardware description language and is not a substitute for partitioning usually carried out at higher levels of abstractions such as "conceptual" or architectural-level [35] or configuration-level [36] where the authors consider architectural partitioning for multiple processors. The problem of partitioning here refers specifically to a partition of the system functionality represented by a flow graph model.…”
Section: Partitioningmentioning
confidence: 99%
“…Few papers have been published on automating the design of, say, a memory hierarchy or an I/O subsystem based on standard components. Notable exceptions to this rule are papers dealing with retargetable compilation (e.g., Theissinger et al [TSV94]), or with a very abstract formulation of partitioning for co-design (e.g., Kumar et al [KAJW92,KAJW93], Prakash and Parker [PP91], and Vahid and Gajski [VG92]). The structure of the application-specific hardware components, on the other hand, is generally much less constrained.…”
Section: Mapping From Specification To Architecturementioning
confidence: 99%
“…The initial partition is then improved by a Kernighan and Lin-like iterative swapping procedure. Kumar et al [KAJW92,KAJW93], on the other hand, consider partitioning in a very general and abstract form. They use a complex, set-based representation of the system, its various implementation choices and the various costs associated with them.…”
Section: Partitioningmentioning
confidence: 99%
“…For example, the codesign framework proposed by Kumar et al [1993] presented an important concept of iterative system refinements using an integrated hardwaresoftware model. The codesign methodology proposed by Thomas et al [1993] used a mixed hardware-software system model that facilitated cosimulation and cosynthesis which included performing system partitioning at the task level.…”
Section: Previous and Related Workmentioning
confidence: 99%