Multiprocessor Hardware RTOS

Total Page:16

File Type:pdf, Size:1020Kb

Multiprocessor Hardware RTOS Virtual Platform for Hw RTOS – Multiprocessor Hardware RTOS Fabrice Muller, Farooq Muhammad [email protected], [email protected] LEAT-CNRS - University of Nice-Sophia Antipolis – France http://www.polytech.unice.fr/~fmuller Abstract SiliconOS [1] is a full-fledged operating system in which the majority of the μlTRON functionality is implemented on a coprocessor called Silicon TRON. SiliconOS does not We propose a Hardware Multiprocessor OS running on support multiprocessor architectures. Moreover, services prototyping platform which offers new services to improve like memory and timer management that consumes multiprocessor management and includes a performance processor time are still implemented in software. The analyzer tool. resulting software kernel is one third the size of the original software kernel. 1. Introduction The δ SoC Codesign Framework [2] is built around the With the increasing complexity of applications, Atlanta kernel [3] and allows a more fine-grained Multiprocessor System on Chip (MPSoC) becomes an partitioning with respect to [1]. This kernel provides key important choice for implementation. But, MPSoC RTOS features including multitasking capabilities, event- solutions for real time systems require an efficient Real driven and priority-based pre-emptive scheduling, inter-task Time Operating System (RTOS) to manage the resources communication and synchronization, but it does not permit and to guarantee the real time constraints. However, the to change the scheduling at run time. HOPES [4] is a verification of the application running on the MPSoC RTOS-like system that allows run time partitioning and platform grows to be too complex due to the increase of allocation of reconfigurable FPGAs. It supports both pre- number of processors, the application complexity, the bus emptive and non pre-emptive scheduling methods but does interconnections and the management of resources by one not provide multiprocessor scheduling and semaphore or more OS. Indeed, management of resources and services. FASTCHART [1] is a real time kernel fully scheduling of applications distributed on processors are also implemented in hardware. Key features of this kernel are: complex problems. priority scheduling, synchronization primitives and We propose a new approach which includes a Prototyping interrupt handling but the last version (Sierra 16) does not Platform and Virtual Platform based on SystemC language support multiprocessor architectures. Despite this amount of composed of a number of heterogeneous processors, previous work and initial industrial attempts like [5], at communication busses and a generic HwRTOS (Hardware present commercial RTOS does not offer generally: Real Time Operating System) to manage the MPSoC • Multiprocessor support with the possibility of dynamic platform. The main challenge is to validate the application load balancing (global and local scheduling), behavior on an MPSoPC platform. To make this possible, • Ability for designers to modify policies at run time. we developed a generic RTOS in hardware with a Hardware Users can decide only offline which algorithms to Debug Module included in the HwRTOS and connected to implement in hardware and cannot adapt to user needs the Performance Analyzer tool. It is also possible to make at run time. decisions about scheduling techniques (Rate Monotonic, We propose an embedded and generic hardware EDF) and scheduling taxonomy (Global, Local, Hybrid), multiprocessor RTOS where the user can select statically and adapt these choices to the varying needs of application the different scheduling algorithms. It can also change the at run time. scheduling policies at run time as well. The effort in this One solution often used for the management of applications work focused on not only implementing RTOS in hardware, is an RTOS. Indeed, some RTOS include specific services but also on providing flexibility to the user for changing to carry out memory or input/output management, but all decision-algorithms at run time thanks to VHDL or these functionalities are implemented in software and are SystemC algorithms within the HwRTOS. Multiprocessor supported by the processor. For example, VxWorks or Main OS Hw Services Complex applications Architecture RTLinux are very complete. Thus our goal is not to rival with these RTOS, but to define an efficient hardware implementation and evaluate its benefits. Open The idea of a hardware Operating System that moves Hardware scheduling and inter-process communication from software RTOS Trace Analyzer to hardware has been addressed in some previous works. Scheduling The main idea is to move the RTOS functionalities that Algorithms consume more CPU power into hardware in order to benefit Easy‐plug user Hw services from hardware acceleration. Figure 1 : Hardware RTOS possibilities. 2. Hw MP RTOS feature is the SystemC algorithms integrated on the The HwRTOS is the heart of the SoPC platform and Virtual HwRTOS for scheduling analysis. Platform as shown the Figure 1. It can manage complex In conclusion, we have proposed a new a hardware RTOS applications on a homo/heterogeneous multiprocessor able to support easily different scheduling algorithms and architectures. There are some generic parameters (number new user OS services. The resulting system can be of processors, number of tasks …) to adapt the HwRTOS integrated easily on a SoC/SoPC and Virtual Platform. No for a target application. other multiprocessor hardware RTOS offers this capability Considering the multiprocessor architecture of Figure 2 and and flexibility. a partition of the application, we propose to allocate task execution on set of processors and to use HwRTOS services 128 Global Tasks CLB Slices 64 Global Tasks to schedule tasks and to synchronize the communications 9000 64 Global Tasks 32 Global Tasks between tasks by semaphores or message queues. The goal 8000 32 Global Tasks 7000 32 Global Tasks 16 Global Tasks is to run computational intensive parts of the HwRTOS in 6000 16 Global Tasks 5000 8 Global Tasks Slices hardware to improve the performances and to control all 4000 processors at any time. We have just kept a minimal CLB 3000 2000 software layer to responds quickly to the commands of the 1000 0 hardware part. Per processor 1 proc 2 proc 4 proc The software layer sends parameters and a command 8 local tasks 1507 2035 3037 associated to an OS service, towards the hardware part that 16 local tasks 1998 2816 4668 triggers the execution of hardware OS services. The 32 local tasks 2853 4478 7958 HwRTOS core can be connected to any bus. The designer Dffs or Latches 128 Global Tasks 64 Global Tasks 64 Global Tasks has to create a wrapper to adapt the protocol of the 12000 32 Global Tasks 32 Global Tasks 10000 HwRTOS generic bus. The capability of multi-port is 32 Global Tasks 16 Global Tasks possible to separate the debug port and the application 8000 16 Global Tasks Latches 8 Global Tasks ports. That does not cause any disturbance in behavior of 6000 or 4000 the application in the Prototyping/Real Platform. DFF 2000 Application Global Area Registers 0 Per processor 1 proc 2 proc 4 proc ‐ OS Name, Version 8 local tasks ‐ Generic paremeters 2196 2914 4545 ‐ Service information 16 local tasks 2798 3962 6732 processorprocessor Processors ‐ Debug information 32 local tasks 3948 6090 10930 Bus Interrupt Processor Area Registers ‐ Parameters ‐ Status Figure 3 : Resources Utilizations on Virtex5 SX50. ‐ Command ‐ Return value ‐ Command,parameters ‐ Status, return value … Wrapper ‐ Tcb pointer 7. References ‐ Timer [1] Nakano, A. Utama, M. Itabashi, A. Shiomi, and M. Debug Area Registers Registers Imai. Hardware implementation of real-time operating port HwRTOS ‐ Busy place, system. s.l. : Proceedings of the 12 TRON Project Hw OS Hw OScore ‐ Debug control International Symposium pp 34-42;1995, 1995. Debug service service ‐ Event filter, trigger HwRTOS IP ‐ Data trace [2] Blough, V. J. Mooney and D. M. A Hardware-Software Real-Time Operating System Framework for SOCs. s.l. : Figure 2 : Interaction with Environment. IEEE Design and Test of Computers, pp. 44-51, November- December 2002, 2002. 5. Results [3] P. Kuacharoen, M. Shalan and V. Mooney. A The HwRTOS implementation has been tested in VirtexII Configurable Hardware Scheduler for Real-Time Systems. Pro, Virtex4 and Virtex5 technology. The Figure 3 sums up s.l. : Proceedings of the International Conference on the resources for configurations of the HwRTOS for Engineering of Reconfigurable Systems and Algorithms Virtex5 target. We have fixed 8 semaphores, 8 message (ERSA'03) pp.96-101, June 2003, 2003. Vol. pp.96-101, queues and no debug service. We also include the local June 2003. scheduling mode (by priority and parallel computation) and [4] K. Baskaran, W. Jigang, and T. .Srikanthan. A mixed scheduling mode (by priority and sequential Hardware Operating System based Approach for Run-time computation). To obtain the total number of schedulable Reconfigurable Platform of Embedded Devices. s.l. : 6th task for a configuration, you must add the local tasks and Real Time Linux Workshop (Singapore), Nov 3-5 2004, global tasks. For example, for 4 processors and 8 local 2004. tasks, the HwRTOS can schedule till 48 tasks. [5] Klevin, Tommy. Get RealFast RTOS with Xilinx FPGAs. XCELL. 2003, 45. 6. Conclusion The multiprocessor Hardware RTOS is efficient (fast) and flexible as well since it provides much freedom to the designer for customization. It integrated main OS services with multiprocessor characteristics. The other important .
Recommended publications
  • Sistemi Operativi Real-Time Marco Cesati Lezione R13 Sistemi Operativi Real-Time – II Schema Della Lezione
    Sistemi operativi real-time Marco Cesati Lezione R13 Sistemi operativi real-time – II Schema della lezione Caratteristiche comuni VxWorks LynxOS Sistemi embedded e real-time QNX eCos Windows Linux come RTOS 15 gennaio 2013 Marco Cesati Dipartimento di Ingegneria Civile e Ingegneria Informatica Università degli Studi di Roma Tor Vergata SERT’13 R13.1 Sistemi operativi Di cosa parliamo in questa lezione? real-time Marco Cesati In questa lezione descriviamo brevemente alcuni dei più diffusi sistemi operativi real-time Schema della lezione Caratteristiche comuni VxWorks LynxOS 1 Caratteristiche comuni degli RTOS QNX 2 VxWorks eCos 3 LynxOS Windows Linux come RTOS 4 QNX Neutrino 5 eCos 6 Windows Embedded CE 7 Linux come RTOS SERT’13 R13.2 Sistemi operativi Caratteristiche comuni dei principali RTOS real-time Marco Cesati Corrispondenza agli standard: generalmente le API sono proprietarie, ma gli RTOS offrono anche compatibilità (compliancy) o conformità (conformancy) allo standard Real-Time POSIX Modularità e Scalabilità: il kernel ha una dimensione Schema della lezione Caratteristiche comuni (footprint) ridotta e le sue funzionalità sono configurabili VxWorks Dimensione del codice: spesso basati su microkernel LynxOS QNX Velocità e Efficienza: basso overhead per cambi di eCos contesto, latenza delle interruzioni e primitive di Windows sincronizzazione Linux come RTOS Porzioni di codice non interrompibile: generalmente molto corte e di durata predicibile Gestione delle interruzioni “separata”: interrupt handler corto e predicibile, ISR lunga
    [Show full text]
  • Μitron 4.0 Specification (Ver. 4.03.00) TEF024-S001-04.03.00/En July 2010 Copyright © 2010 by T-Engine Forum
    μITRON 4.0 Specification Ver. 4.03.00 TEF024-S001-04.03.00/en July 2010 μITRON 4.0 Specification (Ver. 4.03.00) TEF024-S001-04.03.00/en July 2010 Copyright © 2010 by T-Engine Forum. This “μITRON 4.0 Specification (Ver. 4.03.00)” was originally released by TRON ASSOCIATION which has been integrated into T-Engine Forum since January 2010. The same specification now has been released by T-Engine Forum as its own specification without modification of the content after going through the IPR procedures. T-Engine Forum owns the copyright of this specification. Permission of T-Engine Forum is necessary for copying, republishing, posting on servers, or redistribution to lists of the contents of this specification. The contents written in this specification may be changed without a prior notice for improvement or other reasons in the future. About this specification, please refer to follows; Publisher T-Engine Forum The 28th Kowa Building 2-20-1 Nishi-gotanda Shinagawa-Ward Tokyo 141-0031 Japan TEL:+81-3-5437-0572 FAX:+81-3-5437-2399 E-mail:[email protected] TEF024-S001-04.03.00/en µITRON4.0 Specification Ver. 4.03.00 Supervised by Ken Sakamura Edited and Published by TRON ASSOCIATION µITRON4.0 Specification (Ver. 4.03.00) The copyright of this specification document belongs to TRON Association. TRON Association grants the permission to copy the whole or a part of this specification document and to redistribute it intact without charge or at cost. However, when a part of this specification document is redistributed, it must clearly state (1) that it is a part of the µITRON4.0 Specification document, (2) which part was taken, and (3) the method to obtain the whole specification document.
    [Show full text]
  • V850 Series Development Environment Pamphlet
    To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding. Renesas Electronics website: http://www.renesas.com April 1st, 2010 Renesas Electronics Corporation Issued by: Renesas Electronics Corporation (http://www.renesas.com) Send any inquiries to http://www.renesas.com/inquiry. Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples.
    [Show full text]
  • Ken Sakamura
    2014 TRON Symposium. 30th Anniversary TRON Project 30th Anniversary and Its Future Outlook Embedded systems technology to support the utilization of the IoT big data and future plan for T-Engine Ken Sakamura Professor, Graduate School of Interdisciplinary Studies, The University of Tokyo Director of YRP Ubiquitous Networking Laboratory Chair of T-Engine Forum / uID Center 2014 TRON Symposium. 30th Anniversary ① TRON Project The Real-time Operating system Nucleus The 30th anniversary in 2014 One of the longest lasting projects related to Japanese computing Copyright © 2014 by Ken SAKAMURA 2 2014 TRON Symposium. 30th Anniversary What is TRON? RTOS for system control, and has different basic architecture from Windows and Linux RTOS: Real-Time Operating System Copyright © 2014 by Ken SAKAMURA 3 2014 TRON Symposium. 30th Anniversary TRON RTOS Is Embedded in Many Things “HAYABUSA” (MUSES-C), an asteroid explorer “IKAROS, ” Interplanetary Kite-craft Accelerated by Radiation Of the Sun 4 2014 TRON Symposium. 30th Anniversary TRON Project’s Root Is in Embedded Systems 5 2014 TRON Symposium. 30th Anniversary ② 30 Years of TRON Copyright © 2014 by Ken SAKAMURA 6 2014 TRON Symposium. 30th Anniversary Started in 1984 Copyright © 2014 by Ken SAKAMURA 7 2014 TRON Symposium. 30th Anniversary Historical Background at the Time Copyright © 2014 by Ken SAKAMURA 8 I4004 by Intel (1971) 2014 TRON Symposium. 30th Anniversary Alto by Xerox (1973) 2014 TRON Symposium. 30th Anniversary 2014 TRON Symposium. 30th Anniversary ③ Future Design Copyright © 2014 by Ken SAKAMURA 11 2014 TRON Symposium. 30th Anniversary How the Society Will Change Based on Newly Available Computers? Copyright © 2014 by Ken SAKAMURA 12 2014 TRON Symposium.
    [Show full text]
  • U.S. Government Publishing Office Style Manual
    Style Manual An official guide to the form and style of Federal Government publishing | 2016 Keeping America Informed | OFFICIAL | DIGITAL | SECURE [email protected] Production and Distribution Notes This publication was typeset electronically using Helvetica and Minion Pro typefaces. It was printed using vegetable oil-based ink on recycled paper containing 30% post consumer waste. The GPO Style Manual will be distributed to libraries in the Federal Depository Library Program. To find a depository library near you, please go to the Federal depository library directory at http://catalog.gpo.gov/fdlpdir/public.jsp. The electronic text of this publication is available for public use free of charge at https://www.govinfo.gov/gpo-style-manual. Library of Congress Cataloging-in-Publication Data Names: United States. Government Publishing Office, author. Title: Style manual : an official guide to the form and style of federal government publications / U.S. Government Publishing Office. Other titles: Official guide to the form and style of federal government publications | Also known as: GPO style manual Description: 2016; official U.S. Government edition. | Washington, DC : U.S. Government Publishing Office, 2016. | Includes index. Identifiers: LCCN 2016055634| ISBN 9780160936029 (cloth) | ISBN 0160936020 (cloth) | ISBN 9780160936012 (paper) | ISBN 0160936012 (paper) Subjects: LCSH: Printing—United States—Style manuals. | Printing, Public—United States—Handbooks, manuals, etc. | Publishers and publishing—United States—Handbooks, manuals, etc. | Authorship—Style manuals. | Editing—Handbooks, manuals, etc. Classification: LCC Z253 .U58 2016 | DDC 808/.02—dc23 | SUDOC GP 1.23/4:ST 9/2016 LC record available at https://lccn.loc.gov/2016055634 Use of ISBN Prefix This is the official U.S.
    [Show full text]
  • Μitron4.0 Specification (Ver
    µITRON4.0 Specification Ver. 4.00.00 ITRON Committee, TRON ASSOCIATION Supervised by Ken Sakamura Edited by Hiroaki Takada Copyright (C) 1999, 2002 by TRON ASSOCIATION, JAPAN µITRON4.0 Specification (Ver. 4.00.00) The copyright of this specification document belongs to the ITRON Committee of the TRON Association. The ITRON Committee of the TRON Association grants the permission to copy the whole or a part of this specification document and to redistribute it intact without charge or with a distribution fee. However, when a part of this specification document is redistributed, it must clearly state (1) that it is a part of the µITRON4.0 Specification document, (2) which part it was taken, and (3) the method to obtain the whole specifi- cation document. See Section 6.1 for more information on the conditions for using this specification and this specification document. Any questions regarding this specification and this specification document should be directed to the following: ITRON Committee, TRON Association Katsuta Building 5F 3-39, Mita 1-chome, Minato-ku, Tokyo 108-0073, JAPAN TEL: +81-3-3454-3191 FAX: +81-3-3454-3224 § TRON is the abbreviation of “The Real-time Operating system Nucleus.” § ITRON is the abbreviation of “Industrial TRON.” § µITRON is the abbreviation of “Micro Industrial TRON.” § BTRON is the abbreviation of “Business TRON.” § CTRON is the abbreviation of “Central and Communication TRON.” § TRON, ITRON, µITRON, BTRON, and CTRON do not refer to any specific product or products. µITRON4.0 Specification Ver. 4.00.00 A Word from the Project Leader Fifteen years have passed since the ITRON Sub-Project started as a part of the TRON Project: a real-time operating system specification for embedded equipment control.
    [Show full text]
  • Analysis of a Hardware-Based Real-Time Kernel
    MÄLARDALEN UNIVERSITY, DEPARTMENT OF SCIENCE, DESIGN AND TECHNOLOGY Analysis of a Hardware- Based Real-Time Kernel Improving Embedded Systems Performance Author: Nils Forsberg ([email protected]) Supervisor: Lennart Lindh Examiner and Supervisor: Moris Behnam 5/5/2014 An evaluation of how to improve embedded and real-time systems performance. I Abstract Embedded systems rely on faster microprocessors and system optimizations to improve their performance. These enhancements are becoming marginal, and so it is interesting to look at other alternatives. This thesis examines the use of a hardware-based kernel called Sierra as an accelerator for software-based real-time operating systems. The software RTOS focused upon is FreeRTOS, and it is compared to Sierra in regards to performance to see if there is actually any improvement to be gained. This proves true, as Sierra is several times faster than FreeRTOS in regards to most of the functionality measured. In order to find out how difficult it would be to perform such acceleration a comparison of the systems is also included, encompassing their architecture, features and functionality. It is showed that the systems are similar in these properties, meaning acceleration would be possible. This information was used in an analysis that shows how to perform the acceleration. The work of implementing system acceleration is not in the scope of this thesis, but the result is presented as a suggestion, or manual, for future work in this vein. II Sammanfattning Inbäddade system förlitar sig på snabbare mikroprocessorer och optimeringar för att nå bättre prestanda resultat. Dessa förbättringar ger allt mindre resultat, och det är därför intressant att hitta alternativ.
    [Show full text]
  • Run-Time Management for Future Mpsoc Platforms
    Run-time management for future MPSoC platforms Citation for published version (APA): Nollet, V. (2008). Run-time management for future MPSoC platforms. Technische Universiteit Eindhoven. https://doi.org/10.6100/IR633897 DOI: 10.6100/IR633897 Document status and date: Published: 01/01/2008 Document Version: Publisher’s PDF, also known as Version of Record (includes final page, issue and volume numbers) Please check the document version of this publication: • A submitted manuscript is the version of the article upon submission and before peer-review. There can be important differences between the submitted version and the official published version of record. People interested in the research are advised to contact the author for the final version of the publication, or visit the DOI to the publisher's website. • The final author version and the galley proof are versions of the publication after peer review. • The final published version features the final layout of the paper including the volume, issue and page numbers. Link to publication General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal.
    [Show full text]
  • Economic Impact of Technology Standards
    Economic Impact of Technology Standards The past and the road ahead September 2017 Authors: Jorge Padilla, John Davies and Aleksandra Boutin compasslexecon.com This report was commissioned by Qualcomm Incorporated. All opinions expressed here are those of the authors, who are all employees of Compass Lexecon: Jorge Padilla, John Davies and Aleksandra Boutin, supported by Anubhav Mohanty and Sabire Ipek Demir. Executive Summary COMpass LEXECON Economic Impact of Technology Standards The past and the road ahead Executive Summary 1.1 This report examines the economic impact of technology others in the ITC sector. Furthermore, this approach is standards - which enable components from different spreading, not least because other industries are adopting suppliers to work together - on innovation, competition and wireless technologies in the ‘Internet of Things’. thus consumer choice and welfare. Such standards exist in 1.6 The mobile telephony industry has seen an impressive rate of all industries but are particularly important in Information growth and innovation, as well as a dynamic market structure and Communications Technology. We show that the way in in which new entrants continue to arise to challenge existing which these standards are developed and governed can have suppliers. Between 1994 and 2013, the number of devices profound implications for the pace of innovation and intensity sold each year rose 62 times or 20.1% per year on average. of competition. The cost of mobile subscriptions relative to maximum data 1.2 We present evidence that industries such as mobile speed has decreased 99% (approx. 40% per year) between telephony, which are based on open standards agreed through 2005 and 2013.
    [Show full text]
  • Modeling Creativity
    TOM DE SMEDT — MODELING CREATIVITY Faculteit Letteren en Wijsbegeerte Departement Taalkunde Modeling Creativity CASE STUDIES IN PYTHON Computermodellen van Creativiteit: Gevalstudies in de Python-programmeertaal Proefschrift voorgelegd tot het behalen van de graad van doctor in de Kunsten aan de Universiteit Antwerpen te verdedigen door Tom De Smedt PROMOTOR Prof. dr. Walter Daelemans CLiPS Computational Linguistics Group Universiteit Antwerpen CO-PROMOTOR Lucas Nijs EMRG Experimental Media Research Group St. Lucas University College of Art & Design, Antwerpen Antwerpen, 2013 1 TOM DE SMEDT — MODELING CREATIVITY Cover artwork: SELF-REPLICATION (Tom De Smedt & Ludivine Lechat) The fonts in the book are Computer Modern, Helvetica Neue, Arial and Courier New. The text was written in Google Docs. The layout was processed in LibreOffice. The illustrations were done in NodeBox. Computer Modern, LibreOffice and NodeBox are free and open source. Print: Silhouet, Maldegem © 2013 Tom De Smedt 2013 Uitgeverij UPA University Press Antwerp UPA is an imprint of ASP nv (Academic and Scientific Publishers nv) Ravensteengalerij 28 B-1000 Brussels Tel. +32 (0)2 289 26 50 Fax +32 (0)2 289 26 59 E-mail: [email protected] www.upa-editions.be ISBN 978 90 5718 260 0 NUR 984 / 616 / 656 Legal deposit D/2013/11.161/016 All rights reserved. No part of this book may be reproduced or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the author. 2 TOM DE SMEDT — MODELING CREATIVITY Modeling Creativity CASE STUDIES IN PYTHON Tom De Smedt “Enough!” he said, hoarse with indignation.
    [Show full text]
  • Vysoké Učení Technické V Brně Brno University of Technology
    VYSOKÉ UČENÍ TECHNICKÉ V BRNĚ BRNO UNIVERSITY OF TECHNOLOGY FAKULTA INFORMAČNÍCH TECHNOLOGIÍ ÚSTAV POČÍTAČOVÝCH SYSTÉMŮ FACULTY OF INFORMATION TECHNOLOGY DEPARTMENT OF COMPUTER SYSTEMS OPERAČNÍ SYSTÉM PRO ŘÍZENÍ VESTAVĚNÝCH APLIKACÍ OPERATING SYSTEM FOR EMBEDDED APPLICATIONS CONTROL BAKALÁŘSKÁ PRÁCE BACHELOR‘S THESIS AUTOR PRÁCE TOMÁŠ KOLARÍK AUTHOR VEDOUCÍ PRÁCE Ing. VÁCLAV ŠIMEK SUPERVISOR BRNO 2009 Abstrakt Práce se zabývá výběrem operačního systému pro vestavěnou řídící jednotku parního sterilizátoru obsluhující barevný displej s dotekovým panelem. Na teoretické úrovni se zabývá architekturou vestavěných systémů a operačních systémů. U nich je pozornost soustředěna na správu procesů. Dále se zabývá přístrojem, pro nějž je vybírán operační systém, důvody pro jeho zavedení, jeho výhodami a nevýhodami v řídícím systému. Pak je součástí práce přehled a rozdělení OS do kategorií podle způsobu použití. A blíže jsou popsány dva open source operační systémy eCos a FreeRTOS. Z nich byl následně kód FreeRTOSe upraven z překladače GCC na překladač IAR. Poslední část práce popisuje architekturu a funkcionalitu vytvořené ukázkové aplikace. Ta pomocí dotekového panelu a barevného displeje umožňuje kreslit barevné nákresy, které se dají pomocí sériové komunikace přenášet do počítače. Abstract This thesis deals with selection of operating system for embedded control unit of steam sterilizer with color touch screen. Theoretical part of the thesis deals with the architecture of embedded systems and operating systems with focus on process management. In addition, the thesis deals with a device for which the operating system is selected, the reason for its implementation, advantages and disadvantages in the control system. The thesis also contains categorization of operating systems by way of use. Of these, two open source operating systems eCos and FreeRTOS are described more thoroughly.
    [Show full text]
  • Introduction to the ITRON Specifications Open Real-Time Operating System Standards for Embedded Systems
    ITRON pf/lettersize/2002/2 02.2.13 11:02 AM ページ6 Introduction to the ITRON Specifications Open Real-Time Operating System Standards for Embedded Systems The ITRON specifications are the standards for real-time operating systems and related specifications for embedded systems. Since the project started, we have published a series of ITRON real-time kernel specifications. Of these, the µITRON real-time kernel specification, which was designed for consumer products and other small- scale embedded systems, has been implemented for numerous 8-bit, 16-bit and 32-bit MCUs (Microcontroller Units) and adopted in countless end products, making it an industry standard in this field. Based on these achievements, we have broadened the scope of our standardization efforts beyond the kernel specifications to related aspects, working to expand the ITRON specifications as well as embedded system design technologies. http://www.itron.gr.jp/ ITRON pf/lettersize/2002/2 02.2.13 11:02 AM ページ1 The Status and Features of Embedded severely limited. On a typical 16-bit MCU there might be 64 KB of Systems ROM and around 1 KB of RAM available, or perhaps 128 KB and 4 KB on a slightly larger system. Another notable feature is the Advances in microprocessor technology continue to open up extremely large number of processor cores in use, since the MCU is new application fields for embedded systems. Originally they were often optimized to a particular application for the sake of cost used mainly for factory production line control and other industrial performance. applications. Their use spread to communications and office Even in the small-scale embedded system field, the growing equipment, then on to automotive systems, audio and video scale and complexity of software and the need for fast development products, TVs, cellular phones, synthesizers, game machines, and turnaround time have made improving software productivity a household appliances such as washing machines, airconditioners pressing need.
    [Show full text]