DOCSLIB.ORG

Embedded Linux System Design and Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Au0586 half title page 11/17/05 2:05 PM Page 1 EMBEDDED LINUX SYSTEM DESIGN AND DEVELOPMENT Au0586 title page 11/17/05 2:04 PM Page 1 EMBEDDED LINUX SYSTEM DESIGN AND DEVELOPMENT P. Raghavan • Amol Lad • Sriram Neelakandan Boca Raton New York Published in 2006 by Auerbach Publications Taylor & Francis Group 6000 Broken Sound Parkway NW, Suite 300 Boca Raton, FL 33487-2742 © 2006 by Taylor & Francis Group, LLC Auerbach is an imprint of Taylor & Francis Group No claim to original U.S. Government works Printed in the United States of America on acid-free paper 10987654321 International Standard Book Number-10: 0-8493-4058-6 (Hardcover) International Standard Book Number-13: 978-0-8493-4058-1 (Hardcover) Library of Congress Card Number 2005048179 This book contains information obtained from authentic and highly regarded sources. Reprinted material is quoted with permission, and sources are indicated. A wide variety of references are listed. Reasonable efforts have been made to publish reliable data and information, but the author and the publisher cannot assume responsibility for the validity of all materials or for the consequences of their use. No part of this book may be reprinted, reproduced, transmitted, or utilized in any form by any electronic, mechanical, or other means, now known or hereafter invented, including photocopying, microfilming, and recording, or in any information storage or retrieval system, without written permission from the publishers. For permission to photocopy or use material electronically from this work, please access www.copyright.com (http://www.copyright.com/) or contact the Copyright Clearance Center, Inc. (CCC) 222 Rosewood Drive, Danvers, MA 01923, 978-750-8400. CCC is a not-for-profit organization that provides licenses and registration for a variety of users. For organizations that have been granted a photocopy license by the CCC, a separate system of payment has been arranged. Trademark Notice: Product or corporate names may be trademarks or registered trademarks, and are used only for identification and explanation without intent to infringe. Library of Congress Cataloging-in-Publication Data Raghavan, P. (Pichai), 1973- Embedded Linux system design and development / P. Raghavan, Amol Lad, Sriram Neelakandan. p. cm. Includes bibliographical references and index. ISBN 0-8493-4058-6 (alk. paper) 1. Linux. 2. Operating systems (Computers) 3. Embedded computer systems. I. Lad, Amol. II. Neelakandan, Sriram. III. Title. QA76.76.O63R335 2005 005.4'32--dc22 2005048179 Visit the Taylor & Francis Web site at http://www.taylorandfrancis.com Taylor & Francis Group and the Auerbach Publications Web site at is the Academic Division of T&F Informa plc. http://www.auerbach-publications.com All source code in the book is released under GNU GPL v2. It can be used as desired under terms and conditions of GNU GPL v2. Trademarks Ⅲ MIPS is a registered trademark and YAMON is a trademark of MIPS Technologies. Ⅲ IBM and ClearCase are registered trademarks and PowerPC is a trademark of International Business Machines Corporation. Ⅲ UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Ⅲ X11 is a trademark of Massachusetts Institute of Technology. Ⅲ NEC is a registered trademark of NEC Corporation Ⅲ HP is a registered trademark of Hewlett-Packard Company. Ⅲ ColdFire is a registered trademark and Motorola is a trademark of Motorola, Inc Ⅲ Microblaze is trademark of Xilinx Inc Ⅲ Red Hat is a registered trademark and eCos and RedBoot are trademarks of Red Hat, Inc. Ⅲ uClinux is a registered trademark of Arcturus Networks Inc Ⅲ Linux is a registered trademark of Linus Torvalds Ⅲ GoAhead is a registered trademark of GoAhead Software, Inc Ⅲ RTLinux is a registered trademark and FSMLabs, RTLinuxPro and RTCore are trademarks of Finite State Machine Labs, Inc Ⅲ Debian is a registered trademark of Software in the Public Interest, Inc Ⅲ LMBench is a trademark of BitMover, Inc Ⅲ VRTX is a trademark of Microtech Research Inc Ⅲ VxWorks and pSOS are registered trademarks of Wind River Systems, Inc Ⅲ Trolltech is registered trademark and Qt is a trademark of Trolltech in Norway, the United States and other countries Ⅲ OpenGL is a registered trademark of Silicon Graphics, Inc Ⅲ Perforce is a registered trademark of Perforce Software, Inc Ⅲ Eclipse is trademark of Eclipse Foundation, Inc Ⅲ KDE and K Desktop Environment are trademarks of KDE Ⅲ FFmpeg is a trademark of Fabrice Bellard, originator of the FFmpeg project Ⅲ NVIDIA is a registered trademark of NVIDIA Corporation in the United States and other countries Ⅲ ViewML is a registered trademark of Century Software Inc Ⅲ QNX and Neutrino are registered trademarks of QNX Software Systems Ltd Ⅲ Nucleus is a trademark of Accelerated Technology, Inc Ⅲ Accelerated Technology is a registered trademark of Mentor Graphics Corporation Ⅲ ARM and StrongARM are registered trademarks and ARM7 and ARM9 are trademarks of Advanced RISC Machines, Ltd. Ⅲ AMD is a registered trademark of Advanced Micro Devices, Inc. Ⅲ Intel and Pentium are registered trademarks and i386 and XScale are trademarks of Intel Corporation. Ⅲ Sharp is a registered trademark of Sharp Electronics Corp. Ⅲ SPARC is a registered trademark of SPARC International, Inc., and is used under license by Sun Microsystems, Inc. Ⅲ Toshiba is a registered trademark of the Toshiba Corporation. Ⅲ MontaVista is registered trademark of MontaVista Software Inc. Ⅲ LynxOS and BlueCat are registered trademarks and LynuxWorks, SpyKer and VisualLynux are trademarks of LynuxWorks, Inc. Ⅲ Samsung is a registered trademark of Samsung Electronics America, Inc. and its related entities. Ⅲ Ericsson is a registered trademark of Ericsson, Inc. Ⅲ Atmel is registered trademarks of Atmel Corporation. Ⅲ TimeSys®, TimeStorm®, TimeStorm IDE™, TimeStorm LVS™, TimeStorm LDS™, TimeStorm LHD™, TimeSys Reservations™, TimeTrace®, Linux/RTTM and TimeWiz® are registered or unregistered trademarks of TimeSys Corporation in the United States and other countries. Ⅲ NeoMagic is registered trademark of NeoMagic Corporation. Ⅲ Transmeta is a trademark of Transmeta Corporation. Ⅲ Broadcom is a registered trademark of Broadcom Corporation and/or its subsidiaries. Ⅲ SuSE is a registered trademark of SuSE AG. vi Embedded Linux System Design and Development Ⅲ Borland is a registered trademark of Borland Software Corporation in the United States and other countries. Ⅲ Merant is a registered trademark of Merant. Ⅲ SnapGear is a registered trademark of SnapGear Inc. Ⅲ Matsushita is a trademark of the Matsushita Electric Corporation. Ⅲ I2C is a trademark of Philips Semiconductors Corporation. Ⅲ Philips® is a registered trademark of Philips Consumer Electronics Corporation. Ⅲ Cadenux is a trademark of Cadenux, LLC. Ⅲ ELinOS is a registered trademark of SYSGO AG. Ⅲ Metrowerks and CodeWarrior are trademarks of Metrowerks Corp. in the U.S. or other countries. Ⅲ FreeBSD is a registered trademark of the FreeBSD Foundation. Ⅲ IEEE and POSIX are registered trademarks of Institute of Electrical and Electronics Engineers, Inc. in the United States. Ⅲ Xtensa is a trademark belonging to Tensilica Inc. Ⅲ Fujitsu is a registered trademark of Fujitsu, Ltd. Ⅲ Firewire is a registered trademark of Apple computer. Ⅲ SuperH is a trademark of Hitachi, Ltd. Ⅲ Windows, WinCE and Microsoft are registered trademarks and MS-DOS and DirectX .are trademarks of Microsoft Corporation. Ⅲ Solaris and Java are registered trademarks and ChorusOS is a trademark of Sun Microsystems, Inc. in the U.S. or other countries. Ⅲ Symbian is a trademark of Symbian Ltd. Dedication Raghavan In memory of my late father Amol To Lord Krsna,... my parents, my wife Parul, and my brother Amit Sriram To my family and all Linux enthusiasts vii Contents 1 Intr oduction ............................................................................................. 1 1.1 History of Embedded Linux .................................................... 2 1.1.1 Year 1999 ..................................................................... 3 1.1.2 Year 2000 ..................................................................... 4 1.1.3 Year 2001 ..................................................................... 4 1.1.4 Year 2002 ..................................................................... 5 1.1.5 Year 2003 ..................................................................... 6 1.1.6 Year 2004 ..................................................................... 6 1.2 Why Embedded Linux? ............................................................ 7 1.2.1 Vendor Independence................................................. 7 1.2.2 Time to Market............................................................ 8 1.2.3 Varied Hardware Support ........................................... 8 1.2.4 Low Cost ...................................................................... 8 1.2.5 Open Source................................................................ 9 1.2.6 Standards (POSIX®) Compliance............................. 10 1.3 Embedded Linux Versus Desktop Linux .............................. 10 1.4 Frequently Asked Questions.................................................. 11 1.4.1 Is Linux Too Large?................................................... 11 1.4.2 Is Linux Real-Time Enough?..................................... 11 1.4.3 How Can I Protect My Proprietary Software?......... 12 1.4.4 Should I Buy a Commercial Embedded Linux Distribution?....................................................
Recommended publications
  • Operating System Boot from Fully Encrypted Device

    Operating System Boot from Fully Encrypted Device

    Masaryk University Faculty of Informatics Operating system boot from fully encrypted device Bachelor’s Thesis Daniel Chromik Brno, Fall 2016 Replace this page with a copy of the official signed thesis assignment and the copy of the Statement of an Author. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Daniel Chromik Advisor: ing. Milan Brož i Acknowledgement I would like to thank my advisor, Ing. Milan Brož, for his guidance and his patience of a saint. Another round of thanks I would like to send towards my family and friends for their support. ii Abstract The goal of this work is description of existing solutions for boot- ing Linux and Windows from fully encrypted devices with Secure Boot. Before that, though, early boot process and bootloaders are de- scribed. A simple Linux distribution is then set up to boot from a fully encrypted device. And lastly, existing Windows encryption solutions are described. iii Keywords boot process, Linux, Windows, disk encryption, GRUB 2, LUKS iv Contents 1 Introduction ............................1 1.1 Thesis goals ..........................1 1.2 Thesis structure ........................2 2 Boot Process Description ....................3 2.1 Early Boot Process ......................3 2.2 Firmware interfaces ......................4 2.2.1 BIOS – Basic Input/Output System . .4 2.2.2 UEFI – Unified Extended Firmware Interface .5 2.3 Partitioning tables ......................5 2.3.1 MBR – Master Boot Record .
  • CNTR: Lightweight OS Containers

    CNTR: Lightweight OS Containers

    CNTR: Lightweight OS Containers Jorg¨ Thalheim, Pramod Bhatotia Pedro Fonseca Baris Kasikci University of Edinburgh University of Washington University of Michigan Abstract fundamental to achieve high efficiency in virtualized datacenters and enables important use-cases, namely Container-based virtualization has become the de-facto just-in-time deployment of applications. Moreover, standard for deploying applications in data centers. containers significantly reduce operational costs through However, deployed containers frequently include a higher consolidation density and power minimization, wide-range of tools (e.g., debuggers) that are not required especially in multi-tenant environments. Because of all for applications in the common use-case, but they these advantages, it is no surprise that containers have seen are included for rare occasions such as in-production wide-spread adoption by industry, in many cases replacing debugging. As a consequence, containers are significantly altogether traditional virtualization solutions [17]. larger than necessary for the common case, thus increasing the build and deployment time. Despite being lightweight, deployed containers often include a wide-range of tools such as shells, editors, CNTR1 provides the performance benefits of lightweight coreutils, and package managers. These additional tools containers and the functionality of large containers by are usually not required for the application’s core function splitting the traditional container image into two parts: the — the common operational use-case — but they are “fat” image — containing the tools, and the “slim” image included for management, manual inspection, profiling, — containing the main application. At run-time, CNTR and debugging purposes [64]. In practice, this significantly allows the user to efficiently deploy the “slim” image and increases container size and, in turn, translates into then expand it with additional tools, when and if necessary, slower container deployment and inefficient datacenter by dynamically attaching the “fat” image.
  • White Paper: Indestructible Firewall in a Box V1.0 Nick Mccubbins

    White Paper: Indestructible Firewall in a Box V1.0 Nick Mccubbins

    White Paper: Indestructible Firewall In A Box v1.0 Nick McCubbins 1.1 Credits • Nathan Yawn ([email protected]) 1.2 Acknowledgements • Firewall-HOWTO • Linux Router Project • LEM 1.3 Revision History • Version 1.0 First public release 1.4 Feedback • Send all information and/or criticisms to [email protected] 1.5 Distribution Policy 2 Abstract In this document, the procedure for creating an embedded firewall whose root filesystem is loaded from a flash disk and then executed from a RAMdisk will be illustrated. A machine such as this has uses in many environments, from corporate internet access to sharing of a cable modem or xDSL connection among many computers. It has the advantages of being very light and fast, being impervious to filesystem corruption due to power loss, and being largely impervious to malicious crackers. The type of firewall illustrated herein is a simple packet-filtering, masquerading setup. Facilities for this already exist in the Linux kernel, keeping the system's memory footprint small. As such the device lends itself to embedding very well. For a more detailed description of firewall particulars, see the Linux Firewall-HOWTO. 3 Equipment This project has minimal hardware requirements. An excellent configuration consists of: For a 100-baseT network: • SBC-554 Pentium SBC with PISA bus and on-board PCI NIC (http://www.emacinc.com/pc.htm#pentiumsbc), approx. $373 • PISA backplane, chassis, power supply (http://www.emacinc.com/sbcpc_addons/mbpc641.htm), approx. $305 • Second PCI NIC • 32 MB RAM • 4 MB M-Systems Flash Disk (minimum), approx. $45 For a 10-baseT network: • EMAC's Standard Server-in-a-Box product (http://www.emacinc.com/server_in_a_box.htm), approx.
  • Handheld Computing Terminal Industrializing Mobile Gateway for the Internet of Things

    Handheld Computing Terminal Industrializing Mobile Gateway for the Internet of Things

    Handheld Computing Terminal Industrializing Mobile Gateway for the Internet of Things Retail Inventory Logistics Management Internet of Vehicles Electric Utility Inspection www.AMobile-solutions.com About AMobile Mobile Gateway for IIoT Dedicated IIoT, AMobile develops mobile devices and gateways for data collectivity, wireless communications, local computing and processing, and connectivity between the fields and cloud. In addition, AMobile's unified management platform-Node-Watch monitors and manages not only mobile devices but also IoT equipment in real-time to realize industrial IoT applications. Manufacturing • IPC mobile • Mobility computing technology Retail Inspection (IP-6X, Military • Premier member grade, Wide- - early access Blockchain temperature) Healthcare Logistics • Manufacturing resource pool Big Data & AI • Logistics • Global customer support Handheld Mobile Computing Data Collector Smart Meter Mobile Inspection Device with Keyboard Assistant Mobile Computing IoT Terminal Device Ultra-rugged Intelligent Barcode Reader Vehicle Mount Handheld Device Handheld Device Tablet Mobile Gateway AMobile Intelligent established in 2013, a joint venture by Arbor Technology, MediaTek, and Wistron, is Pressure Image an expert in industrial mobile computers and solutions for industrial applications including warehousing, Temperature Velocity Gyroscope logistics, manufacturing, and retail. Leveraging group resources of manufacturing and services from Wistron, IPC know-how and distribution channels from Arbor, mobility technology and
  • 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

    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
  • A Survey of Autonomous Vehicles: Enabling Communication Technologies and Challenges

    A Survey of Autonomous Vehicles: Enabling Communication Technologies and Challenges

    sensors Review A Survey of Autonomous Vehicles: Enabling Communication Technologies and Challenges M. Nadeem Ahangar 1, Qasim Z. Ahmed 1,*, Fahd A. Khan 2 and Maryam Hafeez 1 1 School of Computing and Engineering, University of Huddersfield, Huddersfield HD1 3DH, UK; [email protected] (M.N.A.); [email protected] (M.H.) 2 School of Electrical Engineering and Computer Science, National University of Sciences and Technology, Islamabad 44000, Pakistan; [email protected] * Correspondence: [email protected] Abstract: The Department of Transport in the United Kingdom recorded 25,080 motor vehicle fatali- ties in 2019. This situation stresses the need for an intelligent transport system (ITS) that improves road safety and security by avoiding human errors with the use of autonomous vehicles (AVs). There- fore, this survey discusses the current development of two main components of an ITS: (1) gathering of AVs surrounding data using sensors; and (2) enabling vehicular communication technologies. First, the paper discusses various sensors and their role in AVs. Then, various communication tech- nologies for AVs to facilitate vehicle to everything (V2X) communication are discussed. Based on the transmission range, these technologies are grouped into three main categories: long-range, medium- range and short-range. The short-range group presents the development of Bluetooth, ZigBee and ultra-wide band communication for AVs. The medium-range examines the properties of dedicated short-range communications (DSRC). Finally, the long-range group presents the cellular-vehicle to everything (C-V2X) and 5G-new radio (5G-NR). An important characteristic which differentiates each category and its suitable application is latency.
  • Current Status of Win32 Gdk Implementation

    Current Status of Win32 Gdk Implementation

    Current status of Win32 Gdk implementation Bertrand Bellenot - [email protected] Features (recall) ! Same environment on every system : ! Same look and feel on every platform. ! Simplify the code maintenance : ! No need to care about a « windows specific code ». ! Simplify functionality extension : ! No need to implement the code twice, once for windows and once for other OS. ! Only use TVirtualX. Actual Status (recall) ! The actual code uses a modified version of gdk and glib, the GIMP low-level libraries ported on win32. In practice, this means that we only need to link with gdk.lib, glib.lib and iconv.dll as additional libraries (hopefully less in the future). These libraries are under LGPL, so there are no licensing issues in using and distributing them. ! As original version of gdk was not doing everything needed by root (as font orientation!), I did have to slightly modify the original code. Points fixed since last year ! Some characters were not displayed. " ! Some problems with icon’s transparency. " ! The event handling was not perfect. " ! OpenGL was not working. " Events handling architecture (actual) TSystem CINT TGClient TVirtualX Gdk Threads issue ! From gdk developper FAQ : ! Without some major restructuring in GDK-Win32, I don't think there is any chance that GTK+ would work, in general, in a multi-threaded app, with different threads accessing windows created by other threads. ! One problem is that each thread in Windows have its own message queue. GDK-Win32 currently uses just one "message pump" in the main thread. It will never see messages for windows created by other threads. Threads issue ! As gdk is not thread safe, I had to create a separate thread from within the gdk calls are made.
  • Creating a Custom Embedded Linux Distribution for Any Embedded

    Creating a Custom Embedded Linux Distribution for Any Embedded

    Yocto Project Summit Intro to Yocto Project Creating a Custom Embedded Linux Distribution for Any Embedded Device Using the Yocto Project Behan Webster Tom King The Linux Foundation May 25, 2021 (CC BY-SA 4.0) 1 bit.ly/YPS202105Intro The URL for this presentation http://bit.ly/YPS202105Intro bit.ly/YPS202105Intro Yocto Project Overview ➢ Collection of tools and methods enabling ◆ Rapid evaluation of embedded Linux on many popular off-the-shelf boards ◆ Easy customization of distribution characteristics ➢ Supports x86, ARM, MIPS, Power, RISC-V ➢ Based on technology from the OpenEmbedded Project ➢ Layer architecture allows for other layers easy re-use of code meta-yocto-bsp meta-poky meta (oe-core) 3 bit.ly/YPS202105Intro What is the Yocto Project? ➢ Umbrella organization under Linux Foundation ➢ Backed by many companies interested in making Embedded Linux easier for the industry ➢ Co-maintains OpenEmbedded Core and other tools (including opkg) 4 bit.ly/YPS202105Intro Yocto Project Governance ➢ Organized under the Linux Foundation ➢ Split governance model ➢ Technical Leadership Team ➢ Advisory Board made up of participating organizations 5 bit.ly/YPS202105Intro Yocto Project Member Organizations bit.ly/YPS202105Intro Yocto Project Overview ➢ YP builds packages - then uses these packages to build bootable images ➢ Supports use of popular package formats including: ◆ rpm, deb, ipk ➢ Releases on a 6-month cadence ➢ Latest (stable) kernel, toolchain and packages, documentation ➢ App Development Tools including Eclipse plugin, SDK, toaster 7
  • Securing Embedded Systems: Analyses of Modern Automotive Systems and Enabling Near-Real Time Dynamic Analysis

    Securing Embedded Systems: Analyses of Modern Automotive Systems and Enabling Near-Real Time Dynamic Analysis

    Securing Embedded Systems: Analyses of Modern Automotive Systems and Enabling Near-Real Time Dynamic Analysis Karl Koscher A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy University of Washington 2014 Reading Committee: Tadayoshi Kohno, Chair Gaetano Borriello Shwetak Patel Program Authorized to Offer Degree: Computer Science and Engineering © Copyright 2014 Karl Koscher University of Washington Abstract Securing Embedded Systems: From Analyses of Modern Automotive Systems to Enabling Dynamic Analysis Karl Koscher Chair of the Supervisory Committee: Associate Professor Tadayoshi Kohno Department of Computer Science and Engineering Today, our life is pervaded by computer systems embedded inside everyday products. These embedded systems are found in everything from cars to microwave ovens. These systems are becoming increasingly sophisticated and interconnected, both to each other and to the Internet. Unfortunately, it appears that the security implications of this complexity and connectivity have mostly been overlooked, even though ignoring security could have disastrous consequences; since embedded systems control much of our environment, compromised systems could be used to inflict physical harm. This work presents an analysis of security issues in embedded systems, including a comprehensive security analysis of modern automotive systems. We hypothesize that dynamic analysis tools would quickly discover many of the vulnerabilities we found. However, as we will discuss, there
  • Camcorder Multimedia Framework with Linux and Gstreamer

    Camcorder Multimedia Framework with Linux and Gstreamer

    Camcorder multimedia framework with Linux and GStreamer W. H. Lee, E. K. Kim, J. J. Lee , S. H. Kim, S. S. Park SWL, Samsung Electronics [email protected] Abstract Application Applications Layer Along with recent rapid technical advances, user expec- Multimedia Middleware Sequencer Graphics UI Connectivity DVD FS tations for multimedia devices have been changed from Layer basic functions to many intelligent features. In order to GStreamer meet such requirements, the product requires not only a OSAL HAL OS Layer powerful hardware platform, but also a software frame- Device Software Linux Kernel work based on appropriate OS, such as Linux, support- Drivers codecs Hardware Camcorder hardware platform ing many rich development features. Layer In this paper, a camcorder framework is introduced that is designed and implemented by making use of open Figure 1: Architecture diagram of camcorder multime- source middleware in Linux. Many potential develop- dia framework ers can be referred to this multimedia framework for camcorder and other similar product development. The The three software layers on any hardware platform are overall framework architecture as well as communica- application, middleware, and OS. The architecture and tion mechanisms are described in detail. Furthermore, functional operation of each layer is discussed. Addi- many methods implemented to improve the system per- tionally, some design and implementation issues are ad- formance are addressed as well. dressed from the perspective of system performance. The overall software architecture of a multimedia 1 Introduction framework is described in Section 2. The framework design and its operation are introduced in detail in Sec- It has recently become very popular to use the internet to tion 3.
  • Enhanced Embedded Linux Board Support Package Field Upgrade – a Cost Effective Approach

    Enhanced Embedded Linux Board Support Package Field Upgrade – a Cost Effective Approach

    International Journal of Embedded Systems and Applications (IJESA), Vol 9, No.1, March 2019 Enhanced Embedded Linux Board Support Package Field Upgrade – A Cost Effective Approach Kantam Nagesh1, Oeyvind Landsnes2, Tore Fuglestad2, Nina Svensen2 and Deepak Singhal1 1ABB Ability Innovation Center, Robotics and Motion, Bengaluru, India 2ABB AS, Robotics and Motion, Bryne, Norway ABSTRACT Latest technology, new features and kernel bug fixes shows a need to explore a cost-effective and quick upgradation of Embedded Linux BSP of Embedded Controllers to replace the existing U-Boot, Linux kernel, Dtb file, and JFFS2 File system. This field upgrade technique is designed to perform an in-the-field flash upgrade while the Linux is running. On successful build, the current version and platform specific information will be updated to the script file and further with this technique the file system automates the upgrade procedure after validating for the version information from the OS-release and if the version is different it will self-extract and gets installed into the respective partitions. This Embedded Linux BSP field upgrade invention is more secured and will essentially enable the developers and researchers working in this field to utilize this method which can prove to be cost-effective on the field and beneficial to the stake holder. KEYWORDS Embedded Linux, Upgrade, Kernel, U-boot, JFFS2 File system. INTRODUCTION Embedded systems form an essential part of the connected world. 1, 2 BSP (Board Support Package) is a collection of binary code and supported files which are used to create a Linux kernel firmware and filesystem images for a particular target.
  • National Semiconductor Is Pleased to Bring You This Kit in Cooperation with the Following Partners

    National Semiconductor Is Pleased to Bring You This Kit in Cooperation with the Following Partners

    September 2001 Revision 1.0 Introducing Our Partners National Semiconductor is pleased to bring you this kit in cooperation with the following partners: Century Software Century Software, a fifteen-year veteran in the software industry, has developed core technologies for the new and fast-paced embedded Linux industry. These technologies include: a graphical develop- ment environment; customized Internet browsers and HTML viewers; multimedia, including MP3 audio players and MPEG video viewers; and a PDA development suite. These core technologies were designed specifically to allow both hardware designers and their customers to use either a small footprint graphical API (Microwindows), or the larger and more complex X-Window system, while maintaining compatibility with upper-level applications. Our technologies center around two core open source projects, Microwindows and ViewML. http://www.centurysoftware.com Datalight A world leader in embedded system software since 1983, Datalight has over 15 years of experience in developing reliable, small-footprint system software. In that time, Datalight has earned a reputation for providing ultra-compact, turnkey software solutions for OEMs of dedicated and multi-purpose information appliances from various industries worldwide. Hidden almost everywhere, Datalight soft- ware can be found in products representing: Computer Telephony, Electronic Data Interchange, Thin Clients, Point-of-Sale Systems, Medical Equipment, Single Board Computers, Gaming/ Entertain- ment Systems, Diagnostics and many more. http://www.datalight.com DT Research DT Research is an industry-leading provider of information access devices featured in a wide range of commercial and consumer deployments involving Intranet access, Internet connectivity, and offline applications. These display-centric systems emphasize wireless connectivity together with hardware and software integration to offer mobility, functionality and superior user experience on a thin client platform.