DOCSLIB.ORG

RTEMS User Manual Release 6.7B289f6 (23Th September 2021) © 1988, 2020 RTEMS Project and Contributors

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
RTEMS User Manual Release 6.7B289f6 (23Th September 2021) © 1988, 2020 RTEMS Project and Contributors RTEMS User Manual Release 6.7b289f6 (23th September 2021) © 1988, 2020 RTEMS Project and contributors CONTENTS 1 Introduction 3 1.1 Overview........................................4 1.2 Features.........................................5 1.3 Ecosystem.......................................8 1.3.1 Rational....................................8 1.3.2 Open Source..................................9 1.3.3 Deployment..................................9 1.4 Real-time Application Systems............................ 10 1.5 Real-time Executive.................................. 11 2 Quick Start 13 2.1 Preparation....................................... 14 2.1.1 Host Computer................................ 14 2.1.2 Selecting a BSP................................ 14 2.1.3 Selecting a Version of RTEMS........................ 15 2.2 Choose an Installation Prefix............................. 16 2.3 Obtain the Sources................................... 17 2.3.1 Releases.................................... 17 2.3.2 Git....................................... 18 2.3.3 Offline Download............................... 18 2.4 Install the Tool Suite.................................. 19 2.4.1 Need for RTEMS-Specific Cross-Compiler.................. 20 2.5 Build a Board Support Package (BSP)........................ 21 2.5.1 RSB BSP Build................................. 21 2.5.2 Manual BSP Build............................... 22 2.6 Test a Board Support Package (BSP)......................... 25 2.7 Build Your Application................................. 27 2.8 Build an RSB Package................................. 31 2.8.1 RTEMS Packages............................... 31 2.8.2 BSP Stack Build................................ 31 2.8.3 Package Build................................. 33 2.9 GSoC Getting Started................................. 34 2.9.1 Installing Dependencies........................... 34 2.9.2 Choosing an installation prefix........................ 34 2.9.3 Downloading the Sources.......................... 35 2.9.4 Installing the Tool Suite........................... 35 2.9.5 Building the Board Support Package.................... 35 2.9.6 Testing the Board Support Package..................... 35 i 2.9.7 Prove You Can Work On RTEMS....................... 35 2.9.8 Creating and Sending Patches........................ 36 3 Support and Contributing 37 3.1 RTEMS Project Support................................ 38 3.1.1 Users Mailing List............................... 38 3.1.2 Documentation................................ 38 3.1.3 All Mailing Lists................................ 38 3.1.4 IRC....................................... 38 3.2 Report Bugs...................................... 39 3.2.1 Search for Existing Bugs........................... 39 3.2.2 Not RTEMS Bugs............................... 39 3.2.3 Good Bug Reports............................... 40 3.2.4 Nobody Fixes my Bug............................. 41 3.3 Contributing...................................... 42 3.3.1 How to Contribute?.............................. 42 3.3.2 Preparing and Sending Patches....................... 42 3.3.3 Checklist for Patches............................. 42 3.3.4 Patch Review Process............................. 43 3.3.5 Why Contribute?............................... 43 3.3.6 Common Questions and Answers...................... 45 3.4 Commercial Support Services............................. 47 4 Host Computer 49 4.1 Python......................................... 50 4.1.1 Virtual Environment............................. 50 4.1.2 Symbolic Link................................. 51 4.1.3 Directly Invoking Python........................... 51 4.2 Host Operating Systems................................ 52 4.3 POSIX Hosts...................................... 54 4.3.1 Root Access.................................. 54 4.3.2 Linux...................................... 54 4.3.2.1 ArchLinux.............................. 54 4.3.2.2 CentOS................................ 55 4.3.2.3 Fedora................................ 55 4.3.2.4 Raspbian............................... 55 4.3.2.5 Ubuntu................................ 55 4.3.2.6 Linux Mint.............................. 56 4.3.2.7 openSUSE.............................. 56 4.3.3 FreeBSD.................................... 56 4.3.4 NetBSD.................................... 57 4.4 Apple macOS...................................... 58 4.4.1 Catalina.................................... 58 4.4.2 Sierra..................................... 58 4.4.3 Mavericks................................... 58 4.5 Microsoft Windows.................................. 59 4.5.1 Windows Path Length............................. 59 4.5.2 Windows Spaces In Paths........................... 59 4.5.3 Parallel Builds with Make.......................... 60 4.5.4 POSIX Support................................ 60 4.5.5 Python..................................... 60 4.5.6 MSYS2..................................... 61 ii 4.5.7 Cygwin..................................... 62 5 Installation 65 5.1 Releases......................................... 66 5.1.1 RTEMS Tools and Kernel........................... 67 5.2 Developer (Unstable)................................. 73 5.2.1 POSIX and OS X Host Tools Chain...................... 73 5.2.2 Windows Host Tool Chain.......................... 78 5.2.2.1 RTEMS Windows Tools....................... 78 5.2.2.2 Building the Kernel......................... 82 5.3 RTEMS Kernel..................................... 87 5.3.1 Development Sources............................. 87 5.3.2 Tools Path Set Up............................... 87 5.3.3 Bootstrapping................................. 87 5.3.4 Building a BSP................................ 88 5.3.5 Installing A BSP................................ 91 5.3.6 Contributing Patches............................. 92 5.4 Project Sandboxing.................................. 94 6 Target Hardware 97 6.1 Targets......................................... 98 6.2 Architectures...................................... 99 6.3 Tiers.......................................... 101 7 BSP Build System 103 7.1 Overview........................................ 104 7.2 Work Flow....................................... 105 7.3 Commands....................................... 106 7.3.1 Help...................................... 106 7.3.2 BSP List.................................... 106 7.3.3 BSP Defaults.................................. 106 7.3.4 Configure................................... 107 7.3.5 Build, Clean, and Install........................... 107 7.4 Configuration..................................... 108 7.5 Migration from Autoconf/Automake......................... 110 8 Board Support Packages 113 8.1 aarch64 (AArch64).................................. 114 8.1.1 Qemu A53................................... 114 8.1.1.1 Boot via ELF............................. 114 8.1.1.2 Clock Driver............................. 114 8.1.1.3 Console Driver............................ 114 8.1.1.4 Running Executables......................... 114 8.1.2 Qemu A72................................... 114 8.1.2.1 Boot via ELF............................. 114 8.1.2.2 Clock Driver............................. 114 8.1.2.3 Console Driver............................ 115 8.1.2.4 Running Executables......................... 115 8.1.3 Qemu Xilinx Versal.............................. 115 8.1.3.1 Boot via ELF............................. 115 8.1.3.2 Clock Driver............................. 115 8.1.3.3 Console Driver............................ 115 iii 8.1.3.4 Running Executables......................... 115 8.1.4 Qemu Xilinx ZynqMP............................. 116 8.1.4.1 Boot on QEMU............................ 116 8.1.4.2 Boot on ZynqMP Hardware..................... 116 8.1.4.3 Hardware Boot Image Generation................. 116 8.1.4.4 Clock Driver............................. 116 8.1.4.5 Console Driver............................ 116 8.1.4.6 SDHCI Driver............................. 117 8.1.4.7 Network Configuration....................... 117 8.1.4.8 Running Executables on QEMU................... 117 8.2 arm (ARM)....................................... 118 8.2.1 altera-cyclone-v (Intel Cyclone V)...................... 118 8.2.1.1 Boot via U-Boot........................... 118 8.2.1.2 Clock Driver............................. 118 8.2.1.3 Console Driver............................ 118 8.2.1.4 I2C Driver.............................. 119 8.2.1.5 Network Interface Driver...................... 119 8.2.1.6 MMC/SDCard Driver........................ 119 8.2.1.7 USB Host Driver........................... 119 8.2.1.8 Caveats................................ 119 8.2.2 atsam..................................... 119 8.2.3 beagle..................................... 119 8.2.3.1 Boot via U-Boot........................... 120 8.2.3.2 Getting the Device Tree Blob.................... 120 8.2.3.3 Writing the uEnv.txt file....................... 120 8.2.3.4 I2C Driver.............................. 120 8.2.3.5 SPI Driver............................... 121 8.2.3.6 Debugging using libdebugger.................... 121 8.2.3.7 Debugging Beagle Bone Black using a JTAG debugger and gdb. 122 8.2.4 stm32h7.................................... 123 8.2.4.1 Clock Driver............................. 124 8.2.4.2 Console Driver............................ 124 8.2.4.3 Network Interface Driver...................... 124 8.2.4.4 USB Host Driver........................... 124 8.2.5 csb336..................................... 124 8.2.6 csb337..................................... 124 8.2.7
Load more

Recommended publications
  • PL/SQL Multi-Diagrammatic Source Code Visualization
    SQLFlow: PL/SQL Multi-Diagrammatic Source Code Visualization Samir Tartir Ayman Issa Department of Computer Science University of the West of England (UWE), University of Georgia Coldharbour Lane, Frenchay, Bristol BS16 1QY Athens, Georgia 30602 United Kingdom USA Email: [email protected] Email: [email protected] ABSTRACT: A major problem in software introducing new problems to other code that was perfectly maintenance is the lack of a well-documented source code working before. Therefore, educating programmers about in software applications. This has led to serious the behaviors of the target code before start modifying it difficulties in software maintenance and evolution. In is not an easy task. Source code visualization is one of the particular, for those developers who are faced with the heavily used techniques in the literature to overcome this task of fixing or modifying a piece of code they never lack of documentation problem, and its consequent even knew existed before. Database triggers and knowledge-sharing problem [7, 9]. procedures are parts of almost every application, are typical examples of badly documented software Therefore, this research aims at investigating the current components being the hidden back end of software database source code visualization tools and identifying applications. Source code visualization is one of the the main open issues for research. Consequently, the heavily used techniques in the literature so as to mostly used PL/SQL database programming language has familiarize software developers with new source code, been selected for a flowcharting reverse engineering and compensate for the knowledge-sharing problem. prototype tool called "SQLFlow". SQLFlow has been Therefore, a new PL/SQL flowcharting reverse designed, implemented, and tested to parse the target engineering tool, SQLFlow, has been designed and PL/SQL code stored in database procedures, analyze its developed.
    [Show full text]
  • Buildbot: a Continuous Integration System
    Buildbot: A continuous integration system Krzysztof Voss January, 2013 Outline • Testing and Continuous Integration • Introduction to Buildbot • BuildMaster • BuildMaster components • BuildSlave • Installation and Usage 1 Testing and continuous integration Tests: • the best specification • safety-net for refactoring • bug identification Tests are the most effective if we: • run them often • run them on different machines/environments • can easily see their results 2 The most straightforward approach would entail: • logging in to different machines • fetching the newest source code • running tests • analyzing their output In case we want to test a few environments, repeating the above steps is tedious. Developers do not focus on the code, instead they run tests. A continuous integration system performs all of these steps for us, so developers can focus on their code. 3 Introduction to Buildbot: Features • run builds on a variety of BuildSlave platforms • arbitrary build process: handles projects using C, Python, . • minimal host requirements: python and Twisted • BuildSlave can be behind a firewall if they can still do checkout • status delivery through web page, email, IRC, other protocols • track builds in progress, provide estimated completion time • flexible configuration by subclassing generic build process classes 4 • debug tools to force a new build, submit fake Changes, query BuildSlave status • released under the GPL source: http://buildbot.net/buildbot/docs/current/manual/introduction.html 5 Introduction to Buildbot: Overview system overview source: http://buildbot.net/buildbot/docs/0.8.1/full.html 6 BuildMaster BuildMaster components source: http://buildbot.net/buildbot/docs/0.8.1/full.html 7 BuildMaster BuildMaster: • holds the configuration of the entire system.
    [Show full text]
  • A Prolog-Based Proof Tool for Type Theory Taλ and Implicational Intuitionistic-Logic
    A Prolog-based Proof Tool for Type Theory TAλ and Implicational Intuitionistic-Logic L. Yohanes Stefanus University of Indonesia Depok 16424, Indonesia [email protected] and Ario Santoso∗ Technische Universit¨atDresden Dresden 01187, Germany [email protected] Abstract Studies on type theory have brought numerous important contributions to computer science. In this paper we present a GUI-based proof tool that provides assistance in constructing deductions in type theory and validating implicational intuitionistic-logic for- mulas. As such, this proof tool is a testbed for learning type theory and implicational intuitionistic-logic. This proof tool focuses on an important variant of type theory named TAλ, especially on its two core algorithms: the principal-type algorithm and the type inhabitant search algorithm. The former algorithm finds a most general type assignable to a given λ-term, while the latter finds inhabitants (closed λ-terms in β-normal form) to which a given type can be assigned. By the Curry{Howard correspondence, the latter algorithm provides provability for implicational formulas in intuitionistic logic. We elab- orate on how to implement those two algorithms declaratively in Prolog and the overall GUI-based program architecture. In our implementation, we make some modification to improve the performance of the principal-type algorithm. We have also built a web-based version of the proof tool called λ-Guru. 1 Introduction In 1902, Russell revealed the inconsistency in naive set theory. This inconsistency challenged the foundation of mathematics at that time. To solve that problem, type theory was introduced [1, 5]. As time goes on, type theory becomes widely used, it becomes a logician's standard tool, especially in proof theory.
    [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]
  • Overrun Handling for Mixed-Criticality Support in RTEMS Kuan-Hsun Chen, Georg Von Der Brüggen, Jian-Jia Chen
    Overrun Handling for Mixed-Criticality Support in RTEMS Kuan-Hsun Chen, Georg von der Brüggen, Jian-Jia Chen To cite this version: Kuan-Hsun Chen, Georg von der Brüggen, Jian-Jia Chen. Overrun Handling for Mixed-Criticality Support in RTEMS. WMC 2016, Nov 2016, Porto, Portugal. hal-01438843 HAL Id: hal-01438843 https://hal.archives-ouvertes.fr/hal-01438843 Submitted on 25 Jan 2017 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. Overrun Handling for Mixed-Criticality Support in RTEMS Kuan-Hsun Chen, Georg von der Bruggen,¨ and Jian-Jia Chen Department of Informatics, TU Dortmund University, Germany Email: fkuan-hsun.chen, georg.von-der-brueggen, [email protected] Abstract—Real-time operating systems are not only used in of real-time operation systems is sufficient. However, some embedded real-time systems but also useful for the simulation and applications also have tasks with arbitrary deadlines, i.e., for validation of those systems. During the evaluation of our paper some tasks D > T . If the tasks are strictly periodic, this about Systems with Dynamic Real-Time Guarantees that appears i i in RTSS 2016 we discovered certain unexpected system behavior leads to a situation where two or more instances of the same in the open-source real-time operating system RTEMS.
    [Show full text]
  • Analysis of Devops Tools to Predict an Optimized Pipeline by Adding Weightage for Parameters
    International Journal of Computer Applications (0975 – 8887) Volume 181 – No. 33, December 2018 Analysis of DevOps Tools to Predict an Optimized Pipeline by Adding Weightage for Parameters R. Vaasanthi V. Prasanna Kumari, PhD S. Philip Kingston Research Scholar, HOD, MCA Project Manager SCSVMV University Rajalakshmi Engineering Infosys, Mahindra City, Kanchipuram College, Chennai Chennai ABSTRACT cloud. Now-a-days more than ever, DevOps [Development + Operations] has gained a tremendous amount of attention in 2. SCM software industry. Selecting the tools for building the DevOps Source code management (SCM) is a software tool used for pipeline is not a trivial exercise as there are plethora’s of tools development, versioning and enables team working in available in market. It requires thought, planning, and multiple locations to work together more effectively. This preferably enough time to investigate and consult other plays a vital role in increasing team’s productivity. Some of people. Unfortunately, there isn’t enough time in the day to the SCM tools, considered for this study are GIT, SVN, CVS, dig for top-rated DevOps tools and its compatibility with ClearCase, Mercurial, TFS, Monotone, Bitkeeper, Code co- other tools. Each tool has its own pros/cons and compatibility op, Darcs, Endevor, Fossil, Perforce, Rational Synergy, of integrating with other tools. The objective of this paper is Source Safe, and GNU Bazaar. Table1 consists of SCM tools to propose an approach by adding weightage to each with weightage. parameter for the curated list of the DevOps tools. 3. BUILD Keywords Build is a process that enables source code to be automatically DevOps, SCM, dependencies, compatibility and pipeline compiled into binaries including code level unit testing to ensure individual pieces of code behave as expected [4].
    [Show full text]
  • Getting Started Guide for Freebsd Release 18.11.11
    Getting Started Guide for FreeBSD Release 18.11.11 Jan 20, 2021 CONTENTS 1 Introduction 1 1.1 Documentation Roadmap...............................1 2 Installing DPDK from the Ports Collection3 2.1 Installing the DPDK FreeBSD Port..........................3 2.2 Compiling and Running the Example Applications.................3 3 Compiling the DPDK Target from Source6 3.1 System Requirements.................................6 3.2 Install the DPDK and Browse Sources........................7 3.3 Installation of the DPDK Target Environments...................7 3.4 Browsing the Installed DPDK Environment Target.................8 3.5 Loading the DPDK contigmem Module.......................8 3.6 Loading the DPDK nic_uio Module..........................9 4 Compiling and Running Sample Applications 12 4.1 Compiling a Sample Application........................... 12 4.2 Running a Sample Application............................ 13 4.3 Running DPDK Applications Without Root Privileges............... 14 5 EAL parameters 15 5.1 Common EAL parameters.............................. 15 5.2 FreeBSD-specific EAL parameters.......................... 17 i CHAPTER ONE INTRODUCTION This document contains instructions for installing and configuring the Data Plane Development Kit (DPDK) software. It is designed to get customers up and running quickly and describes how to compile and run a DPDK application in a FreeBSD application (bsdapp) environment, without going deeply into detail. For a comprehensive guide to installing and using FreeBSD, the following handbook is available from the FreeBSD Documentation Project: FreeBSD Handbook. Note: The DPDK is now available as part of the FreeBSD ports collection. Installing via the ports collection infrastructure is now the recommended way to install the DPDK on FreeBSD, and is documented in the next chapter, Installing DPDK from the Ports Collection.
    [Show full text]
  • The Many Approaches to Real-Time and Safety Critical Linux Systems
    Corporate Technology The Many Approaches to Real-Time and Safety-Critical Linux Open Source Summit Japan 2017 Prof. Dr. Wolfgang Mauerer Siemens AG, Corporate Research and Technologies Smart Embedded Systems Corporate Competence Centre Embedded Linux Copyright c 2017, Siemens AG. All rights reserved. Page 1 31. Mai 2017 W. Mauerer Siemens Corporate Technology Corporate Technology The Many Approaches to Real-Time and Safety-Critical Linux Open Source Summit Japan 2017 Prof. Dr. Wolfgang Mauerer, Ralf Ramsauer, Andreas Kolbl¨ Siemens AG, Corporate Research and Technologies Smart Embedded Systems Corporate Competence Centre Embedded Linux Copyright c 2017, Siemens AG. All rights reserved. Page 1 31. Mai 2017 W. Mauerer Siemens Corporate Technology Overview 1 Real-Time and Safety 2 Approaches to Real-Time Architectural Possibilities Practical Approaches 3 Approaches to Linux-Safety 4 Guidelines and Outlook Page 2 31. Mai 2017 W. Mauerer Siemens Corporate Technology Introduction & Overview About Siemens Corporate Technology: Corporate Competence Centre Embedded Linux Technical University of Applied Science Regensburg Theoretical Computer Science Head of Digitalisation Laboratory Target Audience Assumptions System Builders & Architects, Software Architects Linux Experience available Not necessarily RT-Linux and Safety-Critical Linux experts Page 3 31. Mai 2017 W. Mauerer Siemens Corporate Technology A journey through the worlds of real-time and safety Page 4 31. Mai 2017 W. Mauerer Siemens Corporate Technology Outline 1 Real-Time and Safety 2 Approaches to Real-Time Architectural Possibilities Practical Approaches 3 Approaches to Linux-Safety 4 Guidelines and Outlook Page 5 31. Mai 2017 W. Mauerer Siemens Corporate Technology Real-Time: What and Why? I Real Time Real Fast Deterministic responses to stimuli Caches, TLB, Lookahead Bounded latencies (not too late, not too Pipelines early) Optimise average case Repeatable results Optimise/quantify worst case Page 6 31.
    [Show full text]
  • LIGO Data Analysis Software Specification Issues
    LASER INTERFEROMETER GRAVITATIONAL WAVE OBSERVATORY - LIGO - CALIFORNIA INSTITUTE OF TECHNOLOGY MASSACHUSETTS INSTITUTE OF TECHNOLOGY Document Type LIGO-T970100-A - E LIGO Data Analysis Software Specification Issues James Kent Blackburn Distribution of this draft: LIGO Project This is an internal working document of the LIGO Project. California Institute of Technology Massachusetts Institute of Technology LIGO Project - MS 51-33 LIGO Project - MS 20B-145 Pasadena CA 91125 Cambridge, MA 01239 Phone (818) 395-2129 Phone (617) 253-4824 Fax (818) 304-9834 Fax (617) 253-7014 E-mail: [email protected] E-mail: [email protected] WWW: http://www.ligo.caltech.edu/ Table of Contents Index file /home/kent/Documents/framemaker/DASS.fm - printed July 22, 1997 LIGO-T970100-A-E 1.0 Introduction The subject material discussed in this document is intended to support the design and eventual implementation of the LIGO data analysis system. The document focuses on raising awareness of the issues that go into the design of a software specification. As LIGO construction approaches completion and the interferometers become operational, the data analysis system must also approach completion and become operational. Through the integration of the detector and the data analysis system, LIGO evolves from being an operational instrument to being an operational grav- itational wave detector. All aspects of software design which are critical to the specifications for the LIGO data analysis are introduced with the preface that they will be utilized in requirements for the LIGO data analysis system which drive the milestones necessary to achieve this goal. Much of the LIGO data analysis system will intersect with the LIGO diagnostics system, espe- cially in the areas of software specifications.
    [Show full text]
  • Openbsd Gaming Resource
    OPENBSD GAMING RESOURCE A continually updated resource for playing video games on OpenBSD. Mr. Satterly Updated August 7, 2021 P11U17A3B8 III Title: OpenBSD Gaming Resource Author: Mr. Satterly Publisher: Mr. Satterly Date: Updated August 7, 2021 Copyright: Creative Commons Zero 1.0 Universal Email: [email protected] Website: https://MrSatterly.com/ Contents 1 Introduction1 2 Ways to play the games2 2.1 Base system........................ 2 2.2 Ports/Editors........................ 3 2.3 Ports/Emulators...................... 3 Arcade emulation..................... 4 Computer emulation................... 4 Game console emulation................. 4 Operating system emulation .............. 7 2.4 Ports/Games........................ 8 Game engines....................... 8 Interactive fiction..................... 9 2.5 Ports/Math......................... 10 2.6 Ports/Net.......................... 10 2.7 Ports/Shells ........................ 12 2.8 Ports/WWW ........................ 12 3 Notable games 14 3.1 Free games ........................ 14 A-I.............................. 14 J-R.............................. 22 S-Z.............................. 26 3.2 Non-free games...................... 31 4 Getting the games 33 4.1 Games............................ 33 5 Former ways to play games 37 6 What next? 38 Appendices 39 A Clones, models, and variants 39 Index 51 IV 1 Introduction I use this document to help organize my thoughts, files, and links on how to play games on OpenBSD. It helps me to remember what I have gone through while finding new games. The biggest reason to read or at least skim this document is because how can you search for something you do not know exists? I will show you ways to play games, what free and non-free games are available, and give links to help you get started on downloading them.
    [Show full text]
  • OPERATING SYSTEMS.Ai
    Introduction Aeroflex Gaisler provides LEON and ERC32 users with a wide range of popular embedded operating systems. Ranging from very small footprint task handlers to full featured Real-Time Operating System (RTOS). A summary of available operating systems and their characteristics is outlined below. VxWorks The VxWorks SPARC port supports LEON3/4 and LEON2. Drivers for standard on-chip peripherals are included. The port supports both non-MMU and MMU systems allowing users to program fast and secure applications. Along with the graphical Eclipse based workbench comes the extensive VxWorks documentation. • MMU and non-MMU system support • SMP support (in 6.7 and later) • Networking support (Ethernet 10/100/1000) • UART, Timer, and interrupt controller support • PCI, SpaceWire, CAN, MIL-STD-1553B, I2C and USB host controller support • Eclipse based Workbench • Commercial license ThreadX The ThreadX SPARC port supports LEON3/4 and its standard on-chip peripherals. ThreadX is an easy to learn and understand advanced pico-kernel real-time operating system designed specifically for deeply embedded applications. ThreadX has a rich set of system services for memory allocation and threading. • Non-MMU system support • Bundled with newlib C library • Support for NetX, and USBX ® • Very small footprint • Commercial license Nucleus Nucleus is a real time operating system which offers a rich set of features in a scalable and configurable manner. • UART, Timer, Interrupt controller, Ethernet (10/100/1000) • TCP offloading and zero copy TCP/IP stack (using GRETH GBIT MAC) • USB 2.0 host controller and function controller driver • Small footprint • Commercial license LynxOS LynxOS is an advanced RTOS suitable for high reliability environments.
    [Show full text]
  • Final Report
    Parallel Programming Models for Space Systems BSC - Evidence ESA Contract No. 4000114391/15/NL/Cbi/GM Final Report Parallel Programming Models for Space Systems (ESA Contract No. 4000114391/15/NL/Cbi/GM) Main contractor Subcontractor Barcelona Supercomputing Center (BSC) Evidence Srl. Eduardo Quiñones, Paolo Gai, [email protected] [email protected] Dissemination level: All information contained in this document is puBlic June 2016 1 Parallel Programming Models for Space Systems BSC - Evidence ESA Contract No. 4000114391/15/NL/Cbi/GM Table of Contents 1 Introduction ..................................................................................................... 3 2 Future work: Next development activities to reach higher TRL (5/6) ................ 4 Annex I - D1.1. Report on parallelisation experiences for the space application .... 5 Annex II - D2.1. Report on the evaluation of current implementations of OpenMP ............................................................................................................................ 23 Annex III - D3.1. Report on the applicability of OpenMP4 on multi-core space platforms ............................................................................................................ 36 2 Parallel Programming Models for Space Systems BSC - Evidence ESA Contract No. 4000114391/15/NL/Cbi/GM 1 Introduction High-performance parallel architectures are becoming a reality in the critical real-time embedded systems in general, and in the space domain in particular. This is the case of the
    [Show full text]