1 / 12

Summary and Trends

Summary and Trends. Ingo Sander ingo@imit.kth.se. Embedded Systems. Different Requirements are imposed on Embedded Systems, such as Costs Time-To-Market Performance Power Efficiency Safety Many Embedded Systems have to interact with several systems at the same time

adina
Download Presentation

Summary and Trends

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Summary and Trends Ingo Sander ingo@imit.kth.se

  2. Embedded Systems • Different Requirements are imposed on Embedded Systems, such as • Costs • Time-To-Market • Performance • Power Efficiency • Safety • Many Embedded Systems have to interact with several systems at the same time • Can be modeled as parallel tasks • Can be implemented on a parallel architecture 2B1445 Embedded Systems

  3. Specification of Embedded Systems • Contrary Requirements • Abstract specifications lead to a shorter design time (time-to-market) • Details are needed for an efficient implementation (performance, power) • Ideal Design Process • Model the system with an abstract language and compile it to an efficient implementation! 2B1445 Embedded Systems

  4. Idea (Specification) Magic Product (Implementation) Specification of Embedded Systems Can a Compiler perform the ”magic” we look for? 2B1445 Embedded Systems

  5. Compiler • Embedded System Architectures are so complicated that compilers cannot generate optimal solutions! • Even in a single-processor environment the performance are hard to predict due to e.g. • Caches • Pipeline • For an optimal solution understanding of the hardware and fine-tuning in Assembler is still needed! • For multi-processor systems, the situation is naturally much worse! 2B1445 Embedded Systems

  6. What to do? • Possible strategy • Design your system in a high-level language, where a ”good” compiler exists • Check, if the implementation meets the design requirements • If not, improve the critical parts of your design by fine-tuning it in assembler and using the underlying features of the hardware • If all that fails, think of another architecture • Change cache size • Change processor • Investigate a parallel solution 2B1445 Embedded Systems

  7. Polling vs Interrupt • Polling and Interrupt • In polling, the processor has to wait for a resource to get ready and cannot do anything useful while waiting • Interrupt allows the processor to work with other things, but includes an overhead 2B1445 Embedded Systems

  8. Caches • Caches • Caches shorten the memory access time and lead to much better performance • Caches introduce uncertainties, which make it difficult to use all benefits for hard real-time systems, where the requirements have even to be fulfilled in the worst case situation 2B1445 Embedded Systems

  9. Real-Time Operating Systems • Many embedded systems fit in a parallel process model • Real-Time Operating Systems help to design real-time systems which are described as parallel tasks • Interrupts initiate the scheduling of a new task • For periodic tasks scheduling methods with static (RMS) and dynamic (EDF) priority exist • The RTOS has to work for the worst case. Thus the effects of caches cannot be used to their full advantage 2B1445 Embedded Systems

  10. Source Code uses Comm. Primitives Compiled Program uses OS Comm. Primitives Operating System uses Hardware Drivers Mem P1 P2 here Shared Memory Comm. Hardware Abstraction throughLayered Software Model • A layered model allows to abstract from the implementation detail of the underlying levels • The operating system defines services and hides the hardware • Thus the source code does not need to reflect the architecture at all • Challenge: To develop tools at several levels to translate the source into an implementation on the underlying architecture 2B1445 Embedded Systems

  11. Future Work • May result in • Better compilers that allow to design at a higher level • Better operating systems that can use caches efficiently • Power-efficient high-performance processors at a low cost which can be used for all design problems... • ... But until this happens • Know your compiler well • Know your architecture well • Reflect over architecture alternatives • Design your systems in a methodic way 2B1445 Embedded Systems

  12. A look on the next course... • Embedded Systems (2B1445) has looked at • The microprocessor as a component for embedded system design • SoC Architectures will focus on the communication problem in heterogeneous parallel architectures • Bus Architectures with Shared Memory • Hardware Acceleration • Network on Chip Architectures • The component Digital Signal Processor 2B1445 Embedded Systems

More Related