1 / 23

CS4101 嵌入式系統概論 Design and Development

CS4101 嵌入式系統概論 Design and Development 金仲達教授 國立清華大學資訊工程學系 9/16/2010 Slides from Computers as Components: Principles of Embedded Computing System Design , Wayne Wolf, Morgan Kaufman; An Embedded Software Primer , David E. Simon, Addison Wesley Now, You Have Decided to Save the Earth!

albert
Download Presentation

CS4101 嵌入式系統概論 Design and Development

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. CS4101 嵌入式系統概論Design and Development 金仲達教授 國立清華大學資訊工程學系 9/16/2010 Slides from Computers as Components: Principles of Embedded Computing System Design, Wayne Wolf, Morgan Kaufman;An Embedded Software Primer, David E. Simon, Addison Wesley

  2. Now, You Have Decided to Save the Earth! But how?

  3. After Extensive Study, You Found Fact 1: If every elevator in the world moves one less floor, the annual world CO2 emission will be reduced by X% Fact 2: If a person climbs one floor, he or she will burn Y calories What a business to help exercises & save earth!

  4. Your Product Idea • To develop a device that can record, for each day, the number of floors that the user has climbed and the number of floors that the user has taken the elevator • From this number, we can then calculate the amount of CO2 saved and calories burned • Let us call this device stair counter How to start from here?

  5. Typical Design Flow requirements Top-down design specification architecture Bottom-up design Real design often iterative component development system integration

  6. requirements specification architecture component development system integration Requirements • Plain language description of what the user wants and expects to get • e.g. to develop a device that can record, for each day, the number of floors that the user has climbed and the number of floors that the user has taken the elevator • Vision the end product used by the user • May be developed in several ways: • talking directly to customers • talking to marketing representatives • providing prototypes to users for comment

  7. Requirements • Often need to know target customers and business model • Stair counter as an add-on of cell phone • Stair counter as a consumer product • Stair counter as a gift • …

  8. Requirements • Functional requirements: Output as a function of input; internals as a black box • Show number of stairs climbed and amount of calories burned • Show number of floors by elevator and amount of CO2 saved • Do not count in other cases • Non-functional requirements: • Performance, reliability, etc. • Size, weight, etc. • Power consumption • Cost • … Describe “WHAT”, not “HOW”

  9. Requirements Form

  10. requirements specification architecture component development system integration Specification • More precise, usually quantitative description of the system: • Should not imply a particular architecture • List assumptions • e.g., update screen 0.25 sec after eachstep, error rate < 95%, cost < $300 • May include functional and non-functional elements • May be executable or may be in mathematical form for proofs • e.g. UML (Unified Modeling Language)

  11. requirements specification architecture component development system integration Architecture Design • What major components satisfy the specification?  HOW • Need to know what are available • Hardware components: • CPUs, peripherals, etc. • e.g. 8051 CPU, 3-axis accelerometer • Software components: • Major programs and their operations • e.g. no OS, accelerometer driver, LCD driver • Must take into account functional and non-functional specifications

  12. Design Considerations • Environment which the embedded system is in • External and internal stimulus sources that interact with the embedded system  I/O • Actions and events caused by stimulus • Elements of the embedded system that could be affected by the stimulus • Desired system responses to the stimulus, which reflects one or more system requirements  algorithm/workflow • How the system responses can be measures

  13. requirements specification architecture component development system integration Component Development • Actual implementation of individualhardware and software components • Must spend time architecting the system before you start coding • Some components are ready-made, some can be modified from existing designs, others are to be designed from scratch • e.g. 8051 CPU, 3-axis accelerometer • Good surveys help

  14. requirements specification architecture component development system integration System Integration • Put together the components • Many bugs appear only at this stage • Require good interface definition fromthe start • Have a plan for integrating components to uncover bugs quickly, test as much functionality as early as possible

  15. requirements specification architecture component development system integration System Development • Now that you have better idea of the requirements, specifications, and architecture of the stair counter • How to proceed to develop the components and integrate the system? But, • Real hardware? Programming environment?

  16. Development Environment • Host: a computer running programming tools for development • Target: the HW on which code will run • After program is written, compiled, assembled and linked, it is transferred to the target 8051 X86 Target system Host system

  17. What If Real HW Not Available? • Development board: • Before real hardware is built, software can be developed and tested using development boards • Development boards usually have the same CPU as the end product and provide many IO peripherals for the developed software to useas if it were running on thereal end product • Platform-based design

  18. Platform-Based Design • Platform:一個已經有中央微處理器、記憶體、匯流排、即時作業系統與基本周邊設備的開發環境 • 設計者可針對新的產品需求來加入額外的硬體模組,或是重新燒錄PLD、修改嵌入式應用軟體等 • Common tools for program development • Integrated Development Environment (IDE):整合的圖形操作介面,以方便軟體開發,包括程式編輯、編譯、鏈結、偵錯、下載等 • Toolchain: cross compiler, linker, loader, … • OS and related libraries and packages

  19. Cross Compiler • Runs on host but generates code for target • Target usually have different architecture from host. Hence compiler on host has to produce binary instructions that will be understood by target

  20. Development Process • Process for creating instructions that are built on host but meant for the target • Tools are compatible with each other  a toolchain • Binutils: as, ld • Glibc:C runtime Lib • GCC:C/C++ compiler

  21. Linker/Locators • For computers: • Linker: creates an image file to be run on host • Loader: loads image file into memory during run-time • For embedded systems: • Locater: creates a file, containing binary image or other format, that will be copied onto target, which run on its own (not through loader) • It needs exact addresses beforehand • Certain parts of program need in ROM and some in RAM • Normally done by dividing program in segments • Locator needs to be told where in memory to place segments

  22. Getting Software into Target • PROM Programmers • Classic way – use output file to build a ROM or PROM (if software still needs some changes) • ROM Emulators • Replace (emulate) ROM in the target system • Look like a ROM with a serial port or network connection to talk to host • In-Circuit Emulators (ICE) • Replace processor with an emulator for debugging • Use overlay-memory to get software to target

  23. Getting Software into Target • Monitors • Programs on target ROM that know how to load new programs to the system • Store user software sent from host through a communications link (serial) to target RAM and run it • Might also perform some locator and debugger functions (setting breakpoints, checking register values) etc. also

More Related