Desarrollo De Un Sistema Basado En Mpc8572 Y Linux

Total Page:16

File Type:pdf, Size:1020Kb

Desarrollo De Un Sistema Basado En Mpc8572 Y Linux DESARROLLO DE UN SISTEMA BASADO EN MPC8572 Y LINUX Tesis Final de Máster Isaac Gómez Morales Marzo 2009 Director: Josep Dantí Ponente: Josep Fernàndez Marzo 2009 I Agradecimientos A todas las personas que de una manera u otra han hecho posible este proyecto. Mi familia, los compañeros de trabajo, mis amigos de siempre que aún en la distancia siempre me han apoyado. A Carlos, Raquel y Paulino. Gracias a todos II Índice Índice................................................................................................................. III Índice de Figuras..............................................................................................VII 1 Introducción................................................................................................. 1 1.1 Definición del problema y descripción general del trabajo realizado..... 2 1.2 Fines del proyecto................................................................................. 3 1.3 Materiales y métodos ............................................................................ 5 2 Descripción del Sistema.............................................................................. 7 3 Elección Hardware ...................................................................................... 9 3.1 8572 ...................................................................................................... 9 3.2 8548 .................................................................................................... 10 3.3 Aspectos a considerar del hardware ................................................... 11 4 Elección del Sistema Operativo ................................................................ 13 4.1 Aspectos a considerar del sistema operativo ...................................... 13 4.2 Candidatos de sistema operativo para nuestro sistema...................... 15 1.1.1 Embedded Linux........................................................................... 15 1.1.2 RTLinux ........................................................................................ 16 1.1.3 LynxOS......................................................................................... 17 1.1.4 Windows Xp Embedded ............................................................... 18 1.1.5 VxWorks ....................................................................................... 19 4.3 Sistema operativo escogido ................................................................ 21 4.4 Finalización del análisis....................................................................... 22 1.1.1 Herramientas de comunicación .................................................... 22 1.1.2 Log................................................................................................ 23 1.1.3 Entorno de trabajo ........................................................................ 23 5 Diseño del sistema.................................................................................... 25 5.1 Comunicación ..................................................................................... 25 5.2 Sistema de Log ................................................................................... 26 5.3 Entorno de Trabajo.............................................................................. 27 6 Puesta en marcha del sistema.................................................................. 31 III 6.1 Material Proporcionado ....................................................................... 31 6.2 Entorno de trabajo............................................................................... 36 6.2.1 Componentes disponibles ............................................................ 36 6.3 Formas de comunicación utilizadas .................................................... 39 6.4 LTIB para generar las imágenes de nuestro sistema.......................... 40 6.5 Generación de la primera imagen del Kernel de Linux para MPC8572DS................................................................................................. 41 6.5.1 Selección de opciones del Kernel................................................. 42 6.6 Generación de la primera imagen de U-Boot para MPC8572DS ........ 46 6.7 Programación Flash ............................................................................ 47 6.7.1 Programar U-Boot en Flash desde otro U-Boot operativo ............ 47 6.7.2 Programar U-Boot en Flash con CodeWarrior.............................. 49 6.8 Proceso de arranque del sistema........................................................ 53 7 Entorno de trabajo de la tarjeta ................................................................. 55 7.1.1 Ethernet ........................................................................................ 55 7.1.2 PCI-Express.................................................................................. 56 7.2 Puesta en marcha servidor Xserver desde tarjeta gráfica................... 58 7.2.1 Tarjeta Gráfica.............................................................................. 58 7.2.2 Puesta en marcha de Xserver utilizando el framebuffer de la tarjeta gráfica 60 7.3 Historial del sistema ............................................................................ 82 7.4 Herramientas del sistema.................................................................... 82 7.4.1 Compiladores................................................................................ 83 7.4.2 Editores ........................................................................................ 83 7.4.3 Herramientas de medida de rendimiento...................................... 84 1.1.6 Oprofile ......................................................................................... 86 7.4.4 Valgrind ........................................................................................ 87 7.4.5 Open-mpi...................................................................................... 88 8 Certificación Safety ................................................................................... 91 8.1 Necesidad certificación safety............................................................. 91 8.2 Objetivos del estudio........................................................................... 91 8.3 Certificación safety de un sistema basado en Linux ........................... 92 8.3.1 Introducción .................................................................................. 92 8.3.2 Aspectos a tener en cuenta del sistema operativo ...................... 92 IV 8.3.3 Criterios safety de un sistema operativo....................................... 93 8.3.4 Enfoque ........................................................................................ 94 8.3.5 Evaluación preliminar de Linux con la metodología safety ........... 94 8.3.6 Test............................................................................................... 98 8.3.7 Análisis ......................................................................................... 99 8.3.8 Configuración de Linux................................................................. 99 8.3.9 Metodología para la certificación ................................................ 106 9 VxWorks.................................................................................................. 109 9.1 Objetivos ........................................................................................... 109 9.2 Puesta en marcha de la tarjeta MPC8548PC con VxWorks.............. 109 9.2.1 Estudio de los posibles BSP de referencia ................................. 109 9.2.2 Análisis ....................................................................................... 117 9.2.3 Compilación del proyecto a partir del BSP CDS8548................. 118 9.2.4 Proceso de arranque de la tarjeta con VxWorks......................... 119 9.2.5 Problemas .................................................................................. 119 10 Conclusiones........................................................................................ 122 11 Líneas futuras de investigación ............................................................ 127 12 Referencias .......................................................................................... 129 13 Glosario ................................................................................................ 131 Anexo A.......................................................................................................... 132 Anexo A.1 ................................................................................................... 132 Embedded Linux ..................................................................................... 132 Anexo A.2 ................................................................................................... 136 Linux Target Image Builder ..................................................................... 136 Anexo A.3 ................................................................................................... 141 Universal Bootloader............................................................................... 141 Anexo A.4 ................................................................................................... 146 dispositivo Tree ....................................................................................... 146 Anexo A.5 ................................................................................................... 148 CodeWarrior...........................................................................................
Recommended publications
  • Validated Products List, 1995 No. 3: Programming Languages, Database
    NISTIR 5693 (Supersedes NISTIR 5629) VALIDATED PRODUCTS LIST Volume 1 1995 No. 3 Programming Languages Database Language SQL Graphics POSIX Computer Security Judy B. Kailey Product Data - IGES Editor U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 July 1995 QC 100 NIST .056 NO. 5693 1995 NISTIR 5693 (Supersedes NISTIR 5629) VALIDATED PRODUCTS LIST Volume 1 1995 No. 3 Programming Languages Database Language SQL Graphics POSIX Computer Security Judy B. Kailey Product Data - IGES Editor U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 July 1995 (Supersedes April 1995 issue) U.S. DEPARTMENT OF COMMERCE Ronald H. Brown, Secretary TECHNOLOGY ADMINISTRATION Mary L. Good, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arati Prabhakar, Director FOREWORD The Validated Products List (VPL) identifies information technology products that have been tested for conformance to Federal Information Processing Standards (FIPS) in accordance with Computer Systems Laboratory (CSL) conformance testing procedures, and have a current validation certificate or registered test report. The VPL also contains information about the organizations, test methods and procedures that support the validation programs for the FIPS identified in this document. The VPL includes computer language processors for programming languages COBOL, Fortran, Ada, Pascal, C, M[UMPS], and database language SQL; computer graphic implementations for GKS, COM, PHIGS, and Raster Graphics; operating system implementations for POSIX; Open Systems Interconnection implementations; and computer security implementations for DES, MAC and Key Management.
    [Show full text]
  • How to Configure the NFX250 Nextgen
    How to Configure the NFX250 NextGen Published 2021-04-20 ii Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. How to Configure the NFX250 NextGen Copyright © 2021 Juniper Networks, Inc. All rights reserved. The information in this document is current as of the date on the title page. YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036. END USER LICENSE AGREEMENT The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement ("EULA") posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA. iii Table of Contents About This Guide | x 1 Overview NFX250
    [Show full text]
  • Escuela Técnica Superior De Ingenieros De Telecomunicación
    ESCUELA TÉCNICA SUPERIOR DE INGENIEROS DE TELECOMUNICACIÓN TRABAJO FIN DE GRADO GRADO EN INGENIERÍA DE TECNOLOGÍAS ESPECÍFICAS DE TELECOMUNICACIÓN MENCIÓN EN TELEMÁTICA APLICACIÓN ANDROID PARA EL ENTRENAMIENTO COGNITIVO DE PERSONAS BAJO TUTELA JURÍDICA CON DISCAPACIDAD INTELECTUAL O DEL DESARROLLO AUTOR: D. RAÚL VELASCO CAMINERO TUTORA: DRA. DÑA. MÍRIAM ANTÓN RODRÍGUEZ VALLADOLID, ENERO de 2017 TÍTULO: Aplicación Android para el entrenamiento cognitivo de personas bajo tutela jurídica con discapacidad intelectual o del desarrollo AUTOR: D. Raúl Velasco Caminero TUTORA: Dra. Dña. Míriam Antón Rodríguez DEPARTAMENTO: Teoría de la Señal y Comunicaciones e Ingeniería Telemática TRIBUNAL PRESIDENTE: Míriam Antón Rodríguez VOCAL: Mario Martínez Zarzuela SECRETARIO: David González Ortega SUPLENTE: Francisco Javier Díaz Pernas SUPLENTE: Mª Ángeles Pérez Juárez FECHA: CALIFICACIÓN: 3 Resumen El objetivo principal de este proyecto consiste en el desarrollo de una aplicación para la plataforma Android con el fin de tratar de mejorar las capacidades cognitivas de los tutelados a través de juegos desarrollados específicamente para tal fin. Aunque esta es la funcionalidad principal que se ofrece, la aplicación va más allá. Permite llevar un seguimiento de cada tutelado y crear y ver los detalles de los mismos. También permite ver estadísticas de los tutelados en los distintos juegos para ver su desarrollo y mejora. La aplicación es un sistema de seguimiento y rehabilitación donde los voluntarios introducen sus credenciales para poder acceder a todas las funcionalidades citadas anteriormente que ofrece la aplicación. El sistema está desarrollado en Java utilizando el IDE Android Studio y puede utilizarse en cualquier dispositivo que disponga de Android 4.0 o superior como sistema operativo.
    [Show full text]
  • RTI Data Distribution Service Platform Notes
    RTI Data Distribution Service The Real-Time Publish-Subscribe Middleware Platform Notes Version 4.5c © 2004-2010 Real-Time Innovations, Inc. All rights reserved. Printed in U.S.A. First printing. June 2010. Trademarks Real-Time Innovations and RTI are registered trademarks of Real-Time Innovations, Inc. All other trademarks used in this document are the property of their respective owners. Copy and Use Restrictions No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form (including electronic, mechanical, photocopy, and facsimile) without the prior written permission of Real- Time Innovations, Inc. The software described in this document is furnished under and subject to the RTI software license agreement. The software may be used or copied only under the terms of the license agreement. Technical Support Real-Time Innovations, Inc. 385 Moffett Park Drive Sunnyvale, CA 94089 Phone: (408) 990-7444 Email: [email protected] Website: http://www.rti.com/support Contents 1 Supported Platforms.........................................................................................................................1 2 AIX Platforms.....................................................................................................................................3 2.1 Changing Thread Priority.......................................................................................................3 2.2 Multicast Support ....................................................................................................................3
    [Show full text]
  • Research Purpose Operating Systems – a Wide Survey
    GESJ: Computer Science and Telecommunications 2010|No.3(26) ISSN 1512-1232 RESEARCH PURPOSE OPERATING SYSTEMS – A WIDE SURVEY Pinaki Chakraborty School of Computer and Systems Sciences, Jawaharlal Nehru University, New Delhi – 110067, India. E-mail: [email protected] Abstract Operating systems constitute a class of vital software. A plethora of operating systems, of different types and developed by different manufacturers over the years, are available now. This paper concentrates on research purpose operating systems because many of them have high technological significance and they have been vividly documented in the research literature. Thirty-four academic and research purpose operating systems have been briefly reviewed in this paper. It was observed that the microkernel based architecture is being used widely to design research purpose operating systems. It was also noticed that object oriented operating systems are emerging as a promising option. Hence, the paper concludes by suggesting a study of the scope of microkernel based object oriented operating systems. Keywords: Operating system, research purpose operating system, object oriented operating system, microkernel 1. Introduction An operating system is a software that manages all the resources of a computer, both hardware and software, and provides an environment in which a user can execute programs in a convenient and efficient manner [1]. However, the principles and concepts used in the operating systems were not standardized in a day. In fact, operating systems have been evolving through the years [2]. There were no operating systems in the early computers. In those systems, every program required full hardware specification to execute correctly and perform each trivial task, and its own drivers for peripheral devices like card readers and line printers.
    [Show full text]
  • Vxworks OS Changer Gives Developers the Ability to Reuse Vxworks Applications on Diff Erent Operating Systems
    VxWorks® OS Changer Change Your OS - Keep Your Code The OS Changer family of products gives developers the freedom to switch operating systems while leveraging on their existing code and knowledge base to protect their software investment. VxWorks OS Changer gives developers the ability to reuse VxWorks applications on diff erent operating systems. VxWorks OS Changer Highlights Protect your software investment by re-using your VxWorks code Reduce time to market by migrating VxWorks code to a standard OS interface architecture Protect your knowledge-base by using familiar APIs and eliminate the learning curve on the new OS platform Eliminate dependency on a single OS vendor and switch to - An OS that meets your performance and memory footprint needs - An OS that off ers better tools, middleware/drivers and support - An OS that supports your next generation silicon Reduce ongoing development and maintenance cost - Develop target specifi c code on a host platform - Re-use one set of code across multiple host & target OS platforms - Break down VxWorks applications into manageable pieces to reduce complexity and add module protection - Use same APIs for inter-task and inter-process communications OS Changer is highly optimized for each specifi c OS platform Eclipse-based host environment is available to port VxWorks applications using OS Changer in OS PAL (refer to the OS PAL datasheet) OS Changer includes access to the BASE OS Abstractor API features to allow development of highly portable applications (refer to the OS Abstractor datasheet) Additionally, POSIX or open source Linux code can be reused on a new OS platform with POSIX OS Abstractor (refer to the POSIX OS Abstractor datasheet) VxWorks OS Changer is off ered royalty-free with source code Using VxWorks OS Changer OS Changer is designed for use as a C library.
    [Show full text]
  • Altaapi Software User's Manual
    AltaAPI™ Software User’s Manual Part Number: 14301-00000-I4 Cage Code: 4RK27 ● NAICS: 334118 Alta Data Technologies LLC 4901 Rockaway Blvd, Building A Rio Rancho, NM 87124 USA (tel) 505-994-3111 ● www.altadt.com i AltaAPI™ Software User’s Manual ● 14301-00000-I4 Alta Data Technologies LLC ● www.altadt.com CUSTOMER NOTES: Document Information: Alta Software Version: 2.6.5.0 Rev I4 Release Date: November 10, 2014 Note to the Reader and End-User: This document is provided for information only and is copyright by © Alta Data Technologies LLC. While Alta strives to provide the most accurate information, there may be errors and omissions in this document. Alta disclaims all liability in document errors and any product usage. By using an Alta product, the customer or end user agrees (1) to accept Alta’s Standard Terms and Conditions of Sale, Standard Warranty and Software License and (2) to not hold Alta Members, Employees, Contractors or Sales & Support Representatives responsible for any loss or legal liability, tangible or intangible, from any document errors or any product usage. The product described in this document is not US ITAR controlled. Use of Alta products or documentation in violation of local usage, waste discard and export control rules, or in violation of US ITAR regulations, voids product warranty and shall not be supported. This document may be distributed to support government programs and projects. Third party person, company or consultant distribution is not allowed without Alta’s written permission. AltaCore, AltaCore-1553, AltaCore-ARINC, AltaAPI, AltaAPI-LV, AltaView, AltaRTVal, ENET- 1553, ENET-A429 & ENET-1553-EBR are Trademarks of Alta Data Technologies LLC, Rio Rancho, New Mexico USA Contact: We welcome comments and suggestions.
    [Show full text]
  • Introduction to Bioinformatics Introduction to Bioinformatics
    Introduction to Bioinformatics Introduction to Bioinformatics Prof. Dr. Nizamettin AYDIN [email protected] Introduction to Perl http://www3.yildiz.edu.tr/~naydin 1 2 Learning objectives Setting The Technological Scene • After this lecture you should be able to • One of the objectives of this course is.. – to enable students to acquire an understanding of, and understand : ability in, a programming language (Perl, Python) as the – sequence, iteration and selection; main enabler in the development of computer programs in the area of Bioinformatics. – basic building blocks of programming; – three C’s: constants, comments and conditions; • Modern computers are organised around two main – use of variable containers; components: – use of some Perl operators and its pattern-matching technology; – Hardware – Perl input/output – Software – … 3 4 Introduction to the Computing Introduction to the Computing • Computer: electronic genius? • In theory, computer can compute anything – NO! Electronic idiot! • that’s possible to compute – Does exactly what we tell it to, nothing more. – given enough memory and time • All computers, given enough time and memory, • In practice, solving problems involves are capable of computing exactly the same things. computing under constraints. Supercomputer – time Workstation • weather forecast, next frame of animation, ... PDA – cost • cell phone, automotive engine controller, ... = = – power • cell phone, handheld video game, ... 5 6 Copyright 2000 N. AYDIN. All rights reserved. 1 Layers of Technology Layers of Technology • Operating system... – Interacts directly with the hardware – Responsible for ensuring efficient use of hardware resources • Tools... – Softwares that take adavantage of what the operating system has to offer. – Programming languages, databases, editors, interface builders... • Applications... – Most useful category of software – Web browsers, email clients, web servers, word processors, etc..
    [Show full text]
  • Programming Fundamentals - I Basic Concepts Fall-Semester 2016
    Programming Fundamentals - I Basic Concepts Fall-Semester 2016 Prepared By: Rao Muhammad Umer Lecturer, Web: raoumer.github.io Department of Computer Science & IT, The University of Lahore. What is computer? The term "computer" was originally given to humans who performed numerical calculations using mechanical calculators, such as the abacus and slide rule. The term was later given to a mechanical device as they began replacing the human computers. Today's computers are electronic devices that accept data such as numbers, text, sound, image, animations, video, etc., (input), process that data (converts data to information) , produce output, and then store (storage) the results. A basic computer consists of 4 components: 1. Input devices 2. Central Processing Unit or CPU 3. Output devices 4. Memory Input Devices are used to provide input to the computer basic input devices include keyboard, mouse, touch screens etc. Central Processing Unit acts like a brain, it processes all instructions and data in the computer, the instructions are computer commands, these commands are given to CPU by input devices, some of the instructions are generated by the computer itself Output devices are used to receive computer output, the output, some basic output devices are hard drive disk (HDD, commonly known as hard disk), printers, computer screens (Monitors and LCDs) The computer memory is a temporary storage area. It holds the data and instructions that the Central Processing Unit (CPU) needs. Before a program can be run, the program is loaded from some storage device such as into the memory, the CPU loads the program or part of the program from the memory and executes it.
    [Show full text]
  • Mejora Del Comando En Ps En Minix
    MEJORA DEL COMANDO PS EN MINIX. INGENIERIA TECNICA INFORMATICA DE GESTION 2007 1 INTRODUCCIÓN......................................................................................................................................3 OBJETIVO .................................................................................................................................................3 FUNDAMENTOS TEÓRICOS.................................................................................................................3 • FICHERO MINIX/PROC.H.....................................................................................................................3 • FICHERO MINIX/CONF.H.....................................................................................................................3 • FICHERO MINIX/CONFIG.H ................................................................................................................3 • FICHERO MINIX/MPROG.H..................................................................................................................3 • FICHERO USR/LOCAL/SMX/SRC/FS/FPROG.H.......................................................................................4 DESCRIPCIÓN DEL TRABAJO REALIZADO....................................................................................4 PASOS SEGUIDOS PARA LA CREACIÓN DEL PROYECTO..........................................................5 CONCLUSIONES......................................................................................................................................6
    [Show full text]
  • MOL 2 8 Ni 1 6 ;'*•••" CHEP95
    01 v> Si, Ui O 2 MOL 2 8 Ni 1 6 ;'*•••" CHEP95 Hotel Gloria, Rio de Janeiro September 18-22, 1995 — LAFEX/CBPF - — FERMILAB — CHEP95 - COMMITTES LOCAL ORGANIZING LOCAL ORGANIZING COMMITTE - BRASIL - COMMITTE - FERMILAB - Chairpersons of the Conference Alberto Santoro - Chair Vicky White - Chair ALBERTO SANTORO (LAFEX) VICKY WHITE (FERMILAB) Gilvan Alves (LAFEX/CBPF) Paul Lebrun Roberto M. Alves Jr. (LAFEX/CBPF) John Marraffino Valmir C. Barbosa (UFRJ) David Martin International Advisory Committee Denise Belem (Administration) Trang Nguyen Rosemonde Bettencourt (Secretary) Judy Nicholls Marcia Fernandes (Administration) Vivian Odell Katsuya Amako (KEK) Richard Mount (Caltech) Alexandre Grojsgold (LNCC) Frank Rinaldo Paul Avery (Florida State) Thomas Nash (FERMILAB) Marcelo Mendes (LAFEX/CBPF) Elizabeth Schermerhorn Rudy Bock (CERN) Risto Orava (Helsinki) Mariano Miranda (LAFEX/CBPF) Roy Thatcher Kors Bos (NIKHEF) Tony Osborne (CERN) Maria Elena Pol (LAFEX/CBPF) Al Thomas + Network Experts Joel Butler (FERMILAB) Vadim Petukhov (Serpukhov) Ronald Shellard (LAFEX/CBPF) Lauro Whately Aleta Ricciardi (U.TEXAS) Larry Price (ANL) Marcelo Annarumma (IBM) Mari Herrera(Administration) John Cavallini (DOE) Antonio Rivasplata (UNT) Nelly Stanfield(Administration) He S. Chen (Beijing) Raul Rousso (CEFET) Michael Ernst (DESY) Alberto Santoro (LAFEX/CBPF) CONTACT PERSONS (Brazil) Gerson Francisco (Unesp) Sergio Sciutto (Argentina) Hirofumi Fujii (KEK) Ronald Shellard (LAFEX/CBPF) Claudio Amorim (UFRJ) Jose M. Gago (Lisbon) Michel Spiro (Saclay) Felipe Franga (UFRJ) Tom Glanzman (SLAC) Rolando Ticona (Bolivia) Siang W.Song (USP) Bob Grossman (UIC) Enzo Valente (INFN) Carlos Moura (LACC/FUNCEME) Tom Kozlowski (Los Alamos) Jean-Pierre Vialle (LAPP) Raul Russo (CEFET) Paul Kunz (SLAC) Vicky White (FERMILAB) Philippe O.A.Navaux (UFRGS) Stu Loken (LBL) Roy Whitney (CEBAF) Eduardo W.Bergamini (INPA) Luiz F.
    [Show full text]
  • Real-Time Operating Systems at CERN
    cmu — cw -%~*> H CERN/cN/96/11 Paper submitted to the VITA Europe Congress 1996 3 Q q' Brussels, Belgium, 8-9 October 1996 Real-Time Operating Systems at CERN ]. Blake, C. Eck, M. Merkel, L. Pregemig CERN, CN Division CH-1211 Geneva 23, Switzerland Abstract territory". For instance, the LEP (Large Electron Positron Collider) machine and the corresponding control sys Real—time operating systems (RTOS) have been in use at tems have been improved over the years. Its peak CERN for many years in systems to control particle luminosity (i.e., collision rate per second and square accelerators, and in data acquisition and industrial centimetre) increased from 4.25*1030 in 1989 to 24.9*103 control systems for experiments. The paper (i) briefly in 1995 and the integrated luminosity was 26 times overviews CERN’s embedded-systems environment, (ii) higher in 1995 than it was in 1989 ll]. This also had a discusses the reasons for using RTOS at CERN, (iii) gives major impact on the data acquisition systems of the LEP the status of RTOS at CERN, (iv) describes the support, experiments. including netbootable systems, software distribution via servers, and CERN-specific developments. Finally the Athird major distinction between CERN and industry is paper summarizes the experience gained over the years the composition of the experimental work force. In and draws some conclusions. modern experiments several hundred (more than 1000 for next generation experiments) people from dozens of 1. Tm; CERN ENVIRONMENT institutes spread out over Europe and the world collabo rate. Graduate students form an important part of each 1.1 Systems, Changes, and the Workforce collaboration and provide valuable contributions to experiments.
    [Show full text]