GIOVANNI DE MICHELI, FELLOW, IEEE, AND RAJESH K. GUPTA, MEMBER, IEEE Invited Newspaper
Most electronic systems, whether self-contained or embedded, possess a predominant digital component consisting of a components platform which executes software program programs. Hardware/software co-design means meeting system-level objectives by simply exploiting the synergism of hardware and software through their concurrent design. Co-design problems will vary п¬‚avors based on the application site, implementation technology and style methodology.
Digital hardware design has a growing number of similarities to software design and style. Hardware brake lines are often explained using building or encoding languages, and they are generally validated and implemented by executing software packages, which are occasionally conceived pertaining to the speciп¬Ѓc hardware design. Current built-in circuits can incorporate 1 (or more) processor core(s) and storage array(s) on a single substrate. These " devices on siliconвЂќ exhibit a substantial amount of embedded application, which provides п¬‚exibility for product evolution and differentiation reasons. Thus the style of these devices requires designers to be knowledgeable in the two hardware and software fields to make very good design
This newspaper introduces the reader to various areas of co-design. We highlight the commonalities and point out the differences in various co-design problems in certain application areas. Co-design concerns and their romance to classical system execution tasks happen to be discussed to assist the reader build a perspective about modern digital system style that depends on computer-aided design and style (CAD) tools and strategies.
Most executive designs can be viewed as systems,
my spouse and i. e., while collections of several elements whose mixed
operation supplies useful providers. Components may be
heterogeneous in nature and the interaction can be regulated by some simple or intricate means. Many examples of systems today will be either electronic digital in character (e. g.,
information control systems) or contain an electric
subsystem pertaining to monitoring and control (e. g., herb control).
Manuscript received Feb 1, mil novecentos e noventa e seis; revised Dec 2, 1996. This function was reinforced in part by simply DARPA, beneath Contract DABT 63-95-C0049, and part simply by NSF JOB Award MIP 95-01615. G. De Micheli is with the pc Systems Lab, Stanford College or university, Stanford, CALIFORNIA 94305 USA (e-mail: [email protected] stanford. edu).
R. E. Gupta is by using the Office of Computer Science, University or college of Washington dc, Irvine, LOS ANGELES 92797 UNITED STATES (e-mail: [email protected] uci. edu). Publisher Item Identiп¬Ѓer S i9000 0018-9219(97)02017-3.
In addition, the execution of electric systems and
subsystems displays often a predominant digital element.
We concentrate in this daily news on the digital component of
digital systems, and refer to these people as (digital) systems for brevity. Nearly all such devices are pre-reglable,
and thus incorporate hardware and software components. The
value of a system can be assessed by a few objectives that
are speciп¬Ѓc to their application site (e. g., performance,
design, and developing cost, and ease of programmability) and this will depend on both hardware and the software pieces. Hardware/software co-design means meeting
system-level targets by exploiting the synergism of
software and hardware through their particular concurrent style.
Since digital systems have distinct organizations and applications, there are many co-design challenges of interest. Such problems have already been tackled simply by skillful designers
for many years, nevertheless detailed-level design and style performed by simply
humans can be a time-consuming and error-prone job.
Moreover, the large amount of information involved in codesign problems makes it unlikely that human designers can enhance all targets, thus ultimately causing products whose
value is leaner than the potential one.
The recent within interest in hardware/software codesign is because of the...
Sources:  A. Aho, L. Sethi, and J. Ullman, Compilers: Principles, Techniques and Tools. Studying, MA: Addison-Wesley, 1988.
ICCD, 1994, pp. 278вЂ“281.
architectures, вЂќ in Proc. DAC, 1996, pp. 591вЂ“596.
EURODAC, 1994, pp. 220вЂ“225.
 A. Bender, " Style of an optimum loosely paired heterogeneous multiprocessor system, вЂќ in Proc. EDTC, 1996, pp.
1270вЂ“1282, Sept. 1991.
McCanny, M. McWhirter, and E. Schwartzlander, Eds. Englewood Cliffs, NJ-NEW JERSEY: Prentice-Hall, 1989.
Micheli and M. Sami, Eds. Amsterdam: Kluwer, 1996, pp.
volume. 14, number 4, pp. 37вЂ“47, Aug. 1994.
embedded systems, вЂќ in Proc. DAC, 1995.
France, 1995, pp. 22вЂ“27.
Workshop about Hardware/Software Co-design, Sept. 1992.
Nets and Genetic Algorithms, Apr. 93, pp. 441вЂ“449.
Amsterdam: Kluwer, 1996.
New York: McGraw-Hill, 1994.
Micro, vol. 14, number 4, pp. 10вЂ“16, August. 1994.
37вЂ“53, Oct. 1990.
on Hardware/Software Codesign, Sept. 1994, pp. 22вЂ“24.