Embedded Software Education: an RTOS-Based Approach

Total Page:16

File Type:pdf, Size:1020Kb

Embedded Software Education: an RTOS-Based Approach Embedded Software Education: An RTOS-based Approach James Archibald Doran Wilde Electrical and Computer Engineering Dept. Electrical and Computer Engineering Dept. Brigham Young University Brigham Young University [email protected] [email protected] ABSTRACT Under the best of circumstances, the creation of functional Embedded computer systems are proliferating, but the com- software for non-trivial applications is demanding. Virtu- plexities of embedded software make it increasingly difficult ally no substantive software programs have been found to be to produce systems that are robust and reliable. These chal- error-free when subjected to careful analysis [1]. Embedded lenges increase as embedded systems are connected to net- developers face all the challenges of conventional software works and relied on to control or monitor physical processes and more. For example, embedded software typically must in critical infrastructure. This paper describes a senior-level interact directly with hardware, it must respond to time- course that exposes students to foundational characteristics critical events in specified time windows, and it often relies of embedded software, such as concurrency, synchronization on concurrency (processes, threads, interrupts) to meet re- and communication. The core of the class is a sequence of sponse time requirements. laboratory assignments in which students design and imple- ment a real-time operating system. Each student-developed Given the formidable task facing firmware developers, it is RTOS has the same API, so all can run the same applica- not surprising that the creation of embedded software is tion code, but internal implementations vary widely. The quantifiably more demanding than conventional software [8], principal challenges that arise in the design and debugging nor is it surprising that the same kinds of mistakes turn of a multi-tasking RTOS tend to be instances of the general up repeatedly during design and development [24]. Given problems that arise in embedded software. In our experi- the importance of embedded systems, there is considerable ence, the activity of creating a working RTOS is effective in interest among researchers and practitioners in improving helping students acquire the knowledge and skills required the efficiency with which embedded software is created. Ef- to be successful embedded software developers. forts focus on a wide range of alternatives, ranging from improved tools and languages to optimized testing method- ologies. These approaches may well improve productivity Keywords and reduce error rates, but it is highly unlikely that they Embedded systems, embedded systems education, real-time will eliminate bugs in embedded software. operating systems, concurrency, real-time computing, soft- ware bugs An undergraduate education that prepares students to be- come embedded system developers should expose students to the fundamental challenges of embedded software, includ- 1. INTRODUCTION ing the use of typical constructs and related problems that Mobile and embedded devices are commonplace in modern too-often accompany their use. As practicing professionals, society, and embedded systems are increasingly deployed to graduates should understand the underlying issues so they support critical infrastructure. Consumers naturally expect can avoid problems in their own designs, and so they know their embedded devices to operate reliably; embedded sys- the most likely causes of behavioral anomalies in their sys- tems that provide essential functionality in an airplane or a tems during development and testing. It is widely accepted municipal water system will be held to the highest standards that students learn best about embedded systems through of dependable operation. Unfortunately, reports of vulnera- their own hands-on experience [10] [13] [18] [14]. bilities or outright failures in critical embedded systems are increasing in frequency and attracting the attention of the Within the dynamically evolving academic disciplines re- general public. lated to embedded systems, there is constant pressure to create new classes and to expand coverage of emerging top- ics, but changes are limited by faculty resources and the number of course that can be packed into an undergradu- This work is based on an earlier work: Preparing Students for ate curriculum [25]. In practice, the well founded desire to Embedded Software Development: An RTOS-based Approach. In expose each student to a broad spectrum of technical topics Workshop on Embedded and Cyber-Physical Systems Education, limits the extent to which they can focus on specializations WESE, © ACM, 2015. within their major discipline. As a result, many students will http://dx.doi.org/10.1145/2832920.2832926. end up working in a sub-discipline in which they have taken Copyright of this extended version retained by the authors. just one advanced undergraduate class. Educators thus fre- quently face this challenge (as we have): if our graduates ley, which they note was shaped by their research projects will go into the workplace as embedded software developers [21] [22]. They describe an advanced graduate class that having taken just one class with that focus, what is the best focuses on RTOS concepts, including scheduling and com- content we can provide in that course to prepare them? munication. Among other assignments in the class, students implement a simple RTOS. This paper describes our answer to that question: a senior- level course in which students work with a partner to design Marwedel describes an introductory course in embedded sys- and implement a real-time operating system (RTOS) or ker- tems for students from multiple disciplines that has been nel from the ground up. In a sequence of labs over the course fine-tuned over a period of almost ten years [19]. Relevant of the semester, students create interrupt service routines, topics covered in the class include scheduling, operating sys- then core kernel routines that perform context switching, tems for embedded systems, and typical properties of an and then other kernel functions that support synchroniza- RTOS. tion and communication between concurrent tasks. A final lab focuses on writing code for a time-critical application Koopman et al. describe embedded system education for un- that uses their RTOS. A central thesis of this paper is that dergraduates at Carnegie Mellon University. Students in the completion of this project sequence gives students crit- their first course develop application software for microcon- ical insight into and experience with the fundamental chal- trollers running an RTOS. In a later class, students more lenges inherent in embedded software. fully explore the capabilities of an RTOS in supporting real- time software. In class labs, students implement an embed- In the remainder of this paper, we discuss a sampling of ded RTOS and then write application code that runs on related work from the literature, we explore the challenges their OS. Topics addressed in the class include concurrency, of embedded software, we describe the RTOS-based course preemption, real-time synchronization and communication. that has been in place in our curriculum for over a decade, and we consider those aspects of the course that are most Sztipanovits et al. describe the embedded curriculum at Van- responsible for its success. derbilt University. They note the difficulty in a mid-sized engineering school of creating new classes for new areas of 2. RELATED WORK specialization. They describe an undergraduate course on real-time systems that emphasizes design, implementation, A survey of the literature on embedded system education and theoretical foundations, and that covers many of the confirms that a wide variety of approaches have been taken, same topics as the course we describe in this paper. depending on the technical nature of the associated degree program, whether the courses are graduate or undergrad- Caspi et al. discuss guidelines for a graduate curriculum on uate, and the mix of other (non-embedded) courses in the embedded software. One area of foundational knowledge curriculum [11]. We focus here on papers that make specific they identify is real-time computing, including design, val- mention of a course that involves the design or use of an idation and operating systems. They observe that classes RTOS, or that includes very similar content. with a real-time focus are among the most commonly taught in existing embedded systems curricula. Chen et al. describe a set of six short courses on embedded systems intended to address deficiencies in first-year grad- Ping describes five main areas of emphasis that embedded uate students [7]. One of those courses focuses on kernel systems curricula should address [20], one of which is op- implementation issues, including context switching, schedul- erating systems for embedded systems. The author states ing, message passing, and interrupt service routines. Stu- that students should master the basic concepts of an RTOS dents study the mechanisms of an embedded operating sys- and know enough to port an existing RTOS to a new target. tem so that they understand the services it provides, but they do not implement an RTOS. The authors note that Wolf and Madsen discuss key factors in education about it requires \sophisticated programming skills to develop a embedded computing [26]. They observe that, outside em- kernel." bedded system classes, students have virtually no experience with raw CPUs, where they are \free from operating system Hsu
Recommended publications
  • Nintendo Wii Software
    Nintendo wii software A previous update, ( U) introduced the ability to transfer your data from one Wii U console to another. You can transfer save data for Wii U software, Mii. The Wii U video game console's built-in software lets you watch movies and have fun right out of the box. BTW, why does it sound like you guys are crying about me installing homebrew software on my Wii console? I am just wondering because it seems a few of you. The Nintendo Wii was introduced in and, since then, over pay for any of this software, which is provided free of charge to everyone. Perform to Popular Chart-Topping Tunes - Sing up to 30 top hits from Season 1; Gleek Out to Never-Before-Seen Clips from the Show – Perform to video. a wiki dedicated to homebrew on the Nintendo Wii. We have 1, articles. Install the Homebrew Channel on your Wii console by following the homebrew setup tutorial. Browse the Homebrew, Wii hardware, Wii software, Development. The Wii was not designed by Nintendo to support homebrew. There is no guarantee that using homebrew software will not harm your Wii. A crazy software issue has come up. It's been around 10 months since the wii u was turned on at all. Now that we have, it boots up fine and you. Thus, we developed a balance assessment software using the Nintendo Wii Balance Board, investigated its reliability and validity, and. In Q1, Nintendo DS software sales were million, up million units Wii software sales reached million units, a million.
    [Show full text]
  • Embedded Linux Systems with the Yocto Project™
    OPEN SOURCE SOFTWARE DEVELOPMENT SERIES Embedded Linux Systems with the Yocto Project" FREE SAMPLE CHAPTER SHARE WITH OTHERS �f, � � � � Embedded Linux Systems with the Yocto ProjectTM This page intentionally left blank Embedded Linux Systems with the Yocto ProjectTM Rudolf J. Streif Boston • Columbus • Indianapolis • New York • San Francisco • Amsterdam • Cape Town Dubai • London • Madrid • Milan • Munich • Paris • Montreal • Toronto • Delhi • Mexico City São Paulo • Sidney • Hong Kong • Seoul • Singapore • Taipei • Tokyo Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. For information about buying this title in bulk quantities, or for special sales opportunities (which may include electronic versions; custom cover designs; and content particular to your business, training goals, marketing focus, or branding interests), please contact our corporate sales depart- ment at [email protected] or (800) 382-3419. For government sales inquiries, please contact [email protected]. For questions about sales outside the U.S., please contact [email protected]. Visit us on the Web: informit.com Cataloging-in-Publication Data is on file with the Library of Congress.
    [Show full text]
  • Design Languages for Embedded Systems
    Design Languages for Embedded Systems Stephen A. Edwards Columbia University, New York [email protected] May, 2003 Abstract ward hardware simulation. VHDL’s primitive are assign- ments such as a = b + c or procedural code. Verilog adds Embedded systems are application-specific computers that transistor and logic gate primitives, and allows new ones to interact with the physical world. Each has a diverse set be defined with truth tables. of tasks to perform, and although a very flexible language might be able to handle all of them, instead a variety of Both languages allow concurrent processes to be de- problem-domain-specific languages have evolved that are scribed procedurally. Such processes sleep until awak- easier to write, analyze, and compile. ened by an event that causes them to run, read and write variables, and suspend. Processes may wait for a pe- This paper surveys some of the more important lan- riod of time (e.g., #10 in Verilog, wait for 10ns in guages, introducing their central ideas quickly without go- VHDL), a value change (@(a or b), wait on a,b), ing into detail. A small example of each is included. or an event (@(posedge clk), wait on clk un- 1 Introduction til clk='1'). An embedded system is a computer masquerading as a non- VHDL communication is more disciplined and flexible. computer that must perform a small set of tasks cheaply and Verilog communicates through wires or regs: shared mem- efficiently. A typical system might have communication, ory locations that can cause race conditions. VHDL’s sig- signal processing, and user interface tasks to perform.
    [Show full text]
  • Sr. Firmware - Embedded Software Engineer
    SR. FIRMWARE - EMBEDDED SOFTWARE ENGINEER Atel USA is a leading provider of high-performance, small form-factor tracking systems for the vehicle recovery, fleet, heavy trucks, and asset tracking industries. Our team has years of experience in developing complex wireless and communications systems. We have shipped several millions of vehicle tracking devices operating on all major cellular networks. We are seeking an enthusiastic embedded software engineer to be a key team member in the design, implementation, and verification of our asset tracking devices and sensory accessories. The Sr. Firmware Engineer will become an integral part of our company and will work as part of a small, multi-disciplinary development team to design, construct and deliver software/firmware for our current and next generation products. Primary Responsibilities: • Work independently on project tasks as well as work as a team member of a larger project team. • Collaborate with hardware/system design engineers to define the product feature set and work within a product development team to deliver firmware that meets or exceeds product requirements. • Engage with customers and product managers to define requirements, develop software architecture, and plan development in dynamic, evolving customer driven environment. • Deliver innovative solutions from concept to prototype to production. • Conduct/participate in engineering reviews to provide technical input on product designs and quality. • Conduct software unit tests to exercise implemented functionality. • Document software designs. • Troubleshoot and remove defects from production software. • Communicate and interact with team and customers to clearly set expectations, share technical details, resolve issues, and report progress. • Participate in brainstorms and otherwise contribute outside your area of expertise.
    [Show full text]
  • Sr. Embedded Software/ Firmware Engineer This Position Is Located at the Corporate Headquarters in Henderson, Nevada
    Sr. Embedded Software/ Firmware Engineer This position is located at the Corporate Headquarters in Henderson, Nevada VadaTech, Inc. is seeking experienced candidates for Senior Embedded Software/Firmware Engineer. Primary Responsibilities: • Responsible for the focus on BIOS and board bring up • Responsible for the coordinating and prioritizing application modifications and bug fixes • Responsible for working with the customer support team to troubleshoot and resolve production issues • Responsible for the support, maintenance and documentation of software functionality • Responsible for Contributing to the development of internal tools to streamline the engineering and build and release processes • Responsible for the production of functional specifications and design documents Desired Skills and Experience • Bachelor’s degree in computer science or related field; master’s degree preferred • 8+ years of related work experience • Fluency in C programming required • Experience with Embedded Bootloader/OS porting required • Experience with U-Boot/Embedded Linux porting and PC BIOS maintenance preferred • Experience with new/untested hardware board bring-up required • Demonstrated ability to read hardware schematics and use lab instruments such as oscilloscopes, multimeters and JTAG probes to resolve problems required • Must be knowledgeable in low-level board-support software/hardware interfacing for DDR3 memory, local bus timings, Ethernet PHYs, NOR/NAND flash, I2C/SPI, and others • Experience with diverse CPU types such as PowerPC/PowerQUICC/QorIQ,
    [Show full text]
  • Embedded Linux Systems
    Dpto Sistemas Electrónicos y de Control Universidad Politécnica de Madrid Embedded Linux Systems Using Buildroot for building Embedded Linux Systems with the Raspberry-PI V1.2 Mariano Ruiz 2014 EUIT Telecomunicación Dpto. Sistemas Electrónicos y de C o n t r o l Page 1 of 41 Page 2 of 41 Table of contents 1 SCOPE ........................................................................................................................................ 6 1.1 Document Overview .............................................................................................................. 6 1.2 Acronyms .............................................................................................................................. 6 2 REFERENCED DOCUMENTS ......................................................................................................... 7 2.1 References ............................................................................................................................. 7 3 LAB1: BUILDING LINUX USING BUILDROOT ................................................................................. 8 3.1 Elements needed for the execution of these LABS. .................................................................. 8 3.2 Starting the VMware .............................................................................................................. 8 3.3 Configuring Buildroot. .......................................................................................................... 11 3.4 Compiling buildroot. ...........................................................................................................
    [Show full text]
  • 1.1 Purpose of Embedded System 1.2 Host and Target Machine 1.2.1
    e-PG Pathshala Subject : Computer Science Paper: Embedded System Module: Embedded Software Development Tools Module No: CS/ES/36 Quadrant 1 – e-text In this module, we will discuss about the host and target machine, Embedded Software development process and Embedded tools. 1.1 Purpose of Embedded System An embedded system is a special-purpose system in which the computer is completely encapsulated by the device it controls. Each embedded system has unique characteristics. The components and functions of hardware and software can be different for each system. Nowadays, embedded software is used in all the electronic devices such as watches, cellular phones etc. This embedded software is similar to general programming. But the embedded hardware is unique. The method of communication between interfaces can vary from processor to processor. It leads to more complexity of software. Engineers need to be aware of the software developing process and tools. There are a lot of things that software development tools can do automatically when the target platform is well defined. This automation is possible because the tools can exploit features of the hardware and operating system on which your program will execute. Embedded software development tools can rarely make assumptions about the target platform. Hence the user has to provide some explicit instructions of the system to the tools. Figure 1.1 shows how an embedded system is developed using a host and a target machine. 1.2 Host and Target machine Figure 1.1 Embedded system using host and target machine 1.2.1 Performance of Host machine The application program developed runs on the host computer.
    [Show full text]
  • Asurvey of Embedded Software Profiling Methodologies
    International Journal of Embedded Systems and Applications (IJESA) Vol.1, No.2, December 2011 A SURVEY OF EMBEDDED SOFTWARE PROFILING METHODOLOGIES Rajendra Patel1 and Arvind Rajawat 2 1,2 Department of Electronics and Communication Engineering, Maulana Azad National Institute of Technology, Bhopal, India 1 [email protected] [email protected] 2 ABSTRACT Embedded Systems combine one or more processor cores with dedicated logic running on an ASIC or FPGA to meet design goals at reasonable cost. It is achieved by profiling the application with variety of aspects like performance, memory usage, cache hit versus cache miss, energy consumption, etc. Out of these, performance estimation is more important than others. With ever increasing system complexities, it becomes quite necessary to carry out performance estimation of embedded software implemented in a particular processor for fast design space exploration. Such profiled data also guides the designer how to partition the system for Hardware (HW) and Software (SW) environments. In this paper, we propose a classification for currently available Embedded Software Profiling Tools, and we present different academic and industrial approaches in this context. Based on these observations, it will be easy to identify such common principles and needs which are required for a true Software Profiling Tool for a particular application. KEYWORDS Profiling, Embedded, Software, Performance, Methodology 1. INTRODUCTION In the design of embedded systems, design space exploration is performed to satisfy the application requirements. This can be achieved either by different architectural choices or by appropriate task partitioning. At the end the synthesis process generates the final solution with proper combination of Software, Hardware and Communication Structures.
    [Show full text]
  • Embedded Software Development Process and Tools: Lesson-1 Introduction to Embedded Software Development Process and Tools
    Embedded Software development Process and Tools: Lesson-1 Introduction to Embedded Software Development Process and Tools 2015 Chapter-14L01: "Embedded Software Development Process and 1 Tools, Publs.: McGraw-Hill Education 1. Development Process and Hardware─ Software 2015 Chapter-14L01: "Embedded Software Development Process and 2 Tools, Publs.: McGraw-Hill Education Cost of developing a final targeted system • Small processor cost • Larger time frame needed than the hardware circuit design • High development cost for final targeted system 2015 Chapter-14L01: "Embedded Software Development Process and 3 Tools, Publs.: McGraw-Hill Education Development Process • Edit-test-debug cycles • Fixed Processor and hardware parts once chosen • Application software codes perfected by a number of runs and tests. 2015 Chapter-14L01: "Embedded Software Development Process and 4 Tools, Publs.: McGraw-Hill Education Development process of an embedded system 2015 Chapter-14L01: "Embedded Software Development Process and 5 Tools, Publs.: McGraw-Hill Education Edit-Test-Debug Cycle implementation phase of the development process 2015 Chapter-14L01: "Embedded Software Development Process and 6 Tools, Publs.: McGraw-Hill Education 2. Software Tools 2015 Chapter-14L01: "Embedded Software Development Process and 7 Tools, Publs.: McGraw-Hill Education Software Tools • Software Development Lit (SDK) • Source-code Engineering Software • RTOS • Integrated Development Environment • Prototyper • Editor • Interpreter 2015 Chapter-14L01: "Embedded Software Development
    [Show full text]
  • Comparing Embedded Linux Build Systems and Distros
    Comparing embedded Linux build systems and distros Drew Moseley Solutions Architect Mender.io Session overview ● Review of embedded Linux development challenges. ● Define build system and criteria. ● Discuss a few popular options. ● Give me an opportunity to learn about some of the other tools. Goal: Help new embedded Linux developers get started About me Drew Moseley Mender.io ○ 10 years in Embedded Linux/Yocto development. ○ Over-the-air updater for Embedded Linux ○ Longer than that in general Embedded Software. ○ Open source (Apache License, v2) ○ Project Lead and Solutions Architect. ○ Dual A/B rootfs layout (client) [email protected] ○ Remote deployment management (server) https://twitter.com/drewmoseley https://www.linkedin.com/in/drewmoseley/ ○ Under active development https://twitter.com/mender_io Challenges for Embedded Linux Developers Hardware variety Storage Media Software may be maintained in forks Cross development Initial device provisioning Simple Makefiles don't cut it (anymore) Facts: ● These systems are huge ● Dependency Hell is a thing ● Builds take a long time ● Builds take a lot of resources ● Embedded applications require significant customization ● Developers need to modify from defaults Build System Defined _Is_ _Is Not_ ● Mechanism to specify and build ● An IDE ○ Define hardware/BSP ● A Distribution components ● A deployment and provisioning ○ Integrate user-space tool applications; including custom ● An out-of-the-box solution code ● Need reproducibility ● Must support multiple developers ● Allow for parallel
    [Show full text]
  • Programming Embedded Systems, Second Edition with C and GNU Development Tools
    Programming Embedded Systems Second Edition Programming Embedded Systems, Second Edition with C and GNU Development Tools Foreword If you mention the word embedded to most people, they'll assume you're talking about reporters in a war zone. Few dictionaries—including the canonical Oxford English Dictionary—link embedded to computer systems. Yet embedded systems underlie nearly all of the electronic devices used today, from cell phones to garage door openers to medical instruments. By now, it's nearly impossible to build anything electronic without adding at least a small microprocessor and associated software. Vendors produce some nine billion microprocessors every year. Perhaps 100 or 150 million of those go into PCs. That's only about one percent of the units shipped. The other 99 percent go into embedded systems; clearly, this stealth business represents the very fabric of our highly technological society. And use of these technologies will only increase. Solutions to looming environmental problems will surely rest on the smarter use of resources enabled by embedded systems. One only has to look at the network of 32-bit processors in Toyota's hybrid Prius to get a glimpse of the future. Page 1 Programming Embedded Systems Second Edition Though prognostications are difficult, it is absolutely clear that consumers will continue to demand ever- brainier products requiring more microprocessors and huge increases in the corresponding software. Estimates suggest that the firmware content of most products doubles every 10 to 24 months. While the demand for more code is increasing, our productivity rates creep up only slowly. So it's also clear that the industry will need more embedded systems people in order to meet the demand.
    [Show full text]
  • Chapter 1 Concepts for Developing Portable Firmware
    Jacob Beningo Chapter 1 Concepts for Developing Portable Firmware “A good scientist is a person with original ideas. A good engineer is a per- son who makes a design that works with as few original ideas as possible. “ – Freeman Dyson Why Code Reuse Matters Over the past several decades, embedded systems have steadily in- creased in complexity. The internet’s birth has only accelerated the process as our society has been in a race to connect nearly every device imaginable. Systems that were once simple and stand-alone must now connect through the internet in a secure and fail-safe manner in order to stream critical in- formation up into the cloud. Complexity and features are increasing at an exponential rate with each device generation forcing engineers to reevalu- ate how to successfully develop embedded software within the allotted timeframe and budget. The increased demand for product features along with the need to connect systems to the internet has dramatically increased the amount of 3 Confidential – ©2016 Jacob Beningo, All Rights Reserved, DRAFT A08 Developing Reusable Firmware software that needs to be developed to launch a product. While software complexity and features have been increasing, the time available to devel- op a product has for the most part remained constant with a negligible increase in development time (2 weeks in 5 years) as can be seen in Figure 1. In order to meet project timelines, developers are forced to either pur- chase commercial off-the-shelf (COTS) software that can decrease their development time or they need to reuse as much code as possible from previous projects.
    [Show full text]