D. Gajski and F. Vahid, "Specification and design of embedded software /hardware systems", IEEE Design and Tests of Computer, vol. 12, no. 1, pp. 53--67, Jan. 1995.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....the designer with performance evaluation tools, in order to derive quantitative measures of the effectiveness of a given partition. In spite of the existing efforts to automate this process, yet there are few resources to aid the specification refinement, development and partitioning of a protocol [3][4] Several projects currently in progress are trying to integrate both HW and SW into the same design process: COSMOS [5] SpecSyn [6] Ptolemy [7] LYCOS [8] Chinook [9] e PISH [10] Fischer [4] proposes an integrated HW SW design to meet high performance in distributed systems, such as ....

D. Gajski and F. Vahid, "Specification and design of embedded software /hardware systems", IEEE Design and Tests of Computer, vol. 12, no. 1, pp. 53--67, Jan. 1995.

....the designer with performance evaluation tools, in order to derive quantitative measures of the effectiveness of a given partition. In spite of the existing efforts to automate this process, yet there are few resources to aid the specification refinement, development and partitioning of a protocol [2][3] Several projects currently in progress integrate both HW and SW into the same design process: COSMOS [4] SpecSyn [5] Ptolemy [6] LYCOS [7] Chinook [8] e PISH [9] Fischer [3] proposes an integrated HW SW design to meet high performance in distributed systems, such as multimedia systems. ....

D. Gajski and F. Vahid. Specification and design of embedded software/hardware systems. IEEE Design and Tests of Computer, 12(1):53--67, Jan. 1995.

....2 (ii) It is possible to retarget systems for different architectures. This ensures large variations in processors and can handle market pressure. ii) Code quality is comparable to that provided by a good engineer. The response to the above challenges can be met by hardware software co design [1, 7, 16] methodology. First, let us take a brief look at hardware software co design. The overall strategy of hardware software co design are usually captured by the following layers: 0) Requirement Capture Level: Requirement specification gives a set of explicit or implicit relations which involve ....

D. Gajski and F. Vahid. Specification and Design of Embedded SoftwareHardware Systems, 1995.

....measures of the effectiveness of a given partition. The decision to adopt a given HW SW partition is always taken by the designer. Although the efforts to automate this process, he still has few resources to aid him in the specification refinement, development and partitioning of the protocol [2][3] Several projects currently in progress are trying to integrate both HW and SW into the same design process: COSMOS [4] SpecSyn [5] Ptolomey [6] LYCOS [7] Chinook [8] e PISH [9] Fischer [3] proposes an integrated HW SW design to meet a high performance in distributed systems, like ....

D. Gajski and F. Vahid, "Specification and design of embedded software/hardware systems ", IEEE Design and Tests of Computer, vol. 12, no. 1, pp. 53--67, Jan. 1995.

.... design courses: on the one side, the availability of a tool, which can provide practical example sessions in order to show the main concepts about embedded system architecture; on the other side, fostering the students to the actual design activity of embedded application oriented systems [Gajski95]. The idea of building this environment came up from the observation that actual computer systems and or commercial design tools are generally not suitable to be used as didactic tools and to present the basic concepts of architecture design in both basic and advanced Computer Engineering ....

....methodologies like co design, and system in a chip approach, implies the demand for specific architectural knowledge by computer engineers. A typical design path starts from the definition of the hardware software requirements needed to implement the specified function through the embedded system [Gajski95]. After that, the designer usually has a prototype program and a prototype hardware configuration that has to be tuned in order to meet the low power consumption and or low cost requirements or to minimize execution time. At this point, it is very important that the designer understands how to ....

D. D. Gajski and F. Vahid, "Specification and Design of Embedded Software-Hardware Systems, " IEEE Design & Test of Computers, vol. 12, no. 1, Spring 1995.

....that program. The approach makes use of a software environment used in Computer Architecture courses at the University of Pisa. We will show that the student can extract from the program much significant information to carry out the actual design activity of embedded application oriented systems [2]. The environment has been made up by our University and is integrated in a toolkit (JumpStart) distributed by VLSI Technology, Inc. for the design of ARM based applications. ARM [6] is a 32 bit microprocessor designed by ARM Ltd. and largely used in embedded products. It uses RISC technology ....

D. D. Gajski and F. Vahid. Specification and design of embedded software-hardware systems. IEEE Design & Test of Computers, 12(1), Spring 1995.

.... a single instrument: on the one side, it supplies the teacher with a tool to be used in practical example sessions while dealing with the main concepts about cache memories [10] on the other side, it aims to help the student in the actual design activity of embedded application oriented systems [3]. The package includes a parametric cache simulation and performance analysis tool (ChARM) developed by the University of Pisa for VLSI Technology, Inc. 8] and the JumpStart [7] toolkit, a graphical development environment by VLSI Technology, Inc. for the design of ARM based applications. ARM ....

D. D. Gajski and F. Vahid. Specification and design of embedded software-hardware systems. IEEE Design & Test of Computers, 12(1), Spring 1995.

.... simulators, integrated environments, and graphical tools is a well accepted methodology to explain the internal behavior of such systems [1] This approach proves particularly important in respect to the emerging co design technologies for the development of embedded system hardware and software [2]. In that case, the design process can be quite complex, because it has to face a number of various and often conflicting component requirements: cost effective performance through small die size and low power consumption, particularly for mobile systems, but also high processing power (real time ....

D. D. Gajski and F. Vahid, "Specification and design of embedded software-hardware systems," IEEE Design & Test of Computers, vol. 12, no. 1, Spring 1995.

....simulation of multiple functional models. The simulator accepts a gate level description of the hardware, the assembly code of the software component 2 and a description of the interface, giving as result a cycle by cycle simulation. Gajski et al. developed a new framework called SpecSyn [26] based on specification refinement [27] The system s behaviour was captured with SpecCharts [24] a hierarchical Program State Machine (PSM) language [27] Then, as the group evolved, they created a complete specification language, called SpecC 3 [29, 63, 30] which keeps the attention of ....

D. D. Gajski and F. Vahid. Specification and Design of Embedded Software/Hardware Systems. Technical Report CS-94-08, U. C. RiversideDepartment of Computer Science, Oct. 24 1994. 14

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