1.3 THE EMBEDDED SYSTEM DESIGN PROCESS ¥ Embedded system design process has two objectives. * Introduction to the various steps in embedded system design before developed in detaited design + Designmethodology Top-down design design CrstiionIntroduction to: Embedded System Design 115 ¥ Adesignmethodology is important for following reasons. Oo Design toensure mee un lg elopcomputer-aided designtools. ~~ 5 Vana Ei citeans0 cotinine + There are five major levels of embedded system design process. Before going todesign a system the designers rieed to fulfil tiie néeds-to design such a system. They are J, REQUIREMENTS: _ Fits the désigner must gather an informal description from th customers itis wnas requirements. r: > Sccond, then the designer must know what we are designing and then o refine the requirement nto specification and to begin to designing the system athitecure. Requirements may be functional or non-finctional, we must of course capture the basic functions of the embedded system, but functional description is often. notsufficent. ¥ Typical non-functional requirements include: i. Performance: Thespeed of the system is often a major consideration both for the usability of the system and for its ultimate cost. ¥ Performance may be a combination of soft performance metries such as approximate time to perform a user-level function and hatd deadlines by which particular operation must be completed. | ii. Cost: Thetarget cost or purchase price for the systems almost: beeen Cost typically has two major components: + Manufacturing cost includes the cost of components and assembly, t + Non recurring engineering (NRE) costs inchude the personand other costs. of designing the system. aiaEmbedded and Réal-Time Systems i. Physical size and weight: The; physical: aspects of the final system can vary greatly: depending upon the” application. ‘An industrial control system for an assembly line may be designed tofit into; stanidard-size rack with no strict limitations on weight. i A bbandbeld device typically has ight requirements on both size and wight that can tipple through the entire system design. Power consumption: Power, deem igo interpre ree oc aga nother applications as well. Power can be specified in the requirements stage in terms of battery life. ¥ Now wewill list some requirements form collected from the user at the start of the project. a. Name“ b. Purpose~ c. Inputs ~ d.. Outputs” ¢. Functions” £ Performarice g Manufacturing cost f h Power Physical size andweight 2. SPECIFICATION: v ‘The specification is more precise it serves asthe contract between the customer and the architects. It must be carefully written so that it accurately refiects the. customér’s requirements. Specification is essential to creating working systems witha minimum of designer effort. a 4 ‘Iniroduiction to Embedded Systein Design a Y _ Specification will guide the designers what to Bild when it build, > ° Specification Should be understandable ériough so that someone can verify that it meets system requirements'and overall expectations of the customer. (3, ARCHITECTURE DESIGN: - v specification doesnot say how the system does thfings, only what the system, does. Y_.. Thearchitectureisaplan forthe overall structure of the system that will be used we later to desigti the components that make up the architecture. The creation of the architecture isthe first phase of what many designers think of as design. Bene 1/ Tne architecture inthe form of botk diagram that shows major operations and data flows among them. 7 ¥ This block diagram is still quite abstract -we have not yet specified which operations will be performed by software running on a CPU, what will be done by special-purpose hardware, and so on. Y Architectural descriptions must be designed to satisfy both functional and non- ¥ Not only must all the required functions be present, but we must meet cost, speed, power, and other non-functional constraints. Y — Starting out witha system architecture and refining that to hardware and software architectures is one good way to ensure that we meet all specifications. ~ ‘We can concentrate on the functional elements in the system block. diagram, and then consider the non-fantional constraints when creating the hardware and software architectures. 4. DESIGNING HARDWARE AND SOFTWARE COMPONENTS: y : ; The component design effort builds those components in conformance to the architecture and specification. « ‘The components will in general include both hardware like FPGAs, boards, and118 Embedded. and Real Time Systems ¥ Some of the comporients will be ready-made. . ¥ The CPU, forexample, willbe a standard component in almost all cases, as well asmemory chips and many other components. 5, SYSTEM INTEGRATION: _ 7 Only after the components are built do.we have the satisfaction of putting them * together and seeing a working system. “This phase usually consists ofa lot more than just plugging everything together andstandingback. ~ ° y _© Bigs are typically found during system integration, and good planning can help usfind the bugs quickly. ¥ Bybuilding up the system in phases and running property chosen tests, we can often find bugs more easily. ‘System integration is difficult because it usually uncdvers problems. _- tis often hard to observe the system in sufficient detail to determine exactly whats wrong. ¥_Alfd debugging facilities for embedded systems are usually much more limited tan what you would find on desktop systems. 1.3.1 Example: Embedded System Design Process: GPS Moving Map “Now consider one example as GPS moving map and disciss about embedded system design process. Requirements analysis ofa GPS moving map: “ Themoving mapis ahandheld device that displays for the user a map of the terrain around the user's current position, the map display changes as the user andt the map device change position. % Themoving:map otainsits postion from the GS, satellite-based navigaion system ~~ ‘The moving map display might look something like the following functions.Introduction to Embedded System Design ‘ 119 Functionality: This systemis designed for highway driving and similar uses, ‘ot nautical or aviation iss thal rejire more specialized databases ane functions. The system should show mor roasand thee landmarks available in standard topographic databases. s “User interface: The sercashouldhave at least 400° 60K device should be controlled by no more than three buttons. Amen system should Pop up on the screen when buttons are pressed to allow the user to make selections tocontrol the system. Y Performance: The map should scroll smoothly. Upon power-up, a display should take no more than one second to appéar, and the system should be able to verify its position and display the current map within 15 s, i‘ Y Cost: The selling cost (street price) of the unit should be no more than $100. a Poysicesie «and weight: The device should fit comforiably in the palm of the ee ee eodand =e v Poe omni srt rd _ batteries. Sa = iB Based on this discussion, let's write a requirements chart for our moving map system: Name GPS moving map Purpose Consumer-grade moving map for drivinguse Inputs Power button, two control buttons Outputs Backlit LCD display 400 x 600 = Functions Uses S-receiver GPS system; three user-selectable resolutions; always displays current latitude and longi Performance Updates screen within 0.25 seconds upon movement’ | Manufacturing cost x Power 100mW a! Embedded and Real Timesystems Figurel.3 Block diagram for. the moving map A specification of the GPS systein would include several components: * Data received from the GPS satellite constellation. + Map data. +. Useriinterface. * - Operations that must be performed to satisfy ctistomer requests. 2pkgrouned sets required to keep the system ring, sichas operating the GPS receiver, ‘The GPS is a good example of a specialized component in almost that will nonetheless be predesigned, standard component. ee ft dene oles one good example is that topographic database. Display GPS receiver Figure 1.4a HardwareIntroduction to. Embedded System Design [> Pixels Figure 1.46 Sofoware Figure 14 Hardware and Software Architecture of the Moving Map 121