Nuttx RTOS Beginnings

Total Page:16

File Type:pdf, Size:1020Kb

Nuttx RTOS Beginnings NuttX RTOS Beginnings Gregory Nutt AboutAboutAbout MeMeMe Math/Physics Digital Signal Processing Math Neuro- Computer Science 1970 science Academia 1980 First mult-tasking, pre-emptive RTOS, 1982 Cooperative Schedulers Hewlett Packard Military Avionics Cooperative Schedulers Commercial Electronics 1990 LaserJet POSIX RTOS, 1996 Costa Rica LaserJet Firmware Architect Open Source 2000 Ridgerun.com NuttX Release to Open Source, 2007 NX-Engineering, SA GraduateGraduateGraduate SchoolSchoolSchool DaysDaysDays LINC PDP-8/i LINC-8 PDP-8/e TRS-80 Model 1 HardwareHardwareHardware ofofof FirstFirstFirst RTOSRTOSRTOS InterruptInterruptInterrupt DrivenDrivenDriven ––– OSOSOS #1#1#1 (Bare(Bare(Bare Metal)Metal)Metal) NoNo OSOS:: ExtensiveExtensive interruptinterrupt processing,processing, prioritizedprioritized Response Latency interruptsinterrupts and,and, maybe,maybe, aa mainmain loop. Single Interrupt Handler loop. Deterministic?Deterministic? NoNo MeetMeet Deadlines?Deadlines? MaybeMaybe High Priority Medium Priority Low Priority Response Latency Problems:Problems: Stacked,Stacked, CanCan loselose interrupts.interrupts. NoNo waiting,waiting, allall runrun toto completion.completion. MainMainMain LoopLoopLoop ––– OSOSOS #1#1#1 (Cont'd)(Cont'd)(Cont'd) Task A Task G Task B Task F Main, Background Task C Loop Task E Non-deterministic! ● Round-Robin ● Non-premptive ● Cooperative Scheduling Task D ● State machines ● Ad hoc strategies Non-deterministic! RealRealRealReal TimeTimeTimeTime ======== DeterministicDeterministicDeterministicDeterministic Response Latency Stimulus Response Deadline RealReal timetime doesdoes notnot meanmean “fast”“fast” RealReal timetime systemssystems havehave DeadlinesDeadlines MainMainMain LoopLoopLoop withwithwith PriorityPriorityPriority QueueQueueQueue ––– OSOSOS #2#2#2 Interrupt BriefBrief interruptinterrupt processing,processing, onlyonly queuesqueues workwork Lowest Prio Main, Background Loop Highest Prio StillStill Non-deterministic!Non-deterministic! HighHigh prioritypriority workwork stillstill hashas toto waitwait forfor workwork inin progress.progress. TaskTask X X MainMainMain LoopLoopLoop withwithwith CooperativeCooperativeCooperative Scheduler–Scheduler–Scheduler– OSOSOS #3#3#3 Task X ●● Non-premptiveNon-premptive switch (state) ● { ● CooperativeCooperative SchedulingScheduling case state A: Start event processing; state = state B; ●● DivideDivide eventevent processingprocessing upup intointo piecespieces Reschedule; ●● ManageManage withwith aa statestate machinemachine Break; ●● RescheduleReschedule toto allowallow higherhigher prioritypriority taskstasks ●● OtherOther adad hochoc strategiesstrategies Case state B: Continue event processing; State = state C; Reschedule; Break; Case state C: Finish event processing; State = state X; Break; Case state X: Break; StillStill Non-deterministic!Non-deterministic! } HighHigh prioritypriority workwork stillstill hashas toto waitwait forfor workwork inin progress.progress. ForegroundForegroundForeground /// BackgoundBackgoundBackgound MainMainMain LoopsLoopsLoops ––– OSOSOS #4#4#4 ContextContext Switch!Switch! Foreground Background Main Loop Main Loop ParitiallyParitially DeterministicDeterministic Pre-emptivePre-emptivePre-emptive OSOSOS ––– OSOSOS #5#5#5 Task Start TheThe DECDEC connectionconnection Pending (NuttX) FullyFully pre-emptiblepre-emptible ContextContext switch:switch: Ready-to-run ThinkThink setjmp/longjmpsetjmp/longjmp onon steriodssteriods TaskTask ControlControl BlockBlock (TCB)(TCB) Blocked StatesStates representedrepresented byby listslists ofof TCBsTCBs HighestHighest PriorityPriority WaitWait forfor signal,signal, Running Ready-to-runReady-to-run tasktask semaphore,semaphore, isis RunningRunning messagemessage queue,queue, pagepage fill,fill, stopped,stopped, etc.etc. RTOSRTOSRTOSRTOS InterruptInterruptInterruptInterrupt ProcessingProcessingProcessingProcessing Stimulus Response Interrupt RTOSRTOS Scheduler Scheduler Handler ReassessReassess next next ready-to-runready-to-run thread thread Signals thread via IPC Resumes thread if highest priority, ready-to-run Task Task Suspended, Suspended, Waiting for Task awakened, Waiting for event Processes interrupt related event Next event RTOSRTOSRTOSRTOS InterruptsInterruptsInterruptsInterrupts NoNo OSOS way:way: ExtensiveExtensive interruptinterrupt processing,processing, prioritizedprioritized interruptsinterrupts and,and, maybe,maybe, aa mainmain looploop.. Interrupt Interrupt Interrupt Interrupt Interrupt Signal Task C SignalSignal Task Task A A Signal Task C SignalSignal Task Task E E SignalSignal Task Task B B SignalSignal Task Task D D RTOSRTOS way:way: MinimalMinimal workwork performedperformed inin interruptinterrupt handlershandlers InterruptInterrupt handlershandlers onlyonly signalsignal eventsevents toto taskstasks RTOSRTOS schedulerscheduler managesmanages real-timereal-time behaviorbehavior PrioritizedPrioritized interruptsinterrupts replacedreplaced withwith prioritizedprioritized taskstasks NoNo benefitbenefit inin nestingnesting interruptsinterrupts (usually)(usually) SMPSMPSMP Pending Ready-to-run nn HighestHighest PriorityPriority Blocked Ready-to-runReady-to-run taskstasks areare RunningRunning SpinlocksSpinlocks AffinityAffinity RunningRunningRunning CPU 1 Running CPU CPU2 3 AssignedAssigned TaskTask ListList (not(not shown)shown) CPU 0 CPU 1 CPU 2 CPU n RateRateRate MontonicMontonicMontonic SchedulingSchedulingScheduling CanCan achieveachieve Real-TimeReal-Time behaviorbehavior underunder certaincertain circumstancescircumstances ● ● StrictStrict prioritypriority schedulingscheduling ● Threads with shorter periods/ ● Static priorities Threads with shorter periods/ Static priorities ● deadlinesdeadlines areare assignedassigned thethe ● PrioritiesPriorities assignedassigned accordingaccording toto highesthighest priorities.priorities. ● ● RateRate MonotonicMonotonic conventionsconventions And this unrealistic assumption: ● No resource sharing ● No waiting for resources ● No semaphores or locks ● No critical sections ● No disabling pre-emption ● No disabling interrupts WhyWhyWhy POSIX?POSIX?POSIX? WhyWhy not...not... VersusVersus customcustom adad hochoc OSOS interfaceinterface POSIXPOSIX devicedevice modelmodel vsvs HALHAL LikeLike simplersimpler FreeRTOS,FreeRTOS, ChibiOS,ChibiOS, Zephyr,Zephyr, mbed,mbed, RIOT,RIOT, etc.etc. AtAt thisthis pointpoint POSIXPOSIX isis thethe NuttXNuttX identityidentity PortabilityPortability LinuxLinux compatibilitycompatibility ComplexComplex buildbuild models:models: PROTECTEDPROTECTED andand KERNELKERNEL buildsbuilds WorkWork Queues Queues Interrupt Handler “Top Half” Worker Prioritized Work Thread Defer more Queue “Bottom half” extended interrupt processing to Worker Thread PriorityPriority Qeue Qeue Non-premptiveNon-premptive Non-deterministic! VeryVery high high priority priority InappropriateInappropriate for for extended processing UseUse withwith care!care! MultipleMultipleMultipleMultiple WorkWorkWorkWork QueuesQueuesQueuesQueues SingleSingle highhigh prioritypriority workwork queuequeue High Priority High Priority IntendedIntended forfor interruptinterrupt “bottom“bottom half”half” WorkWork QueueQueue ShouldShould bebe highesthighest prioritypriority P R I O R MultipleMultiple Multiple low priority work queues I Multiple low priority work queues Low Priority Low Priority Support priority inheritance T WorkHigh Queues Priority Support priority inheritance WorkHigh Queues Priority Y WorkWork High HighQueueQueue PriorityPriority UseUse toto implementimplement asynchronousasynchronous WorkWork QueueQueue I/OI/O (AIO)(AIO) ThreadThread poolpool.
Recommended publications
  • Comparison of Contemporary Real Time Operating Systems
    ISSN (Online) 2278-1021 IJARCCE ISSN (Print) 2319 5940 International Journal of Advanced Research in Computer and Communication Engineering Vol. 4, Issue 11, November 2015 Comparison of Contemporary Real Time Operating Systems Mr. Sagar Jape1, Mr. Mihir Kulkarni2, Prof.Dipti Pawade3 Student, Bachelors of Engineering, Department of Information Technology, K J Somaiya College of Engineering, Mumbai1,2 Assistant Professor, Department of Information Technology, K J Somaiya College of Engineering, Mumbai3 Abstract: With the advancement in embedded area, importance of real time operating system (RTOS) has been increased to greater extent. Now days for every embedded application low latency, efficient memory utilization and effective scheduling techniques are the basic requirements. Thus in this paper we have attempted to compare some of the real time operating systems. The systems (viz. VxWorks, QNX, Ecos, RTLinux, Windows CE and FreeRTOS) have been selected according to the highest user base criterion. We enlist the peculiar features of the systems with respect to the parameters like scheduling policies, licensing, memory management techniques, etc. and further, compare the selected systems over these parameters. Our effort to formulate the often confused, complex and contradictory pieces of information on contemporary RTOSs into simple, analytical organized structure will provide decisive insights to the reader on the selection process of an RTOS as per his requirements. Keywords:RTOS, VxWorks, QNX, eCOS, RTLinux,Windows CE, FreeRTOS I. INTRODUCTION An operating system (OS) is a set of software that handles designed known as Real Time Operating System (RTOS). computer hardware. Basically it acts as an interface The motive behind RTOS development is to process data between user program and computer hardware.
    [Show full text]
  • AMNESIA 33: How TCP/IP Stacks Breed Critical Vulnerabilities in Iot
    AMNESIA:33 | RESEARCH REPORT How TCP/IP Stacks Breed Critical Vulnerabilities in IoT, OT and IT Devices Published by Forescout Research Labs Written by Daniel dos Santos, Stanislav Dashevskyi, Jos Wetzels and Amine Amri RESEARCH REPORT | AMNESIA:33 Contents 1. Executive summary 4 2. About Project Memoria 5 3. AMNESIA:33 – a security analysis of open source TCP/IP stacks 7 3.1. Why focus on open source TCP/IP stacks? 7 3.2. Which open source stacks, exactly? 7 3.3. 33 new findings 9 4. A comparison with similar studies 14 4.1. Which components are typically flawed? 16 4.2. What are the most common vulnerability types? 17 4.3. Common anti-patterns 22 4.4. What about exploitability? 29 4.5. What is the actual danger? 32 5. Estimating the reach of AMNESIA:33 34 5.1. Where you can see AMNESIA:33 – the modern supply chain 34 5.2. The challenge – identifying and patching affected devices 36 5.3. Facing the challenge – estimating numbers 37 5.3.1. How many vendors 39 5.3.2. What device types 39 5.3.3. How many device units 40 6. An attack scenario 41 6.1. Other possible attack scenarios 44 7. Effective IoT risk mitigation 45 8. Conclusion 46 FORESCOUT RESEARCH LABS RESEARCH REPORT | AMNESIA:33 A note on vulnerability disclosure We would like to thank the CERT Coordination Center, the ICS-CERT, the German Federal Office for Information Security (BSI) and the JPCERT Coordination Center for their help in coordinating the disclosure of the AMNESIA:33 vulnerabilities.
    [Show full text]
  • 1921 Tulsa Race Riot Reconnaissance Survey
    1921 Tulsa Race Riot Reconnaissance Survey Final November 2005 National Park Service U.S. Department of the Interior CONTENTS INTRODUCTION 1 Summary Statement 1 Bac.ground and Purpose 1 HISTORIC CONTEXT 5 National Persp4l<live 5 1'k"Y v. f~u,on' World War I: 1896-1917 5 World W~r I and Postw~r ( r.: 1!1t7' EarIV 1920,; 8 Tulsa RaCR Riot 14 IIa<kground 14 TI\oe R~~ Riot 18 AIt. rmath 29 Socilot Political, lind Economic Impa<tsJRamlt;catlon, 32 INVENTORY 39 Survey Arf!a 39 Historic Greenwood Area 39 Anla Oubi" of HiOlorK G_nwood 40 The Tulsa Race Riot Maps 43 Slirvey Area Historic Resources 43 HI STORIC GREENWOOD AREA RESOURCeS 7J EVALUATION Of NATIONAL SIGNIFICANCE 91 Criteria for National Significance 91 Nalional Signifiunce EV;1lu;1tio.n 92 NMiol\ill Sionlflcao<e An.aIYS;s 92 Inl~ri ly E~alualion AnalY'is 95 {"",Iu,ion 98 Potenl l~1 M~na~menl Strategies for Resource Prote<tion 99 PREPARERS AND CONSULTANTS 103 BIBUOGRAPHY 105 APPENDIX A, Inventory of Elltant Cultural Resoun:es Associated with 1921 Tulsa Race Riot That Are Located Outside of Historic Greenwood Area 109 Maps 49 The African American S«tion. 1921 51 TI\oe Seed. of c..taotrophe 53 T.... Riot Erupt! SS ~I,.,t Blood 57 NiOhl Fiohlino 59 rM Inva.ion 01 iliad. TIll ... 61 TM fighl for Standp''''' Hill 63 W.II of fire 65 Arri~.. , of the Statl! Troop< 6 7 Fil'lal FiOlrtino ~nd M~,,;~I I.IIw 69 jii INTRODUCTION Summary Statement n~sed in its history.
    [Show full text]
  • Performance Study of Real-Time Operating Systems for Internet Of
    IET Software Research Article ISSN 1751-8806 Performance study of real-time operating Received on 11th April 2017 Revised 13th December 2017 systems for internet of things devices Accepted on 13th January 2018 E-First on 16th February 2018 doi: 10.1049/iet-sen.2017.0048 www.ietdl.org Rafael Raymundo Belleza1 , Edison Pignaton de Freitas1 1Institute of Informatics, Federal University of Rio Grande do Sul, Av. Bento Gonçalves, 9500, CP 15064, Porto Alegre CEP: 91501-970, Brazil E-mail: [email protected] Abstract: The development of constrained devices for the internet of things (IoT) presents lots of challenges to software developers who build applications on top of these devices. Many applications in this domain have severe non-functional requirements related to timing properties, which are important concerns that have to be handled. By using real-time operating systems (RTOSs), developers have greater productivity, as they provide native support for real-time properties handling. Some of the key points in the software development for IoT in these constrained devices, like task synchronisation and network communications, are already solved by this provided real-time support. However, different RTOSs offer different degrees of support to the different demanded real-time properties. Observing this aspect, this study presents a set of benchmark tests on the selected open source and proprietary RTOSs focused on the IoT. The benchmark results show that there is no clear winner, as each RTOS performs well at least on some criteria, but general conclusions can be drawn on the suitability of each of them according to their performance evaluation in the obtained results.
    [Show full text]
  • Operating in a New Environment
    EMBEDDED DESIGN OPERATING SYSTEMS lthough the concept of the IoT was Ioated around the turn of the Millennium, it is A only recently that the approach has gathered significant momentum. But, because it is a blanket term, IoT is not only being applied to large and small applications alike, it is also being applied in a wide range of end markets. With such a spread, it will come as no surprise to discover that one size does not fit all when it comes to operating systems. At the high end of the market, companies like Intel are vying to provide a complete solution. Alongside its processor technology, Intel can integrate Wind River’s VxWorks operating system and McAfee security software to create a system capable of handling high levels of complexity. But those developing wearable devices, for example, may not want to take advantage of such a system; they may well be looking for an OS that runs in a very small footprint but, nonetheless, offers a range of Operating in a new necessary features while consuming minimal amounts of power. ARM has had its eyes on the sector for some time and, last year, rolled out environment a significant extension to its mbed programme. Previously, mbed was an embedded development community The Internet of Things is posing challenges to OS developers. with ambitions similar to those of Arduino and Raspberry Pi. But mbed How are they responding? By Graham Pitcher. now has a much bigger vision – the IoT. As part of this approach, it is creating mbed OS (see fig 1).
    [Show full text]
  • RIOT: an Open Source Operating System for Low-End Embedded Devices in the Iot Emmanuel Baccelli, Cenk Gundo¨ Gan,˘ Oliver Hahm, Peter Kietzmann, Martine S
    This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/JIOT.2018.2815038, IEEE Internet of Things Journal 1 RIOT: an Open Source Operating System for Low-end Embedded Devices in the IoT Emmanuel Baccelli, Cenk Gundo¨ gan,˘ Oliver Hahm, Peter Kietzmann, Martine S. Lenders, Hauke Petersen, Kaspar Schleiser, Thomas C. Schmidt, and Matthias Wahlisch¨ Abstract—As the Internet of Things (IoT) emerges, compact low-end IoT devices. RIOT runs on minimal memory in the operating systems are required on low-end devices to ease devel- order of ≈10kByte, and can run on devices with neither MMU opment and portability of IoT applications. RIOT is a prominent (memory management unit) nor MPU (memory protection free and open source operating system in this space. In this paper, we provide the first comprehensive overview of RIOT. We cover unit). The goal of this paper is to provide an overview of the key components of interest to potential developers and users: RIOT, both from the operating system point of view, and from the kernel, hardware abstraction, and software modularity, both an open source software and ecosystem point of view. conceptually and in practice for various example configurations. We explain operational aspects like system boot-up, timers, power Prior work [28], [29] has surveyed the space of operating management, and the use of networking. Finally, the relevant APIs as exposed by the operating system are discussed along systems for low-end IoT devices.
    [Show full text]
  • Soft Tools for Robotics and Controls Implementations
    Soft Tools for Robotics and Controls Implementations A Thesis Submitted to the Faculty of Drexel University by Robert M. Sherbert in partial fulfillment of the requirements for the degree of Master of Science in Electrical Engineering June 2011 c Copyright 2011 Robert M. Sherbert. All rights reserved. ii Dedications To the parents who placed me on my path, to the mentors who guided me along its many turns, and to the friends who made the long journey swift. iii Acknowledgments There are a number of people to whom I owe a great deal of thanks in completing this document. While the labor has been my own, the inspiration for it and the support to finish it have come from the community around me. In creating this work I have taken on the role of toolsmith and, as tools are worthless without their users, it is to these individuals that I am especially indebted. I would like to thank Dr. Oh for lending his vision of robotics testing and prototyping which inspired this work. You have taught me more than I realized there was to know about the modern practice of science. I would also like to thank Dr. Chmielewski for lending his experience, insight, and enthusiasm to the project. Having these ideas weighed against and improved by your practical knowledge has provided a very important validation for me. Above all I would like to thank my friends at DASL, without whom the entirety of this project would have been consigned to the dust bin long ago. You have given me not only critical feedback and suggestions but also the support and encouragement that has helped me carry this to completion.
    [Show full text]
  • B.Tech. CSE CBCS W.E.F. July, 2019
    The Curriculum Book BACHELOR OF TECHNOLOGY I tn COMPUTER SCIENCE AND ENGINEERING FOUR YEAR PROGRAMME Choice Based Credit System vy. e. f. JuIy ZAlg (70:30) . ,_i 1 .I DEPARTMENT OF COMPUTER SCIENCE AI\D BNGINEERING GURU JAMBHESHWAR UNIVERSITY OF SCIENCE & TECHNOLOGY tr j HISAR.125OO1, HARYANA scheme & syllabi2019 GURU JAMBHESHWAR UNIVERSITY OF SCIENCE & TECHNOLOGY, HISAR (Established by state Legistature 'A',Grade,. Act 17 of lggs) NA.AC Accreditid state Govt. university Acad /AC-ilt,tFqc_1 Vot. 3DAlgJf 7 7 Dated: Ulfr:f To The Controller of Examinations GJUS&T, Hisar. sub: Approval of scheme of examination & syllabi of various B.Tech. progralle(sJ being run in university Teachiig Departments as welt as affil iated En g i neeri ng c oilege(s)/r nstitutelsy. AND Recommendations of Faculty Engineering open & Technology regarding Elective, Format of Minor Quu.ti;;-of papei Mooc strength for programme courses, minimum Erective, semester Registration etc. Sir, I am directed to inform you that the vice-chancellor, on the recommendations of the Faculty of Engineering & Technology, vide resolutions no. 2to 13 in its meeting held on 1B 07'2a19, is pleased to approve . the following scheme & syllabi of B.Tech. programme(s) w'e'f' the academic session batch / mentioned against each being run in University Teaching Departments as well as affiliated colleges/institutions and recommendations of Faculty of Engineering & Technolcgy, regarding open Elective, format of Minor Question Paper, Mooc courses, minimum strength for programme Elective' semester Registration etc under sectio n 11(5) in anticipation of approvat of the Acadenric councir of the University Act, 1995.- 1' B'Tech (Printing Technology), B Tec.h (Packaging Technology) (Printing & Packaging i""r'norogD-ath ""un',i""o,,,& B.Tech.
    [Show full text]
  • Kinetis SDK V.1.3.0 Release Notes
    Freescale Semiconductor Document Number: KSDK130RN Release Notes Rev. 0, 09/2015 Kinetis SDK v.1.3.0 Release Notes Contents 1 Overview 1 Overview....................................................................1 2 What Is New..................................... .........................1 These are the release notes for the Freescale Kinetis Software Development Kit (KSDK) 1.3.0. The core of the Kinetis SDK 3 Development Tools................................................... 2 is a set of drivers architected in two layers: the Hardware 4 Supported Development Systems..............................3 Abstraction Layer (HAL) and the Peripheral Driver Layer. 5 Release Contents....................................................... 6 The HAL abstracts the hardware register accesses into a set of stateless functional primitives which provide the building 6 Kinetis SDK Release Overview.................................7 blocks for high-level Peripheral Drivers or applications. The 7 Known Issues.......................................................... 11 Peripheral Driver Layer implements use-case driven drivers by utilizing one or more HAL layer components, system services, 8 Change Log............................................................. 13 and possibly other Peripheral Drivers. 9 Revision History......................... ............................ 15 The Kinetis SDK includes a set of example applications demonstrating the use of the Peripheral Drivers and other integrated software modules such as a Real-Time Operating System (RTOS) through an RTOS abstraction layer. The Kinetis SDK also integrates middleware such as the Freescale USB stack to provide an easy-to-use Software Development Kit for Kinetis microcontroller (MCU) product families. For the latest version of this and other Kinetis SDK documents, see the Kinetis SDK homepage KINETIS-SDK: Software Development Kit for Kinetis MCUs . 2 What Is New © 2015 Freescale Semiconductor, Inc. Development Tools This section describes the major changes and new features implemented in this release.
    [Show full text]
  • A Comparative Study Between Operating Systems (Os) for the Internet of Things (Iot)
    VOLUME 5 NO 4, 2017 A Comparative Study Between Operating Systems (Os) for the Internet of Things (IoT) Aberbach Hicham, Adil Jeghal, Abdelouahed Sabrim, Hamid Tairi LIIAN, Department of Mathematic & Computer Sciences, Sciences School, Sidi Mohammed Ben Abdellah University, [email protected], [email protected], [email protected], [email protected] ABSTRACT Abstract : We describe The Internet of Things (IoT) as a network of physical objects or "things" embedded with electronics, software, sensors, and network connectivity, which enables these objects to collect and exchange data in real time with the outside world. It therefore assumes an operating system (OS) which is considered as an unavoidable point for good communication between all devices “objects”. For this purpose, this paper presents a comparative study between the popular known operating systems for internet of things . In a first step we will define in detail the advantages and disadvantages of each one , then another part of Interpretation is developed, in order to analyze the specific requirements that an OS should satisfy to be used and determine the most appropriate .This work will solve the problem of choice of operating system suitable for the Internet of things in order to incorporate it within our research team. Keywords: Internet of things , network, physical object ,sensors,operating system. 1 Introduction The Internet of Things (IoT) is the vision of interconnecting objects, users and entities “objects”. Much, if not most, of the billions of intelligent devices on the Internet will be embedded systems equipped with an Operating Systems (OS) which is a system programs that manage computer resources whether tangible resources (like memory, storage, network, input/output etc.) or intangible resources (like running other computer programs as processes, providing logical ports for different network connections etc.), So it is the most important program that runs on a computer[1].
    [Show full text]
  • Firmware Pro Robotické Vozítko
    VYSOKÉ UČENÍ TECHNICKÉ V BRNĚ BRNO UNIVERSITY OF TECHNOLOGY FAKULTA ELEKTROTECHNIKY A KOMUNIKAČNÍCH TECHNOLOGIÍ ÚSTAV AUTOMATIZACE A MĚŘICÍ TECHNIKY FACULTY OF ELECTRICAL ENGINEERING AND COMMUNICATION DEPARTMENT OF CONTROL AND INSTRUMENTATION FIRMWARE PRO ROBOTICKÉ VOZÍTKO FIRMWARE FOR THE ROBOTIC VEHICLE DIPLOMOVÁ PRÁCE MASTER'S THESIS AUTOR PRÁCE Bc. LUKÁŠ OTAVA AUTHOR VEDOUCÍ PRÁCE Ing. PAVEL KUČERA, Ph.D. SUPERVISOR BRNO 2013 ABSTRAKT Tato práce je zaměřena na vytvoření firmware pro robotické vozítko, založené na ar- chitektuře ARM Cortex-M3, který využívá operační systém reálného času. Úvodní část obsahuje informace o dostupných operačních systémech reálného času pro malé vestavné systémy, popis architektury ARM Cortex-M3 a hardwarového řešení řídicího systému. Praktická část se zabývá výběrem a měřením zvolených operačních systémů reálného času. Výsledkem práce je firmware složený z programových modulů, které slouží kovlá- dání jednotlivých HW prvků. Je vytvořena také ukázková aplikace, která umožňuje na dálku ovládat pohyb robota a ukládat provozní data robota. KLÍČOVÁ SLOVA ARM, Cortex M3, LM3S8962, reálný čas, RTOS, FreeRTOS, CooCox, CoOS, uC/OSIII, absolutní časování, přepnutí kontextu, DC motor, akcelerometr, FreeRTOS+TRACE, synchronizace, regulátor, SLIP, diagnostika RTOS ABSTRACT This thesis is focused on a firmware for robotic vehicle based on the ARM Cortex- M3 architecture that is running a real-time operating system (RTOS). Theoretical part describes available solutions of embedded RTOS and concrete HW implementation of the robotic vehicle. There is also comparison of the three selected RTOS with their measurements. Result of this thesis is base firmware compounded by a program modules that controls HW parts. There is also a sample PC and firmware application that extends base firmware.
    [Show full text]
  • Mastering the Freertos™ Real Time Kernel
    Mastering the FreeRTOS™ Real Time Kernel This is the 161204 copy which does not yet cover FreeRTOS V9.0.0, FreeRTOS V10.0.0, or low power tick-less operation. Check http://www.FreeRTOS.org regularly for additional documentation and updates to this book. See http://www.FreeRTOS.org/FreeRTOS-V9.html for information on FreeRTOS V9.x.x. See https://www.freertos.org/FreeRTOS-V10.html for information on FreeRTOS V10.x.x. Applications created using FreeRTOS V9.x.x onwards can allocate all kernel objects statically at compile time, removing the need to include a heap memory manager. This text is being provided for free. In return we ask that you use the business contact email link on http://www.FreeRTOS.org/contact to provide feedback, comments and corrections. Thank you. i ii iii Mastering the FreeRTOS™ Real Time Kernel A Hands-On Tutorial Guide Richard Barry iv Pre-release 161204 Edition. All text, source code, and diagrams are the exclusive property of Real Time Engineers Ltd. unless otherwise noted inline. © Real Time Engineers Ltd. 2016. All rights reserved. http://www.FreeRTOS.org http://www.FreeRTOS.org/plus http://www.FreeRTOS.org/labs FreeRTOS™, FreeRTOS.org™ and the FreeRTOS logo are trademarks of Real Time Engineers Ltd. OPENRTOS® and SAFERTOS® are trademarks of WITTENSTEIN Aerospace and Simulation Ltd. All other brands or product names are the property of their respective holders. v vi To Caroline, India and Max. vii viii Contents Contents .................................................................................................................................
    [Show full text]