Embedded systems are informally defined as a collection of programmable parts surrounded by ASICs and other standard components, that interact continuously with an environment through sensors and actuators. The programmable parts include micro-controllers and Digital Signal Processors (DSPs).
Embedded systems are often used in life-critical situations, where reliability and safety are more important criteria than performance. Today, embedded systems are designed with an ad hoc approach that is heavily based on earlier experience with similar products and on manual design. Use of higher-level languages such as C helps structure the design somewhat, but with increasing complexity it is not sufficient. Formal verification and automatic synthesis of implementations are the surest ways to guarantee safety.
Thus, the POLIS system which is a co-design environment for embedded systems is based on a formal model of computation.
POLIS was initiated in 1988 as a research project at the University of California at Berkeley and, over the years, grew into a full design methodology with a software system supporting it.
Hardware-Software Co-Design of Embedded Systems: The POLIS Approach is intended to give a complete overview of the POLIS system including its formal and algorithmic aspects.
Hardware-Software Co-Design of Embedded Systems: The POLIS Approach will be of interest to embedded system designers (automotive electronics, consumer electronics and telecommunications), micro-controller designers, CAD developers and students.
Inhaltsverzeichnis
1 Introduction. - 1. 1 The Importance of Embedded Systems. - 1. 2 Design of Embedded Systems. - 1. 3 The POLIS System. - 1. 4 Book Organization. - 2 Models and Representations. - 2. 1 Co-design models and languages. - 2. 2 CFSMs: Intuitive Semantics. - 2. 3 CFSMs: Mathematical Model. - 2. 4 CFSMs: Modeling Data Flow. - 2. 5 The SHIFT Format. - 2. 6 Specification: Synchronous Languages. - 2. 7 Overview of the ESTEREL language. - 2. 8 Specification: Graphical FSMs. - 2. 9 Modeling Software CFSMs. - 2. 10 Software Cost Model. - 2. 11 Processor Characterization Model. - 3 Synthesis. - 3. 1 Partitioning and Architecture Selection. - 3. 2 Software Synthesis. - 3. 3 Software Cost Estimation. - 3. 4 Hardware Synthesis. - 4 Interface Synthesis and the Real-Time Operating System. - 4. 1 Interface synthesis. - 4. 2 Real-Time Operating System Synthesis. - 4. 3 Network-Specific Parts: Interfacing Hardware and Software. - 4. 4 Target-Specific Parts: Creating an Abstraction. - 4. 5 Scheduling-Specific Parts: Coordinating sw-CFSMs. - 4. 6 Common Parts: Filling the Gaps. - 4. 7 Schedule Validation. - 5 Verification. - 5. 1 Rapid Prototyping. - 5. 2 Simulation. - 5. 3 Co-simulation using the PTOLEMY environment. - 5. 4 Simulation as partitioning support. - 5. 5 High-level Co-simulation using VHDL. - 5. 6 Formal Verification. - 6 Interfacing to External Hardware and Software. - 6. 1 External Hardware. - 6. 2 External Software. - 6. 3 Interfacing to an External RTOS. - 7 Design Examples. - 7. 1 A Dashboard Controller. - 7. 2 An Automotive Bus Controller. - 7. 3 A Shock Absorber Controller. - 8 Conclusions and Future Work. - A Glossary. - B The Syntax of Shift. - References.
