Real-Time Operating System for Wireless Sensors Powered by Renewable Energy Source

Total Page:16

File Type:pdf, Size:1020Kb

Real-Time Operating System for Wireless Sensors Powered by Renewable Energy Source International Journal of Computer Applications (0975 8887) Volume 81 - No. 12, November 2013 Real-time Operating System for Wireless Sensors Powered by Renewable Energy Source Hussein El Ghor El-Hadi M Aggoune Lebanese University - IUT Saida Electrical Engineering Department SNCS Research Center, UT, Saudi Arabia Sensor Networks and Cellular Systems (SNCS) Research Center B.P. 813 Saida, Lebanon University of Tabuk, 71491 Tabuk, Saudi Arabia ABSTRACT cating devices (sensor networks). Such devices, mainly character- ized by restrictions in terms of energy capacity, memory size and Energy management is a central problem in real-time systems de- computing power, impose new constraints to real-time operating sign, in particular for embedded wireless devices such as sensor systems (RTOS). Today, the challenge, raised by the emergence of devices. In our work, we aim at the improvement of real-time op- embedded systems powered by renewable energy, is to ensure sus- erating systems that are powered by renewable energy source (so- tainable autonomy if not perpetual that involves new guidelines for lar energy, for example). The objective of this work is to develop RTOS in terms of scheduling and power management. software components for the design of real-time operating systems. In this paper, we address the problem of scheduling hard real-time We provide an on-line scheduling scheme, named Earliest Deadline tasks under energy constraints. The scope of the paper is to develop with energy guarantee (EDeg), in order to address the limitations in software components for the design of real-time operating systems energy harvesting systems. We also integrate EDeg scheduling al- for wireless sensors that are powered by renewable energy sources gorithm into CLEOPATRE open-source component library, a patch such as solar panel and relies on a battery with limited capacity. to Linux/RTAI and evaluate the scheduling overheads of EDeg ob- The remainder of the paper is organized in the following manner. served under Linux/RTAI. In the next section, we summarize the state of art relative to en- ergy management in both real-time systems and real-time operat- Keywords: ing systems. Section 3 describes the CLEOPATRE project includ- ing scheduling and fault tolerance mechanisms. In section 4, we Energy Management, Real-time, Operating Systems, Energy Har- present the energy guarantee scheduler. Section 5 introduces the vesting, RTAI. integration of EDeg into Linux based systems. Performance eval- uation is studied in section 6. Section 7 concludes the paper and 1. INTRODUCTION gives some new directions of work. Real-time computing systems play a critical role in our society. This is due to the fact that many complex systems rely, in part or 2. STATE OF ART completely, on computer control. Examples of applications that re- 2.1 Energy Management in Real-Time Systems quire real-time computing include: sensor and cellular networks, plant and process control, detection and tracking, etc. Energy-aware real-time scheduling has been the subject of inten- A robust guarantee of the performance of a real-time system un- sive research. Most of the works focus on either minimizing the der all possible operating conditions can be achieved only by using energy consumption or maximizing the system performance such more sophisticated design methodologies. Such methodologies are as the lifetime achieved under energy constraints [1]. However, combined with a static analysis of the source code and specific op- the rechargeability of the energy storage unit is disregarded. Other erating systems mechanisms, purposely designed to support com- works use the techniques of Dynamic Voltage and Frequency Scal- putation under time constraints. Moreover, in critical applications, ing (DVFS) and Dynamic Power Management (DPM) [2]. But the control system must be capable of handling all anticipated sce- solely applying these techniques has limitations in energy harvest- narios, including peak load situations, and its design must be driven ing systems because they minimize CPU power, rather than dy- by pessimistic assumptions on the events generated by the environ- namically manage power according to the profiles of both available ment. energy and processor workload. Typically, a real-time system is implemented as a set of concurrent In the last decade, researchers started to address power and schedul- tasks that are managed by a software called Real-Time Operating ing issues but most of them do not consider both rechargeability of System (RTOS). Each task performs a computational activity ac- the batteries and real-time constraints. In the work by Allavena et cording to a set of constraints. Thus, the objective of the RTOS is to al. in [3], power scavenged by the energy source is constant and manage and control the assignment of system resources (including all tasks consume energy at a constant rate. Later in [4], Moser et the microprocessor) to the tasks in order to meet such constraints. al. propose LSA (Lazy scheduling Scheduling Algorithm) to opti- Nowadays, energy management becomes the central problem in mally schedule tasks with deadlines, periodic or not. In that work, real-time systems design, in particular for autonomous communi- the total energy consumption of every task is directly connected 1 International Journal of Computer Applications (0975 8887) Volume 81 - No. 12, November 2013 to its execution time through the constant power of the processing guidelines of RTOS for autonomous communicating devices (sen- device. But in a real application, instantaneous power consumed sor networks). by tasks may vary along time depending on circuitry and devices required by the tasks. 3. CLEOPATRE PROJECT 3.1 Generalities 2.2 Real-time Operating Systems A project named CLEOPATRE (Composants Logiciels sur In recent years, wireless sensor networks (WSN) have received Etageres` Ouverts Pour les Applications Temps Reel´ Embarquee)´ tremendous attention in the research community, with applications was labeled in April 2001 and notified in January 2002 by the ranging from home automation to industrial and environmental French Ministry of Education and Research. The objective of this monitoring. This attention imposes additional challenges on the de- project was to provide solutions to the development of embedded sign of special purpose operating systems deviated from the tradi- real-time applications by providing free and open source software tional ones. However, most of these OSs are non-real-time and can- components based on Linux [7]. CLEOPATRE aims to enhance the not support real-time applications. Moreover, various problems will real-time services of existing versions of Linux, such as RTLinux arise when attempting to convert a non-real-time OS to a real-time [6] or Linux/RTAI [5]. version. Some RTOS are available, which include ThreadX from In addition, many components, dedicated to real-time systems, Xpresslogic, VxWorks by Wind River, QNX Neutrino by QNX like dynamic scheduling, aperiodic task service, resource con- Software Systems, and Real-time Linux (by several vendors). trol access, fault-tolerance and QoS scheduling are offered by the Real-time operating systems are classified into two categories: sys- CLEOPATRE library (figure 1). tems that use light and standard versions of optimized operating RTAI permits Linux to fulfill some real-time constraints in a few system and those who seek the best determinism by liberating milliseconds deadline and with no event loss. It is based on a Hard- any operating system. The main difficulty with standard systems ware Abstraction Layer (HAL) [7]. The HAL defines a clear inter- is to find a balance between providing services of classical sys- face which exports some Linux data and functions related to the tems (such as dynamic allocation of memory pages that is non- hardware. deterministic) and the predictability of these services. This pre- RTAI has a microkernel, which is very close to the proposed archi- dictability is a key factor for application development with strict tecture for CLEOPATRE. In fact, CLEOPATRE components can be real-time constraints. A lot of commercial operating systems based directly treated as microkernel system servers since they have the on UNIX are derived from this approach such as QNX53, OS-954 same goal. We therefore choose RTAI to base our development and and LynxOS55. Moreover, research projects have been emerged to contribute its evolution by providing significant improvements. such as Mach Real-Time system that is an extension of the Mach Moreover, the choice of RTAI enables us to develop a complete project [11]. operating system where we can benefit from the rich Linux envi- Systems from the second category are derived from research ronment (drivers, compilers, interfaces, etc.). projects such as Spring [12], Maruti [14] and YARTOS [15]. Some- times real-time operating systems of this category are based on standard systems such as Linux. But, unlike previous systems, they are modified to give priority to real-time applications that use only CL1 CL2 CLn deterministic services. The standard operating system is relegated to the status of the task background of the real-time system that con- trols scheduling. These systems can be found as patches to Linux Fault-tolerant Aperiodic Synchronization QoS Schedulers which render real-time: RTLinux [6] and RTAI [5]. Schedulers Servers Regrettably, all these systems consider time as the only limiting CLEOPATRE factor, leaving energy efficiency as a hopeful consequence of em- Linux Processes piric decisions. Linux is now the host of most RTOS, especially for wireless sensor TCL T T T networks that operate with an ambient energy source and cannot 1 2 n Task rely on a power outlet on the wall. Thus, a power management de- sign is needed to make the best use of the available power and to adapt the performance of the environmental energy harvesting to RTAI Scheduler LINUX the available energy profile. Scheduler The most well-known versions of real-time Linux are: Real Time RTAI Application Interface (RTAI) [5] and RTLinux [6].
Recommended publications
  • UG1046 Ultrafast Embedded Design Methodology Guide
    UltraFast Embedded Design Methodology Guide UG1046 (v2.3) April 20, 2018 Revision History The following table shows the revision history for this document. Date Version Revision 04/20/2018 2.3 • Added a note in the Overview section of Chapter 5. • Replaced BFM terminology with VIP across the user guide. 07/27/2017 2.2 • Vivado IDE updates and minor editorial changes. 04/22/2015 2.1 • Added Embedded Design Methodology Checklist. • Added Accessing Documentation and Training. 03/26/2015 2.0 • Added SDSoC Environment. • Added Related Design Hubs. 10/20/2014 1.1 • Removed outdated information. •In System Level Considerations, added information to the following sections: ° Performance ° Clocking and Reset 10/08/2014 1.0 Initial Release of document. UltraFast Embedded Design Methodology Guide Send Feedback 2 UG1046 (v2.3) April 20, 2018 www.xilinx.com Table of Contents Chapter 1: Introduction Embedded Design Methodology Checklist. 9 Accessing Documentation and Training . 10 Chapter 2: System Level Considerations Performance. 13 Power Consumption . 18 Clocking and Reset. 36 Interrupts . 41 Embedded Device Security . 45 Profiling and Partitioning . 51 Chapter 3: Hardware Design Considerations Configuration and Boot Devices . 63 Memory Interfaces . 69 Peripherals . 76 Designing IP Blocks . 94 Hardware Performance Considerations . 102 Dataflow . 108 PL Clocking Methodology . 112 ACP and Cache Coherency. 116 PL High-Performance Port Access. 120 System Management Hardware Assistance. 124 Managing Hardware Reconfiguration . 127 GPs and Direct PL Access from APU . 133 Chapter 4: Software Design Considerations Processor Configuration . 137 OS and RTOS Choices . 142 Libraries and Middleware . 152 Boot Loaders . 156 Software Development Tools . 162 UltraFast Embedded Design Methodology GuideSend Feedback 3 UG1046 (v2.3) April 20, 2018 www.xilinx.com Chapter 5: Hardware Design Flow Overview .
    [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]
  • Real-Time Operating System Modelling and Simulation Using Systemc
    Real-Time Operating System Modelling and Simulation Using SystemC Ke Yu Submitted for the degree of Doctor of Philosophy Department of Computer Science June 2010 Abstract Increasing system complexity and stringent time-to-market pressure bring chal- lenges to the design productivity of real-time embedded systems. Various System- Level Design (SLD), System-Level Design Languages (SLDL) and Transaction- Level Modelling (TLM) approaches have been proposed as enabling tools for real-time embedded system specification, simulation, implementation and verifi- cation. SLDL-based Real-Time Operating System (RTOS) modelling and simula- tion are key methods to understand dynamic scheduling and timing issues in real- time software behavioural simulation during SLD. However, current SLDL-based RTOS simulation approaches do not support real-time software simulation ade- quately in terms of both functionality and accuracy, e.g., simplistic RTOS func- tionality or annotation-dependent software time advance. This thesis is concerned with SystemC-based behavioural modelling and simu- lation of real-time embedded software, focusing upon RTOSs. The RTOS-centric simulation approach can support flexible, fast and accurate real-time software tim- ing and functional simulation. They can help software designers to undertake real- time software prototyping at early design phases. The contributions in this thesis are fourfold. Firstly, we propose a mixed timing real-time software modelling and simula- tion approach with various timing related techniques, which are suitable for early software modelling and simulation. We show that this approach not only avoids the accuracy drawback in some existing methods but also maintains a high simu- lation performance. Secondly, we propose a Live CPU Model to assist software behavioural timing modelling and simulation.
    [Show full text]
  • Debugging Threadx RTOS Applications Using Tracex Contents
    Application Note Renesas Synergy™ Platform R20AN0404EJ0112 Debugging ThreadX RTOS Applications Rev.1.12 Using TraceX Sep 10, 2018 ThreadX® is an RTOS from Express Logic which is based on a high-performance embedded kernel. This application note provides procedures to check ThreadX thread and object states (referred to as resources) during the development of applications in e2 studio for Renesas Synergy™. The procedure for starting TraceX® is also explained. For the ThreadX specifications and functions, visit the Express Logic (http://rtos.com/) website. For TraceX specifications and functions, visit the Synergy Software (https://www.renesas.com/us/en/products/synergy.html) page. Under the Development Tools tab, select TraceX. This application note explains examples using a project called Blinky with ThreadX that is available after installing the Renesas Synergy™ Software Package (SSP). For procedures covering operations with Blinky with ThreadX, see the Renesas Synergy™ e2 studio v6.2 or Greater Getting Started Guide available on the Synergy Solutions Gallery (https://www.renesas.com/us/en/products/synergy/gallery.html). This document describes general usage of e2 studio. This application note supports SSP version 1.4.0 and later and e2 studio version 6.2.0 and later. Target Environment The operations covered in this document were confirmed in the following environment. • Renesas SynergyTM Software Package (SSP) v1.4.0 or later • e2 studio for Renesas Synergy™ v6.2.0 or later • ThreadX (requires development/production license, see section 5.1, Licenses for ThreadX) • Development Kit for DK-S7G2 Synergy MCU Group R20AN0404EJ0112 Rev.1.12 Page 1 of 23 Sep 10, 2018 Renesas Synergy™ Platform Debugging ThreadX RTOS Applications Using TraceX Contents 1.
    [Show full text]
  • Xenomai - Implementing a RTOS Emulation Framework on GNU/Linux Philippe Gerum First Edition Copyright © 2004
    Xenomai - Implementing a RTOS emulation framework on GNU/Linux Philippe Gerum First Edition Copyright © 2004 Copyright © 2002 Philippe Gerum Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front- Cover Texts, and no Back-Cover Texts. A copy of the license is published on gnu.org: "GNU Free Documentation License" [http://www.gnu.org/licenses/ fdl.html]. April 2004 Abstract Generally speaking, the Xenomai technology first aims at helping application designers relying on traditional RTOS to move as smoothly as possible to a GNU/ Linux-based execution environment, without having to rewrite their application entirely. This paper discusses the motivations for proposing this framework, the general observations concerning the traditional RTOS directing this technology, and some in-depth details about its implementation. The Xenomai project has been launched in August 2001. It has merged in 2003 with the RTAI project [http://www.gna.org/projects/rtai/] to produce an industrial- grade real-time Free Software platform for GNU/Linux called RTAI/fusion, on top of Xenomai's abstract RTOS core. Eventually, the RTAI/fusion effort became independent from RTAI in 2005 as the xenomai project [http://www.gna.org/ projects/xenomai/]. Linux is a registered trademark of Linus Torvalds. Other trademarks cited in this paper are the property of their respective owner. 1 Xenomai - Implementing a RTOS emulation framework on GNU/Linux Table of Contents 1. White paper ................................................................................................. 2 1.1.
    [Show full text]
  • Strategic Partnership with Chip Manufacturers
    What’s new at Embedded Systems Conference 2007 Strategic Partnership with Chip Manufacturers When the first microcontrollers with on-chip de- Internationa committees bugging interface appeared on the market, the first PowerView debug solutions offered were relatively simple com- Many customers would like to see a higher level pared to the prevailing in-circuit emulators. It soon of standardization of the on-chip debug and trace became clear that pure debuggers without trigger logic as well as a reduction in pincount without any and trace options were not adequate for developing performance loss. In order to take an active role PowerDebug complex embedded designs efficiently. The scope in the development of innovative debug and trace of on-chip debugging and trace interfaces has been technologies, Lauterbach has been participating enlarged gradually, enabling very complex test and in various international committees over the past PowerTrace analysis functions with today’s development tools. years: • Lauterbach has been a member of the Nexus 5001™ Forum ever since its foundation and was first to market with tools conforming to the PowerProbe NEXUS specification. • In the Test & Debug Working Group of the MIPI Alliance, Lauterbach has been involved in the Power- definition of interfaces as well as corresponding Integrator test and debug tools for mobile phones. • Lauterbach has been an active member of the IEEE P1149.7 Working Group for the definition of new JTAG standards ever since its foundation. In 2006 Lauterbach was able to significantly staff up its engineering departments, further strength- ening its leadership position in high performance development tools for a wide range of processor architectures.
    [Show full text]
  • TM4C Applications
    From industrial Gateway to functional safety with TI Cortex based MCU Texas Instruments Inc. Nov, 2015 MCU Trends Ultra-low power • Pushing the limits of power consumption toward a world without batteries Real-time control • Enabling “green” end equipments that use less energy and operate more efficiently Communications • Connecting and automating home, building and industrial systems. Security • Securing data flow over all means of communication Safety • Bringing intelligence to safety-critical applications to prevent and protect Building a Stronger MCU Portfolio Low Power MCUs Performance MCUs Ultra-low Power Real-time Control Applications where the majority of device Applications needing low latency Ultra-low power life in standby closed loop control Real-time control Low Power Performance Control + Automation Mostly ‘On’ battery powered applicationsCommunicationsCommunicationsExpanding real-time control platforms with with significant computational requirements Host Control & Industrial Communications technology Security Security + Communications Hercules™ Safety Datalogging applications that transfer Safety Applications that require functional safety securely over RF TI Confidential - Maximum Restrictions Texas Instruments MCU Portfolio Hercules Tiva™ C C2000™ MSP Safety ARM® Series Real-time Low-power Cortex™-R4 ARM® control MCUs MCUs & Cortex-M3 Cortex™-M4F MCUs Includes dual-core MCUs ARM+DSP MCUs System expertise, integrated analog, software, tools, training and support 4 World’s Broadest Portfolio Wireless Connectivity Portfolio
    [Show full text]
  • Tech Datasheet Using RTOS Simulator As a Development Platform
    R Tech Datasheet DEVELOP AND TEST EMBEDDED APPLICATION ON WINDOWS OR LINUX HOST MACHINE MapuSoft’s RTOS Simulator allows engineers to develop and test commercial RTOS applications on Windows or Linux host environments. Most commercial RTOS’s are expensive to purchase and obtaining them from di¬erent sources is dicult and time consuming. Industry demands that students have experience with popular commercial RTOS’s without which the program and the students will be of little value to Industry. This is where MapuSoft’s RTOS Simulator™ can provide commercial RTOS environments at a very low price. RTOS Simulator eliminates the need for the for expensive target hardware while learning RTOS applications and testing. Using RTOS Simulator as a development platform CROSS_COMPILE, DOWLOAD AND TEST APPLICATIONS C/C++ Applications ON VARIOUS SUPPORTED TARGET HARDWARE MapuSoft’s RTOS Simulator allows engineers to generate R optimized RTOS hypervisor source code to enable Application OS Abstractor POSIX µITRON pSOS ThreadX Windows VxWorks Platform Interface Interface Interface Interface Interface Interface Interface Proler various RTOS applications to be tested and proled for Nucleus µC/OS FreeRTOS VRTX QNX RTLinux performance on Raspberry boards and other supported Interface Interface Interface Interface Interface Interface target hardware. The hypervisor code can be hosted on OS Abstractor Linux and FreeRTOS which are freely available for use. GNU/Eclipse/Mingw Tools Environment There is absolutely no need to purchase the actual OS Simulation Code Generation commercial RTOS’s for your hardware, as MapuSoft’s C/C++ Applications generated hypervisor code will support hosting various types of RTOS environment. This way, the students get Optimized good working experience on using an embedded target Cross-OS Interface and further be able to develop application prototypes Project Files RTOS SIMULATOR for their projects, thesis and other industry collaboration Cross Compilers work.
    [Show full text]
  • Cycloneacme Datasheet
    CycloneACME Embedded ACME Library for MCU CycloneACME is a client implementation of ACME (Automatic Certificate Management Environment) dedicated to embedded applications. This solution can be used to automate the process of managing X.509 certificates (ordering, renewal, revocation) with a remote certification authority like Let's Encrypt. ACME allows deployment of public-key infrastructure on Internet- facing devices (HTTPS server for example) at very low cost. Main Features ACME v2 protocol implementation Client mode of operation ACME account management (creation, update, deactivation and key rollover) Certificate management (ordering, renewal and revocation) Supports RSA, ECDSA and EdDSA certificates Supports standard ACME challenges (HTTP, DNS and TLS-ALPN) ACME-DNS client provides a simple way to automate ACME DNS challenges Compatible with ACME servers such as Let's Encrypt, Encryption Everywhere or Buypass Go SSL Comprehensive user API Flexible memory footprint. Built-time configuration to embed only the necessary features Portable architecture (no processor dependencies) The library is distributed as a full ANSI C and highly maintainable source code © 2010-2021 Oryx Embedded www.oryx-embedded.com CycloneACME Embedded ACME Library for MCU Supported Processors Reference Standards ARM Cortex-M3 RFC 8555: Automatic Certificate Management ARM Cortex-M4 Environment (ACME) ARM Cortex-M7 ARM Cortex-R4 RFC 8737: ACME TLS Application-Layer Protocol ARM Cortex-A5 Negotiation (ALPN) Challenge Extension ARM Cortex-A8 RFC 7515: JSON Web Signature
    [Show full text]
  • REAL-TIME SYSTEMS: an INTRODUCTION Keep up with the Data Stream from the Landing Radar
    R REAL-TIME SYSTEMS: AN INTRODUCTION keep up with the data stream from the landing radar. AND THE STATE-OF-THE-ART However, it was discovered that the missed deadlines were nonfatal, and the scheduler automatically adjusted, INTRODUCTION to meet soft real-time behavior for the landing tasks. Our goal in this article is to give an overview of the broad Periodic and Aperiodic Tasks area of real-time systems. This task daunting because real- Real-time applications are also classified depending on the time systems are everywhere, and yet no generally tasks that comprise the application. In some systems, tasks accepted definition differentiates real-time systems from are executed repetitively within a specified period. A task t non–real-time systems. We will make an attempt at pro- i is characterized as (p ,e), where p its periodicity and e is viding a general overview of the different classes of real- i i i i its (worst-case) execution time. Monitoring patient’s vitals time systems, scheduling of tasks (or threads) in such is an example of such a system. Hard real-time systems are systems, design tools and environments for real-time sys- usually designed using periodic tasks, and static schedul- tems, real-time operating systems, and embedded systems. ing can be used for periodic tasks. We will conclude our discussions with research challenges Aperiodic tasks are tasks that are executed on demand that still remain. (or with unknown period). A task is executed in response to an event, and a task t is characterized as (a ,r,e,d) where Definitions i i i i i ai its the arrival time.
    [Show full text]
  • Benchmarking Real-Time Operating Systems for Use in Radio Base Station Applications Master of Science Thesis
    Benchmarking Real-time Operating Systems for use in Radio Base Station applications Master of Science Thesis OSKAR ÖRNVALL Chalmers University of Technology University of Gothenburg Department of Computer Science and Engineering Göteborg, Sweden, March 2012 The Author grants to Chalmers University of Technology and University of Gothenburg the non-exclusive right to publish the Work electronically and in a non-commercial purpose make it accessible on the Internet. The Author warrants that he/she is the author to the Work, and warrants that the Work does not contain text, pictures or other material that violates copyright law. The Author shall, when transferring the rights of the Work to a third party (for example a publisher or a company), acknowledge the third party about this agreement. If the Author has signed a copyright agreement with a third party regarding the Work, the Author warrants hereby that he/she has obtained any necessary permission from this third party to let Chalmers University of Technology and University of Gothenburg store the Work electronically and make it accessible on the Internet. Benchmarking Real-time Operating Systems for use in Radio Base Station applications OSKAR ÖRNVALL © OSKAR ÖRNVALL, March 2012 Examiner: ROGER JOHANSSON Chalmers University of Technology University of Gothenburg Department of Computer Science and Engineering SE-412 96 Göteborg Sweden Telephone + 46 (0)31-772 1000 Department of Computer Science and Engineering Göteborg, Sweden March 2012 Abstract The support systems for Radio Base Stations (RBS) are getting increasingly advanced. There are demands to support numerous RBS congurations, multiple and alternative energy sources such as wind a solar, dierent cooling systems and alarm handling.
    [Show full text]
  • Mcuxpresso IDE Azure RTOS Threadx Debug Guide Rev
    MCUXpresso IDE Azure RTOS ThreadX Debug Guide Rev. 11.4.1 — 15 September, 2021 User guide NXP Semiconductors MCUXpresso IDE Azure RTOS ThreadX Debug Guide 15 September, 2021 Copyright © 2021 NXP Semiconductors All rights reserved. MCUXpresso IDE Azure RTOS ThreadX Debug Guide - All information provided in this document is subject to legal disclaimers © 2021 NXP Semiconductors. All rights reserved. User Guide Rev. 11.4.1 — 15 September, 2021 ii NXP Semiconductors MCUXpresso IDE Azure RTOS ThreadX Debug Guide 1. Introduction .................................................................................................................. 1 2. LinkServer Azure RTOS ThreadX Thread Aware Debugging ........................................... 2 2.1. Behavior when thread aware debugging ............................................................. 4 2.2. Debugger Messages .......................................................................................... 5 2.3. Switching between all-stop and non-stop debug modes ....................................... 6 3. Azure RTOS ThreadX Thread Aware Debug Views ........................................................ 7 3.1. Showing the Azure RTOS ThreadX TAD Views ................................................... 7 3.2. Threads View .................................................................................................... 8 3.3. Message Queues View ...................................................................................... 8 3.4. Semaphores View ............................................................................................
    [Show full text]