FIRE Emulator MPC8XX
Total Page:16
File Type:pdf, Size:1020Kb
Load more
										Recommended publications
									
								- 
												  UG1046 Ultrafast Embedded Design Methodology GuideUltraFast 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 .
- 
												  Sistemi Operativi Real-Time Marco Cesati Lezione R13 Sistemi Operativi Real-Time – II Schema Della LezioneSistemi operativi real-time Marco Cesati Lezione R13 Sistemi operativi real-time – II Schema della lezione Caratteristiche comuni VxWorks LynxOS Sistemi embedded e real-time QNX eCos Windows Linux come RTOS 15 gennaio 2013 Marco Cesati Dipartimento di Ingegneria Civile e Ingegneria Informatica Università degli Studi di Roma Tor Vergata SERT’13 R13.1 Sistemi operativi Di cosa parliamo in questa lezione? real-time Marco Cesati In questa lezione descriviamo brevemente alcuni dei più diffusi sistemi operativi real-time Schema della lezione Caratteristiche comuni VxWorks LynxOS 1 Caratteristiche comuni degli RTOS QNX 2 VxWorks eCos 3 LynxOS Windows Linux come RTOS 4 QNX Neutrino 5 eCos 6 Windows Embedded CE 7 Linux come RTOS SERT’13 R13.2 Sistemi operativi Caratteristiche comuni dei principali RTOS real-time Marco Cesati Corrispondenza agli standard: generalmente le API sono proprietarie, ma gli RTOS offrono anche compatibilità (compliancy) o conformità (conformancy) allo standard Real-Time POSIX Modularità e Scalabilità: il kernel ha una dimensione Schema della lezione Caratteristiche comuni (footprint) ridotta e le sue funzionalità sono configurabili VxWorks Dimensione del codice: spesso basati su microkernel LynxOS QNX Velocità e Efficienza: basso overhead per cambi di eCos contesto, latenza delle interruzioni e primitive di Windows sincronizzazione Linux come RTOS Porzioni di codice non interrompibile: generalmente molto corte e di durata predicibile Gestione delle interruzioni “separata”: interrupt handler corto e predicibile, ISR lunga
- 
												  OPERATING SYSTEMS.AiIntroduction 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.
- 
												  Operating System StructureOperating System Structure Joey Echeverria [email protected] modified by: Matthew Brewer [email protected] Nov 15, 2006 Carnegie Mellon University: 15-410 Fall 2006 Overview • Motivations • Kernel Structures – Monolithic Kernels ∗ Kernel Extensions – Open Systems – Microkernels – Exokernels – More Microkernels • Final Thoughts Carnegie Mellon University: 15-410 Fall 2006 1 Motivations • Operating systems have a hard job. • Operating systems are: – Hardware Multiplexers – Abstraction layers – Protection boundaries – Complicated Carnegie Mellon University: 15-410 Fall 2006 2 Motivations • Hardware Multiplexer – Each process sees a “computer” as if it were alone – Requires allocation and multiplexing of: ∗ Memory ∗ Disk ∗ CPU ∗ IO in general (network, graphics, keyboard etc.) • If OS is multiplexing it must also allocate – Priorities, Classes? - HARD problems!!! Carnegie Mellon University: 15-410 Fall 2006 3 Motivations • Abstraction Layer – Presents “simple”, “uniform” interface to hardware – Applications see a well defined interface (system calls) ∗ Block Device (hard drive, flash card, network mount, USB drive) ∗ CD drive (SCSI, IDE) ∗ tty (teletype, serial terminal, virtual terminal) ∗ filesystem (ext2-4, reiserfs, UFS, FFS, NFS, AFS, JFFS2, CRAMFS) ∗ network stack (TCP/IP abstraction) Carnegie Mellon University: 15-410 Fall 2006 4 Motivations • Protection Boundaries – Protect processes from each other – Protect crucial services (like the kernel) from process – Note: Everyone trusts the kernel • Complicated – See Project 3 :) – Full
- 
												  Real-Time Operating System Modelling and Simulation Using SystemcReal-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.
- 
												  Workstation Operating Systems Mac OS 915-410 “Now that we've covered the 1970's...” Plan 9 Nov. 25, 2019 Dave Eckhardt 1 L11_P9 15-412, F'19 Overview “The land that time forgot” What style of computing? The death of timesharing The “Unix workstation problem” Design principles Name spaces File servers The TCP file system... Runtime environment 3 15-412, F'19 The Land That Time Forgot The “multi-core revolution” already happened once 1982: VAX-11/782 (dual-core) 1984: Sequent Balance 8000 (12 x NS32032) 1985: Encore MultiMax (20 x NS32032) 1990: Omron Luna88k workstation (4 x Motorola 88100) 1991: KSR1 (1088 x KSR1) 1991: “MCS” paper on multi-processor locking algorithms 1995: BeBox workstation (2 x PowerPC 603) The Land That Time Forgot The “multi-core revolution” already happened once 1982: VAX-11/782 (dual-core) 1984: Sequent Balance 8000 (12 x NS32032) 1985: Encore MultiMax (20 x NS32032) 1990: Omron Luna88k workstation (4 x Motorola 88100) 1991: KSR1 (1088 x KSR1) 1991: “MCS” paper on multi-processor locking algorithms 1995: BeBox workstation (2 x PowerPC 603) Wow! Why was 1995-2004 ruled by single-core machines? What operating systems did those multi-core machines run? The Land That Time Forgot Why was 1995-2004 ruled by single-core machines? In 1995 Intel + Microsoft made it feasible to buy a fast processor that fit on one chip, a fast I/O bus, multiple megabytes of RAM, and an OS with memory protection. Everybody could afford a “workstation”, so everybody bought one. Massive economies of scale existed in the single- processor “Wintel” universe.
- 
												  Debugging Threadx RTOS Applications Using Tracex ContentsApplication 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.
- 
												  In-Circuit Emulator for ARM7ICE-ARM Technical Information Technical In-Circuit Emulator for ARM7 ■ Active, passive and tracking emulation supported ■ Interface for flexible adaption to ARM7TDMI based designs ■ Software compatible JTAG debugger available ■ HLL debugger with C and C++ support ■ Disassembler for ARM and THUMB code ■ Inline assembler for ARM and THUMB code ■ Little and big endian byte ordering ■ Support for pipelined and de-pipelined address timing ARM7TDMI ■ Operation from 3.0 to 5.0V in passive mode ARM7TDMI-AMBA and from 3.0 to 3.6V in active and tracking mode The TRACE32-ICEARM supports the ARM7TDMI macro- cell with and without AMBA interface. The flexible concept of the probe allows the adaption to customer specific ASICs or to standard microcontrollers. An extensive spec- ification is available that provides a detailed overview of our requirements. Please call or email our techinal sup- port to get this document. ICE-ARM 21.02.17 TRACE32 - Technical Information 2 In-Circuit Emulator Basics of Operation Emulation Bus Break Exception Control Control Strobe/ Emulation- Dualport Target Buffer CPU Control Control Voltage Wait Control Control Port Port Buffer Analyzer Emulation module Base module Emulation Modules Modules Overview LA-7230 LA-7231 ARM7TDMI ARMICE-240 LA-7232 ARM7TDMI-AMBA ARMICE-240 ICE-ARM In-Circuit Emulator TRACE32 - Technical Information 3 Interfaces Compiler CPU Language Compier Compan Option y ARM C ARMCC ARM Ltd. AIF ARM C ARMCC ARM Ltd. ELF/DWARF ARM C REALVIEW- ARM Ltd. ELF/DWARF2 MDK ARM C GCCARM Free COFF/STABS Software Foundati on, Inc. ARM C GCCARM Free ELF/DWARF2 Software Foundati on, Inc.
- 
												  Embedded Linux System Design and DevelopmentAu0586 half title page 11/17/05 2:05 PM Page 1 EMBEDDED LINUX SYSTEM DESIGN AND DEVELOPMENT Au0586 title page 11/17/05 2:04 PM Page 1 EMBEDDED LINUX SYSTEM DESIGN AND DEVELOPMENT TEAM FLY P. Raghavan • Amol Lad • Sriram Neelakandan Boca Raton New York Published in 2006 by Auerbach Publications Taylor & Francis Group 6000 Broken Sound Parkway NW, Suite 300 Boca Raton, FL 33487-2742 © 2006 by Taylor & Francis Group, LLC Auerbach is an imprint of Taylor & Francis Group No claim to original U.S. Government works Printed in the United States of America on acid-free paper 10987654321 International Standard Book Number-10: 0-8493-4058-6 (Hardcover) International Standard Book Number-13: 978-0-8493-4058-1 (Hardcover) Library of Congress Card Number 2005048179 This book contains information obtained from authentic and highly regarded sources. Reprinted material is quoted with permission, and sources are indicated. A wide variety of references are listed. Reasonable efforts have been made to publish reliable data and information, but the author and the publisher cannot assume responsibility for the validity of all materials or for the consequences of their use. No part of this book may be reprinted, reproduced, transmitted, or utilized in any form by any electronic, mechanical, or other means, now known or hereafter invented, including photocopying, microfilming, and recording, or in any information storage or retrieval system, without written permission from the publishers. For permission to photocopy or use material electronically from this work, please access www.copyright.com (http://www.copyright.com/) or contact the Copyright Clearance Center, Inc.
- 
												  Real-Time and Embedded GuideReal-Time and Embedded Guide Herman Bruyninckx K.U.Leuven, Mechanical Engineering Leuven Belgium [email protected] Real-Time and Embedded Guide by Herman Bruyninckx Copyright © 2000, 2001, 2002 [email protected] This Guide covers the fundamentals of (i) real-time and embedded operating systems (focusing mostly on the differences with general purpose operating systems such as Linux), and (ii) real-time programming. The emphasis is on Free Software and Open Source Software examples: RTAI, RTLinux, eCos, RT-EMS, uCLinux, . , with a more than proportional focus on RTAI. This text also talks about design issues, software patterns and frameworks for real-time applications. That is, the “high-level” aspects of these software projects. These higher levels are often poorly dealt with in publications on real-time programming, which leads to the unfortunate situation that still too many real-time programmers use only the powerful but dangerously unstructured API of their RTOS. Missing the chance to develop more structured, and, hence, more deterministic and more portable software systems. Both the low-level RTOS primitives, and the high-level design issues, are illustrated by the real-world example of a hard real-time core for feedback control and signal processing. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation, with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of this license can be found at http://www.fsf.org/copyleft/fdl.html.
- 
												  Systèmes Embarqués PFSEM 2007 - 2008ChorusOS Systèmes Embarqués PFSEM 2007 - 2008 Real-Time & Embedded OS Principles Use case: ChorusOS B/PFSEM/Systèmes Embarqués Ivan Boule 1 ChorusOS Plan Environnement de Développement Micro-noyau C5 (ChorusOS®) Device Driver Framework Personnalité POSIX Voir "Programming Under Chorus", Jean-Marie Rifflet http://www.pps.jussieu.fr/~rifflet/PUBLICATIONS/book4.html B/PFSEM/Systèmes Embarqués Ivan Boule 2 ChorusOS OS Architecture Outils, Agents Applications POSIX API DDI C5 Services POSIX Device Drivers API Micro-noyau C5 Micro-noyau B/PFSEM/Systèmes Embarqués Ivan Boule 3 ChorusOS ChorusOS - Système Temps-Réel Environnement de développement croisé (Host/Target) Commandes d'administration embarquées C5 micro-noyau (Chorus 5ème génération) Comportement temps-réel garanti Verrouillage à grain fin (fine-grain locking) Gestion(s) mémoire flexible Device Drivers Framework Debugger système (kdb) intégré B/PFSEM/Systèmes Embarqués Ivan Boule 4 ChorusOS Host/Target System Environment Tool Agents Applications POSIX API DDI C5 POSIX Services Device Drivers C5 Microkernel Host System (Linux or Solaris) Target Platform B/PFSEM/Systèmes Embarqués Ivan Boule 5 ChorusOS Environnement de Développement Embedded Targets • Application download • Embedded Debugger Development Host Linux or Solaris • Jaluna/C5 system configurator • C and C++ Development Toolchain • C and C++ Symbolic Debugger Liens: • Application management utilities ● Ligne série • Set of libraries ● Ethernet ● JTAG B/PFSEM/Systèmes Embarqués Ivan Boule 6 ChorusOS Développement Host/Target
- 
												  Xenomai - Implementing a RTOS Emulation Framework on GNU/Linux Philippe Gerum First Edition Copyright © 2004Xenomai - 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.