Hardware Software Codesign

Topics: Microcontroller, Microprocessor, Computer software Pages: 53 (14613 words) Published: April 11, 2013
Hardware/Software Co-Design

Most electronic systems, whether self-contained or embedded, have a predominant digital component consisting of a hardware platform which executes software application programs. Hardware/software co-design means meeting system-level objectives by exploiting the synergism of hardware and software through their concurrent design. Co-design problems have different flavors according to the application domain, implementation technology and design methodology.

Digital hardware design has increasingly more similarities to software design. Hardware circuits are often described using modeling or programming languages, and they are validated and implemented by executing software programs, which are sometimes conceived for the specific hardware design. Current integrated circuits can incorporate one (or more) processor core(s) and memory array(s) on a single substrate. These “systems on silicon” exhibit a sizable amount of embedded software, which provides flexibility for product evolution and differentiation purposes. Thus the design of these systems requires designers to be knowledgeable in both hardware and software domains to make good design

This paper introduces the reader to various aspects of co-design. We highlight the commonalities and point out the differences in various co-design problems in some application areas. Co-design issues and their relationship to classical system implementation tasks are discussed to help the reader develop a perspective on modern digital system design that relies on computer-aided design (CAD) tools and methods.

Most engineering designs can be viewed as systems,
i.e., as collections of several components whose combined
operation provides useful services. Components can be
heterogeneous in nature and their interaction may be regulated by some simple or complex means. Most examples of systems today are either electronic in nature (e.g.,
information processing systems) or contain an electronic
subsystem for monitoring and control (e.g., plant control).
Manuscript received February 1, 1996; revised December 2, 1996. This work was supported in part by DARPA, under Contract DABT 63-95-C0049, and in part by NSF CAREER Award MIP 95-01615. G. De Micheli is with the Computer Systems Laboratory, Stanford University, Stanford, CA 94305 USA (e-mail: nanni@galileo.stanford. edu).

R. K. Gupta is with the Department of Computer Science, University of California, Irvine, CA 92797 USA (e-mail: rgupta@ics.uci.edu). Publisher Item Identifier S 0018-9219(97)02017-3.

Moreover, the implementation of electronic systems and
subsystems shows often a predominant digital component.
We focus in this paper on the digital component of
electronic systems, and refer to them as (digital) systems for brevity. The majority of such systems are programmable,
and thus consist of hardware and software components. The
value of a system can be measured by some objectives that
are specific to its application domain (e.g., performance,
design, and manufacturing cost, and ease of programmability) and it depends on both the hardware and the software components. Hardware/software co-design means meeting
system-level objectives by exploiting the synergism of
hardware and software through their concurrent design.
Since digital systems have different organizations and applications, there are several co-design problems of interest. Such problems have been tackled by skillful designers
for many years, but detailed-level design performed by
humans is often a time-consuming and error-prone task.
Moreover, the large amount of information involved in codesign problems makes it unlikely that human designers can optimize all objectives, thus leading to products whose
value is lower than the potential one.
The recent rise in interest in hardware/software codesign is due to the...

References: [2] A. Aho, R. Sethi, and J. Ullman, Compilers: Principles, Techniques and Tools. Reading, MA: Addison-Wesley, 1988.
ICCD, 1994, pp. 278–281.
architectures,” in Proc. DAC, 1996, pp. 591–596.
EURODAC, 1994, pp. 220–225.
[11] A. Bender, “Design of an optimal loosely coupled heterogeneous multiprocessor system,” in Proc. EDTC, 1996, pp.
1270–1282, Sept. 1991.
McCanny, J. McWhirter, and E. Schwartzlander, Eds. Englewood Cliffs, NJ: Prentice-Hall, 1989.
Micheli and M. Sami, Eds. Amsterdam: Kluwer, 1996, pp.
vol. 14, no. 4, pp. 37–47, Aug. 1994.
embedded systems,” in Proc. DAC, 1995.
France, 1995, pp. 22–27.
Workshop on Hardware/Software Co-design, Sept. 1992.
Nets and Genetic Algorithms, Apr. 1993, pp. 441–449.
Amsterdam: Kluwer, 1996.
New York: McGraw-Hill, 1994.
Micro, vol. 14, no. 4, pp. 10–16, Aug. 1994.
37–53, Oct. 1990.
on Hardware/Software Codesign, Sept. 1994, pp. 22–24.
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Hardware and software problems of QWD Essay
  • Hardware and Software Essay
  • Software and Hardware Used and Limitations Essay
  • Number Systems and Hardware-Software Interface Essay
  • 2.Hardware and Software Selection Paper
  • Hardware Adn Software Selection Essay
  • hardware and software system Essay
  • Computer Hardware and Software Essay

Become a StudyMode Member

Sign Up - It's Free