DOCSLIB.ORG

Embedded Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Embedded Systems Embedded Systems Altera NIOS II Software Development: Part I Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-1 Overview • NIOS II programs and associated projects – Applications – User libraries – Board support packages (BSPs) • Programming a NIOS II system – User programs – C standard library – Hardware abstraction layer (HAL) and HAL layers – Device drivers • HAL Architecture and Services • Developing Programs Using the HAL Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-2 1 NIOS II Programs • Each NIOS II program consists of: – an application project, – optional user library projects, and – a board support package (BSP) project • The build process creates an Executable and Linking Format File (.elf) which runs on a NIOS II processor. Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-3 NIOS II Software Project Types: Application Project • A NIOS II C/C++ application project consists of a collection of source code, plus a makefile • A typical characteristic of an application is that one of the source files contains function main() • An application includes code that calls functions in libraries and BSPs • The makefile contains commands to: – compile the source code – link it with a BSP and one or more optional libraries – create one .elf file Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-4 2 NIOS II Software Project Types: User Library Project • A user library project is a collection of source code compiled to create a single library archive file (.a) – Libraries often contain reusable, general purpose functions that multiple application projects can share – A collection of common arithmetical functions is one example • A user library does not contain a main() function Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-5 NIOS II Software Project Types: BSP Project • A NIOS II BSP project is a specialized library containing system-specific support code • A BSP provides a software runtime environment customized for one processor in an SOPC Builder system • The NIOS II EDS provides tools to modify settings that control the behavior of the BSP • A BSP contains the following elements: – Hardware abstraction layer – Newlib C standard library – Device drivers – Optional software packages – Optional real-time operating system Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-6 3 Overview of the Hardware Abstraction Layer • The HAL provides a simple device driver interface for programs to connect to the underlying hardware • The HAL application program interface (API) is integrated with the ANSI C standard library • The HAL API allows access to devices and files using familiar C library functions – printf(), fopen(), fwrite(), etc. • The HAL serves as a device driver package for NIOS II processor systems – provides a consistent programming interface to the peripherals in a NIOS II system Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-7 HAL Architecture and Services • Integration with the newlib ANSI C standard library – Provides the familiar C standard library functions • Device drivers – Provides access to each device in the system • The HAL API – Provides a consistent, standard interface to HAL services, such as device access, interrupt handling, and alarm facilities • System initialization – Performs initialization tasks for the processor and the runtime environment before main() • Device initialization – Initializes each device in the system before main() runs Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-8 4 Layers of a HAL-Based System Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-9 HAL Generic Device Models • The HAL provides generic device models for classes of peripherals found in embedded systems – timers, Ethernet MAC/PHY chips, and I/O peripherals that transmit character data, etc. • Generic device models allow programs to use a consistent API, regardless of the underlying hardware Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-10 5 HAL Device Model Classes • Character-mode devices – Hardware peripherals that send and/or receive characters serially, such as a UART. • Timer devices – Hardware peripherals that count clock ticks and can generate periodic interrupt requests. • File subsystems – A mechanism for accessing files stored in physical device(s) • Ethernet devices – Devices that provide access to an Ethernet connection for a networking stack • Direct memory access (DMA) devices – Peripherals that perform bulk data transactions from a data source to a destination • Flash memory devices – Nonvolatile memory devices that use a special programming protocol to store data Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-11 HAL Peripherals • All peripherals must have a header file that defines the peripheral’s low-level interface to hardware • Therefore, all peripherals support the HAL to some extent • However, some peripherals might not provide device drivers • If drivers are not available, use only the definitions provided in the header files to access the hardware • Some peripherals provide functions that are not based on the HAL generic device models – For example, Altera provides a general-purpose parallel I/O (PIO) core for use with the NIOS II processor system – The PIO peripheral does not fit in any class of generic device models provided by the HAL, and so it provides a header file and a few dedicated functions only – User pushbuttons and LEDs are examples of these Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-12 6 Developing Programs Using The HAL • NIOS II Development Flows – The NIOS II Embedded Design Suite (EDS) provides two distinct development flows for creating NIOS II programs • NIOS II Software Build Tools (SBT for Eclipse or command line) • NIOS II Integrated Development Environment (IDE) • HAL BSP Settings – Every NIOS II board support package (BSP) has settings that determine the BSP’s characteristics – For example, HAL BSPs have settings to identify the hardware components associated with standard devices such as stdout • Defining and manipulating BSP settings is an important part of NIOS II project creation • BSP settings can be modified with the NIOS II BSP Editor, with command-line options, or with Tcl scripts Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-13 The NIOS II HAL Project Structure Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-14 7 The NIOS II HAL Project Structure • Every HAL-based NIOS II program consists of two NIOS II projects – Your application-specific code is contained in one project (the user application project), and – it depends on a separate BSP project (the HAL BSP). • The application project contains all the code you develop • The executable image for your program ultimately results from building both projects • With the NIOS II Software Build Tools for Eclipse, the tools create the HAL BSP project when you create your application project • The BSP project depends on the SOPC Builder system, defined by a SOPC Information File (.sopcinfo) – The SOPC file is created using the SPOC Builder tool within the Altera Quartus software Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-15 The system.h System Description File • The system.h file provides a complete software description of the NIOS II system hardware • The system.h file describes each peripheral in the system and provides: – The hardware configuration of the peripheral – The base address – Interrupt request (IRQ) information (if any) – A symbolic name for the peripheral Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-16 8 Excerpts from a system.h File Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-17 Data Widths and the HAL Type Definitions • For embedded processors such as the NIOS II processor, it is often important to know the exact width and precision of data • Because the ANSI C data types do not explicitly define data width, the HAL uses a set of standard type definitions instead • The ANSI C types are supported, but their data widths are dependent on the compiler’s convention • The header file alt_types.h defines the HAL type definitions Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-18 9 The HAL and GNU Toolchain Type Definitions and Data Widths Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-19 UNIX-Style Interface • The HAL API provides a number of UNIX-style functions – The UNIX-style functions provide a familiar development environment for new NIOS II programmers – Can ease the task of porting existing code to run in the HAL environment • The HAL uses these functions primarily to provide the system interface for the ANSI C standard library – For example, the functions perform device access required by the C library functions defined in stdio.h. Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson Lecture 5-20 10 Available UNIX-style Functions • _exit() • open() • close() • read() • fstat() • sbrk() • getpid() • settimeofday() • gettimeofday() • stat() • ioctl() • usleep() • isatty() • wait() • kill() • write() • lseek() Electrical & Computer Engineering – Embedded Systems Dr. Jeff Jackson
Load more

Recommended publications
  • A Survey on Architectures of Mobile Operating Systems: Challenges and Issues
    International Journal of Research Studies in Computer Science and Engineering (IJRSCSE) Volume 2, Issue 3, March 2015, PP 73-76 ISSN 2349-4840 (Print) & ISSN 2349-4859 (Online) www.arcjournals.org A Survey on Architectures of Mobile Operating Systems: Challenges and Issues Prof. Y. K. Sundara Krishna1 HOD, Dept. of Computer Science, Krishna University Mr. G K Mohan Devarakonda2 Research Scholar, Krishna University Abstract: In the early years of mobile evolution, Discontinued Platforms Current mobile devices are enabled only with voice services Platforms that allow the users to communicate with each other. Symbian OS Android But now a days, the mobile technology undergone Palm OS IOS various changes to a great extent so that the devices Maemo OS Windows Phone allows the users not only to communicate but also to Meego OS Firefox OS attain a variety of services such as video calls, faster Black Berry OS browsing services,2d and 3d games, Camera, 2.1 Symbian OS: This Operating system was Banking Services, GPS services, File sharing developed by NOKIA. services, Tracking Services, M-Commerce and so many. The changes in mobile technology may be due Architecture: to Operating System or Hardware or Network or Memory. This paper presents a survey on evolutions SYMBIAN OS GUI Library in mobile developments especially on mobile operating system Architectures, challenges and Issues in various mobile operating Systems. Application Engines JAVA VM 1. INTRODUCTION Servers (Operating System Services) A Mobile operating system is a System Software that is specifically designed to run on handheld devices Symbian OS Base (File Server, Kernel) such as Mobile Phones, PDA’s.
    [Show full text]
  • Windows NT Architecture Previous Screen Gilbert Held Payoff Windows NT Is a Sophisticated Operating System for Workstations and Network Servers
    50-30-19 Windows NT Architecture Previous screen Gilbert Held Payoff Windows NT is a sophisticated operating system for workstations and network servers. This article helps network managers to understand the communications capability of workstations and servers running on Windows NT, and data base administrators to determine the suitability of this platform for a structured query language (SQL) data base server. Introduction Windows NT is a 32-bit, preemptive multitasking operating system that includes comprehensive networking capabilities and several levels of security. Microsoft markets two version of Windows NT: one for workstations—appropriately named Windows NT Workstation—and a second for servers—Windows NT Server. This article, which describes the workings of the NT architecture, collectively references both versions as Windows NT when information is applicable to both versions of the operating system. Similarly, it references a specific version of the operating system when the information presented is specific to either Windows NT Workstation or Windows NT Server. Architecture Windows NT consists of nine basic modules. The relationship of those modules to one another, as well as to the hardware platform on which the operating system runs, is illustrated in Exhibit 1. Windows NT Core Modules Hardware Abstraction Layer The hardware abstraction layer (HAL) is located directly above the hardware on which Windows NT operates. HAL actually represents a software module developed by hardware manufacturers that is bundled into Windows NT to allow it to operate on a specific hardware platform, such as Intel X86, DEC Alpha, or IBM PowerPC. HAL hides the specifics of the hardware platform from the rest of the operating system and represents the lowest level of Windows NT.
    [Show full text]
  • Mobile Systems
    CS 318 Principles of Operating Systems Fall 2017 Lecture 21: Mobile Systems Ryan Huang 11/30/17 CS 318 – Lecture 21 – Mobile Systems 2 Apply the security update immedidately! CS 318 – Lecture 21 – Mobile Systems Administrivia • Lab 4 deadline one week away • Groups of 2 students receive 2-day extra late hour • Groups of 3 students with 1 318 section student receive 1-day extra late-hour • Please, please don’t cheat • Homework 5 is released 11/30/17 CS 318 – Lecture 21 – Mobile Systems 4 Mobile Devices Become Ubiquitous Worldwide Devices Shipments by Device Type (Millions of Units) 3000 2500 2000 1500 1806.96 1879 1910 1959 1000 500 Google Nexus 6P 209.79 226 196 195 296.13 277 246 232 0 2013 2014 2015 2016 Traditional PCs Ultramobiles (Premium) Ultramobiles (Basic and Utility) Mobile Phones 5 History of Mobile OS (1) • Early “smart” devices are PDAs (touchscreen, Internet) • Symbian, first modern mobile OS - released in 2000 - run in Ericsson R380, the first ‘smartphone’ (mobile phone + PDA) - only support proprietary programs 11/30/17 CS 318 – Lecture 21 – Mobile Systems 6 History of Mobile OS (2) • Many smartphone and mobile OSes followed up - Kyocera 6035 running Palm OS (2001) • 8 MB non-expandable memory - Windows CE (2002) - Blackberry (2002) • was a prominent vendor • known for secure communications - Moto Q (2005) - Nokia N70 (2005) • 2-megapixel camera, bluetooth • 32 MB memory • Symbian OS • Java games 11/30/17 CS 318 – Lecture 21 – Mobile Systems 7 One More Thing… • Introduction of iPhone (2007) - revolutionize the smartphone industry - 4GB flash memory, 128 MB DRAM, multi-touch interface - runs iOS, initially only proprietary apps - App Store opened in 2008, allow third party apps 11/30/17 CS 318 – Lecture 21 – Mobile Systems 8 Android – An Unexpected Rival of iPhone • Android Inc.
    [Show full text]
  • 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
    [Show full text]
  • Windows XP History and Versions
    Lecture 23: Windows XP History and Versions n Mid-80ies Microsoft and IBM cooperated to develop OS/2 n Windows XP is produced by Microsoft Co. n 1988 - Microsoft started to develop its own new technology (NT) OS n XP is multi-user, multi-process, preemptive multitasking OS, 30M lines of source code capable of running OS/2, Windows and Unix apps. Hired Dave Cutler - architect of DEC VAX/VMS to head the design n It is developed to support multiple platforms and targeted towards enterprise workstations and server market as well as n NT v. 3.1 first released commercially July 1993 desktops n NT v 4.0 adopted Windows 95 user interface, graphics code moved into kernel to improve performance n In today’s lecture n 2000 – improved networking and laptop support, support for plug-and- u XP’s predecessors, the history of XP design, XP versions play devices, support for more processors (up to 8) and memory, u design principles becomes true multi-user through terminal server u components n XP (released Oct 2001) – update for 2000 replacement for 95/98 F hardware abstraction layer u simplifies user interface, improved reliability, performance F executive improvements, partial 64-bit support F environmental subsystems n versions F file system u desktop: XP personal – 95/98 replacement, professional – advanced features like POSIX support, some network features 1 u server: .NET – support for web/print service, clusters, large memory2 and multiple processors Design goals Components n XP is microkernel-based, modular n security – NT was C-2 certified (US
    [Show full text]
  • A Hardware Abstraction Layer in Java
    A Hardware Abstraction Layer in Java MARTIN SCHOEBERL Vienna University of Technology, Austria STEPHAN KORSHOLM Aalborg University, Denmark TOMAS KALIBERA Purdue University, USA and ANDERS P. RAVN Aalborg University, Denmark Embedded systems use specialized hardware devices to interact with their environment, and since they have to be dependable, it is attractive to use a modern, type-safe programming language like Java to develop programs for them. Standard Java, as a platform independent language, delegates access to devices, direct memory access, and interrupt handling to some underlying operating system or kernel, but in the embedded systems domain resources are scarce and a Java virtual machine (JVM) without an underlying middleware is an attractive architecture. The contribution of this paper is a proposal for Java packages with hardware objects and interrupt handlers that interface to such a JVM. We provide implementations of the proposal directly in hardware, as extensions of standard interpreters, and finally with an operating system middleware. The latter solution is mainly seen as a migration path allowing Java programs to coexist with legacy system components. An important aspect of the proposal is that it is compatible with the Real-Time Specification for Java (RTSJ). Categories and Subject Descriptors: D.4.7 [Operating Systems]: Organization and Design—Real-time sys- tems and embedded systems; D.3.3 [Programming Languages]: Language Classifications—Object-oriented languages; D.3.3 [Programming Languages]: Language Constructs and Features—Input/output General Terms: Languages, Design, Implementation Additional Key Words and Phrases: Device driver, embedded system, Java, Java virtual machine 1. INTRODUCTION When developing software for an embedded system, for instance an instrument, it is nec- essary to control specialized hardware devices, for instance a heating element or an inter- ferometer mirror.
    [Show full text]
  • Operating Systems Principles Design and Implementation Policies And
    Betriebssysteme ws2000/2001 Operating Systems Principles Design and Implementation Policies and Mechanisms S 2004 CS325 1 Textbook: L.Bic and A.C Shaw: "Operating Systems Principles" Other references: • A.S. Tanenbaum, „Modern Operating Systems“, Prentice-Hall • Other references – see web site: cs.nmt.edu/~cs325 S 2004 CS325 2 Prof. H. D. Clausen 1 Betriebssysteme ws2000/2001 Simple hardware configuration control CPU data addres s controller controller main memory device_1 device_2 user IO subsystem S 2004 CS325 3 Typical hardware configuration main CPU memory IOC IOC/PPU controller controller controller controller device device device S 2004 CS325 4 Prof. H. D. Clausen 2 Betriebssysteme ws2000/2001 Processor performance This chart plots relative performance as measured by the SPECint benchmarks with base of one being a VAX 11/780. S 2004 CS325 5 Memory cost Prices of DRAMs (from 16K bits to 64M bits) over time in 1977 dollars. S 2004 CS325 6 Prof. H. D. Clausen 3 Betriebssysteme ws2000/2001 API application program application support API SVC SysCall systems programs kernel programs SW CISC driver programs RISC HW S 2004 CS325 7 Principle of abstraction • Higher-level function: – Read( file, logical_block, main_memory ) • Lower-level functions – Calculate position of logical_block on the disk; – Move Read/Write head to corresponding track; – Check for „seek“ errors; – Read physical block; – Check for „read“ errors; – Copy block to main_memory; S 2004 CS325 8 Prof. H. D. Clausen 4 Betriebssysteme ws2000/2001 Principle of abstraction extended
    [Show full text]
  • Modeling of Hardware and Software for Specifying Hardware Abstraction
    Modeling of Hardware and Software for specifying Hardware Abstraction Layers Yves Bernard, Cédric Gava, Cédrik Besseyre, Bertrand Crouzet, Laurent Marliere, Pierre Moreau, Samuel Rochet To cite this version: Yves Bernard, Cédric Gava, Cédrik Besseyre, Bertrand Crouzet, Laurent Marliere, et al.. Modeling of Hardware and Software for specifying Hardware Abstraction Layers. Embedded Real Time Software and Systems (ERTS2014), Feb 2014, Toulouse, France. hal-02272457 HAL Id: hal-02272457 https://hal.archives-ouvertes.fr/hal-02272457 Submitted on 27 Aug 2019 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Modeling of Hardware and Software for specifying Hardware Abstraction Layers Yves BERNARD1, Cédric GAVA2, Cédrik BESSEYRE1, Bertrand CROUZET1, Laurent MARLIERE1, Pierre MOREAU1, Samuel ROCHET2 (1) Airbus Operations SAS (2) Subcontractor for Airbus Operations SAS Abstract In this paper we describe a practical approach for modeling low level interfaces between software and hardware parts based on SysML operations. This method is intended to be applied for the development of drivers involved on what is classically called the “hardware abstraction layer” or the “basic software” which provide high level services for resources management on the top of a bare hardware platform.
    [Show full text]
  • Flexible Hardware Abstraction for Wireless Sensor Networks
    Flexible Hardware Abstraction for Wireless Sensor Networks Vlado Handziski∗, Joseph Polastrey, Jan-Hinrich Hauer∗, Cory Sharpy, Adam Wolisz∗ and David Cullery ∗Technische Universitat¨ Berlin; Telecommunication Networks Group Sekr. FT 5, Einsteinufer 25, 10587 Berlin, GERMANY yUniversity of California, Berkeley; Computer Science Department Berkeley, CA 94720 US Abstract— We present a flexible Hardware Abstraction Our analysis of several embedded and general- Architecture (HAA) that balances conflicting requirements purpose operating systems (eCos [1], WindowsCE [2], of Wireless Sensor Networks (WSNs) applications and the NetBSD [3] and Linux[4]) that have mature hardware ab- desire for increased portability and streamlined develop- straction architectures has shown us that existing designs ment of applications. Our three-layer design gradually are poorly suited to the flexible abstraction required by adapts the capabilities of the underlying hardware plat- forms to the selected platform-independent hardware inter- WSNs. Their interfaces are rigid and expose the capa- face between the operating system core and the application bilities of the hardware at a single level of abstraction, code. At the same time, it allows the applications to utilize preventing an application from taking full advantage of a platform’s full capabilities – exported at the second layer, the hardware’s capabilities when needed. when the performance requirements outweigh the need for Thus, we need a better Hardware Abstraction Archi- cross-platform compatibility. We demonstrate the practical tecture (HAA) that can strike a balance between the value of our approach by presenting how it can be applied two conflicting goals that are present in the WSNs to the most important hardware modules that are found context.
    [Show full text]
  • 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.
    [Show full text]
  • A Real Time Operating System on the Raspberry Pi
    EPiC Series in Computing Volume 58, 2019, Pages 8{16 Proceedings of 34th International Confer- ence on Computers and Their Applications RealPi - A Real Time Operating System on the Raspberry Pi Samuel Delaney, Dwight Egbert, and Frederick C. Harris, Jr. Department of Computer Science and Engineering, University of Nevada Reno, NV 89557, USA [email protected] [email protected] [email protected] Abstract Academia has always sought to ride the line between established thought and new developments. No much more so than in the terms of technology. Universities seek to teach using known and proven methods and resources but also stay relevant with new technologies to provide students the knowledge they will need to be competitive in the work place or graduate field. In this work we will present how the University of Nevada approaches this problem with its Real Time Operating system course. Namely on how using the established Micro C/OS II Real time Operating System with the new builder phenomena the Raspberry Pi we can overcome the challenge of updating a tried and true lesson plan in order to use technology relevant and interesting to the students of today. 1 Introduction All Computer Science and Computer Engineering disciples have encountered the \real time" catchphrase at least once in their career. Whether that experience equates to a simple buzz word or a fundamental understanding is beyond the scope of this article but none the less the concept has a claim to key concepts in the computing world. As technology has advanced and computers become faster and more efficient they allow us more room to error in our programming and still produce acceptable response times.
    [Show full text]
  • AVR32737: AVR32 AP7 Linux Getting Started
    AVR32737: AVR32 AP7 Linux Getting Started Features 32-bit • Linux development tools overview • Introduction to the Linux boot process Microcontrollers • Compiling, running and debugging applications 1 Introduction Application Note This application note is aimed at helping the reader become familiar with Linux® development with the Atmel AVR®32 AP7 Application Processor. Rev. 32091A-AVR32-02/08 2 Development Tools The software provided with this application note requires the following components to be available. 2.1 Your personal computer (PC) Developing Linux applications for embedded systems is most conveniently done on a Linux development host. It is recommended that developers install, use and become familiar with Linux on the Desktop PC. This can typically be done through the use of a pre-made Virtual Machine image running inside the existing operating system or by installing a Linux distribution (Ubuntu, Fedora, Debian or other) in a dual-boot configuration on the PC. 2.2 AVR32 Linux BSP The AVR32 Linux BSP is a collection of everything you need to start Linux development on the AVR32 AP7 platform. It includes the AVR32 GNU Toolchain, the Linux kernel, the U-Boot boot loader as well as an assortment of useful applications. It also comes with a set of scripts to rebuild the whole environment from scratch. 2.2.1 Buildroot Buildroot is an open-source project, used by Atmel to build its Linux board support packages for development kits and reference designs. Buildroot is a configurable and fully automated build system for embedded systems. The main idea is that the user selects what he wants installed on the system, and buildroot takes care of compiling everything from sources, creating a custom file system image that can be programmed into flash, put on an MMC/SD card, or unpacked on an NFS server.
    [Show full text]