G. De Micheli and R.K. Gupta, "Hardware/Software Co-Design", Proceedings of the IEEE, V85, N3, 1997, pp. 349-365.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....Circuits and Systems Design (SBCCI 03) Given an adequate platform, a specific SoC design may be limited to platform tuning and software adaptation. As for the evolution of design techniques, since hardware and software compose SoCs, their design must rely on hardware software codesign techniques [11]. This is mandatory because the separate implementation of these entities can no longer achieve the best performance and time to market figures for highly complex ICs. Also, to achieve design reuse in general and IP core reuse in particular, modules have to be designed for reuse [12] Many of the ....

De Micheli, G.; Gupta, R. Hardware/software co-design. Proceedings of the IEEE, 85(3), March, 1997. pp 349-365.

....systems. 3)Frame Work Constrained. If unconstrained, the design space will be unbelievably large. A number of hardware software co design algorithms have been proposed which give the designer considerable freedom in terms of processor architecture, communication scheme, and task granularity[HAR,DEM, HEN,ENG,WOL]. The focus of these algorithms is on the top down design of systems. These approaches are important because they help develop methodologies that are applicable to different design situations, but the search spaces are large and they give designers choices that, realistically, they may not want. ....

G. De Micheli and R. K. Gupta, "Hardware/Software Co-Design", Proceedings of the IEEE, VOL. 85, No 3., March 1997, pp 349-365.

....on programmable logic. The processor provides the power to run an operating system and the flexibility of programmable logic to implement custom hardware on the chip. It is a classic example of hardware software co design: designing hardware and software concurrently to meet system level objectives[3]. This architecture allows us to conveniently decide what to implement in hardware and what to implement in software. With the added capability of programmable logic, much more of the system is under our control. It would allow us to use a physical shared memory, rather than just mapping the ....

DE MICHELI, G., AND GUPTA, R. Hardware /software co-design. Proc. IEEE 85, 3 (Mar. 1997), 349--365.

....results obtained using two large, multi process application codes indicate significant runtime benefits. 1. INTRODUCTION The success of any embedded system depends largely on the degree and effectiveness of the coordination between hardware and software. In fact, many codesign strategies (e.g. [3, 4, 2]) try to come up with hardware and software architectures that work well together. In this context, operating system (OS) plays an important role in closing the gap between hardware and software and interfacing them. It achieves this through several inter related activities such as resource ....

G. De Micheli and R. K. Gupta. Hardware-software codesign. Proceedings of the IEEE, 85, No 3. (March 1997):349--365.

....a reconfigurable composite microsystem design methodology that leverages hardware software codesign principles to achieve functional unit reusability. The hardware software codesign method provides design flexibility by allowing software to be compiled efficiently for a modular hardware platform [9]. We show that by partitioning the design parameters of microsystems into two categories nonreconfigurable hardware and reconfigurable software design parameters (referred to as NRDPs and RDPs, Manuscript received July 31, 2001; revised November 19, 2001. This work was supported in part by ....

G. De Micheli and R. K. Gupta, "Hardware/software co-design," Proc. IEEE, vol. 85, pp. 349--365, Mar. 1997.

.... To bring products to market faster and to identify problems earlier in the design cycle, industry has turned to design processes which rely heavily on hardware software co design and co verification and on reuse of complex building blocks (reusable cores and or intellectual property (IP) [1,2,3,4]. Co design refers to a process where design of hardware and software is very closely linked throughout the design process. In the traditional approach, tasks for hardware or software are identified immediately and are then developed largely independent of one another. They are only brought ....

. De Micheli, G., Gupta, R.K., "Hardware/Software CoDesign, " Proceedings of the IEEE, 1997, Vol. 85, No. 3, pp. 349-65.

....encountered, syed, designer has to change the hardware and or software designs, the payjk is substantial extra cost and even over due schedule. Hardware software codesign means meeting syting level objectives by exploiting thesyjB7LkN of hardware and software through their concurrent design [1]. Hardware software codesign is an emerging field of research that deals with embeddedsyedjk having both hardware and software. In past fewy ears, several codesign methodologies were proposed, such as COSMOS [2] TOSCA [3] ECOS project [4] and so on. Codesign tools also abound, such as ....

G. De Micheli and R.Gu[N] "Hardware/software codesign, " Proc. IEEE, vol.85, no.3, pp.349--365, March 1997.

....explore other advanced aspects of digital systems. One example is the development of CAD algorithms. With the hardware and software support tools available, there is one subject which is recent and important that can be examined in elective courses, the hardware software partitioning and codesign [25]. Last but not least, the authors are considering the application of digital systems design technology to other, apparently unrelated disciplines in Computer Science, such as compilers, computer networks, and computer graphics. IX. CONCLUSION The main goals set while developing the work proposed ....

G. De Micheli and M. Sami, Hardware Software Co-Design. Boston, MA: Kluwer, Jan. 1996, p. 467.

No context found.

G. De Micheli and M. Sami, editors, Hardware/Software Co-Design, KluwerAcademic Publishers, Norwell, MA, 1996.

No context found.

G. De Micheli and M. Sami, Hardware/Software Co-Design. Amsterdam: Kluwer, 1996.

....system implementation. The output is the final implementation of the embedded system, which results from the heterogeneous integration of architectures carried out in the synthesis process. A cost effective fulfilment of this design flow is carried out by hardware software co design methodologies [71, 98], which reduce the time to market parameter by jointly designing both hardware and software components of an embedded system architecture. This state of the art methodology is an elegant two dimensional extention of the onedimensional High Level Synthesis (HLS) methodology [40] which has gained ....

....architecture. This state of the art methodology is an elegant two dimensional extention of the onedimensional High Level Synthesis (HLS) methodology [40] which has gained vast acceptance in both industry and academia [17, 68, 99] Three processes are identified in the embedded system design flow [32, 71]: 1. Modelling 2. Validation 3. Synthesis These processes are fundamental steps in any methodology aimed to design an embedded system. In addition, correctness identification and estimation are intermediate steps which might be part of the methodology. However, in most cases these steps are ....

[Article contains additional citation context not shown here]

Giovanni De Micheli and Rajesh K. Gupta. Hardware/Software Co-Design. Proceedings of the IEEE, 85(3):349--365, March 1997.

....even for such devices which cannot be satisfactorily analyzed at the gate level only. 1. Introduction Hierarchical concurrent FSMs have been successfully introduced as a specification approach for controldominated systems, allowing to proceed through topdown definitions of system s behavior (see [5, 9, 11]) The same tools can be applied as well to design of large sequential circuits, for which straightforward gate level design, or even state table definition, would be practically infeasible. The above mentioned tools extend the classical FSM model by introducing hierarchy and concurrency and by ....

G. De Micheli and M. Sami. Hardware-software codesign. Kluwer Academic Publishers, 1996.

No context found.

G. De Micheli and R.K. Gupta, "Hardware/Software Co-Design", Proceedings of the IEEE, V85, N3, 1997, pp. 349-365.

No context found.

G. De Micheli and M.G. Sami eds., "Hardware/Software Co-Design", NATO ASI

No context found.

G. De Micheli, M. G. Sami, et al., "Hardware/Software Codesign," Kluwer Academic Publishers 1996.

No context found.

G. De Micheli and R. K. Gupta, "Hardware/software co-design," Proc. of IEEE, vol. 85, pp. 349--365, Mar. 1997.

No context found.

G. de Micheli and M. Sami, eds., Hardware /Software Co-Design, vol. 310 of NATO ASI Series E, Applied Sciences. Kluwer Academic Publishers, 1996.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC