DOCSLIB.ORG

A Software Guide to Universal Debug Engine for C166, ST10, XC166, XE166 XC2000, Tricore, Powerpc ARM, Xscale, Superh

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

A Software Guide to Universal Debug Engine for C166, ST10, XC166, XE166 XC2000, TriCore, PowerPC ARM, XScale, SuperH Integrated Development Environment for 32-bit TriCore, PowerArchitecture, Cortex, ARM7, ARM9, ARM11, XScale, SuperH derivatives for 16-bit C166, ST10, XC166, XC2000, XE166, C166CBC derivatives PLS 1991-2013 V 4.00.02.02 This manual contains 167 pages. Contact us at: EMail: [email protected] [email protected] WWW: http://www.pls-mc.com PLS Programmierbare Logik & Systeme GmbH PLS Development Tools Technologiepark Lauta 1250 Oakmead Parkway, Suite#210 D - 02991 Lauta Sunnyvale CA, 94085 Germany U.S.A. Phone: + 49 35722 384 - 0 + 1 408 451 - 8408 Fax: + 49 35722 384 - 69 + 1 408 501 - 8808 Toll Free: + 1 877 - 77DEBUG All rights reserved. No part of this manual may be reproduced or may be transmitted in any form or by any means without prior written permission of PLS Programmierbare Logik & Systeme GmbH. The information in this manual is subject to change without notice, no responsibility is assumed for its use. Universal Debug Engine is a trademark of PLS Programmierbare Logik & Systeme GmbH. Adobe is a registered trademark of Adobe Systems Incorporated. TriCore™ is a trademark of Infineon AG. ARM7™, ARM9™, ARM11™, Cortex™ are trademarks of ARM . PowerPC is a registered trademark of IBM Corporation. Power Architecture™ is a trademark of Power.org. Windows XP, Windows Vista, Windows 7, Windows 8 are trademarks of Microsoft Corporation. Pentium and Core™ are trademarks of Intel Corporation. XScale , Celeron are registered trademarks of Intel Corporation. Athlon™ is a trademark of Advanced Micro Devices, Inc. SuperH™ is a trademark of Renesas Technology Corporation. All other names and trademarks are the property of their respective owners. Contents Introduction 7 Overview 7 Feedback 7 Versions of UDE 8 Delivery Contents 9 System Requirements 11 Installing of Universal Debug Engine 12 Installation Notes - before you install UDE 12 Installing Hardware 13 Static Electricity Precautions 13 Demo Version for Starterkits (via JTAG) 14 Demo Version for Starterkits (via ASC Bootstrap loader) 15 Demo Version for Easy Kits (via DAS/USB-JTAG adapter) 16 compact Standard Version UAD2 (via JTAG) 17 pro Standard Version UAD2 and UAD2 (via JTAG) 18 pro Standard Version UAD2 and UAD2 (via DAP) 19 pro Standard Version UAD2 and UAD2 (via SWD) 20 + Standard Version UAD2 (via JTAG) 21 + Standard Version UAD2 (via DAP) 22 + Standard Version UAD2 (via SWD) 23 + Standard Version UAD3 (via JTAG) 24 Standard Version UAD2 (via ASC, SSC, CAN) 25 + Standard Version UAD2 (via ASC, SSC, CAN) 26 + Standard Version UAD2 (via 3Pin) 27 Standard Version fast-PC6x / fast-PC276 (via ASC/SSC) 28 Standard Version fast-PC6x / fast-PC276 (via CAN) 29 + Standard Version UAD2 (with Trace Support) 30 + Standard Version UAD3 (with Trace support) 31 UAD2-JTAG Protector 2 for UAD2 32 + UAD-JTAG Protector 2 for UAD2 33 Simulator Version (TSim) 34 Installing UDE Software 35 Working with the CD browser 35 Start the Installation 36 Driver Installation for Universal Access Device 37 UAD via standard parallel port interface 37 + UAD2 via IEEE1394 38 + UAD3 via IEEE1394b 39 pro + + UAD2, UAD2 , UAD2 , UAD3 via USB port 40 + + UAD2 , UAD3 via Ethernet TCP/IP 41 Driver Installation for USB-JTAG-Port 44 USB-JTAG-Port via USB port 44 Driver Installation for USB-Key (Sentinel USB SuperPro) 45 USB-Key via USB port 45 Driver Installation for fast-PC6x Card 46 fast-PC67C/PCI via PCI Bus Host PC 46 Driver Installation for Starterkit Version 47 JTAG Parallel Port via Standard Parallel port 47 Serial Port via Standard Serial Port 47 Serial Port via USB-to-Serial Port 47 Introduction Overview 3 of 167 License Manager 48 Node-locked licensing 49 How to get the Host ID of UDE Installation 49 Setup of Node-Locked License File 51 Uninstalling or Reinstalling UDE 52 Trouble Shooting 53 Precautions 53 Latest Versions on World Wide Web 53 Known Issues with UDE 53 Getting Started 55 Examples delivered with UDE 55 A First Example with TriCore™ 56 Precautions 56 Starting Universal Debug Engine 56 Loading a TriCore Executable 58 Running and Stepping through the Application 59 Setting Breakpoints 59 CPU Registers 60 SFR Registers 61 Viewing Variables 61 Viewing Memory Locations 62 Leaving the Project 62 A Multi-Core Debugging Example with TriCore/PCP 63 Creating a New Workspace with changed configuration 63 Running the Program 64 HelloPCP Internals 64 A Multi-Core Debugging Example with TriCore2 AURIX 65 Creating a New Workspace 65 Preparing the debugger 65 Loading a multi-core Executable 66 Core selection 67 Single-core Breakpoints 67 Multi-core Breakpoints and Stepping 68 A Multi-Core GTM Debugging Example with PowerPC MPC5746M 69 Creating a New Workspace 69 Preparing the debugger 70 Loading a multi-core Executable 70 Core selection 71 Single-core Breakpoints 71 Multi-core Breakpoints and Stepping 72 Inspecting Multi-Channel-Sequencer (MCS) Channels 72 A TriCore MCDS Trace Example 74 Introduction 74 Target Configuration 74 Preparations 74 MCDS Trace 76 An Example with C166S V2 / XC16x via JTAG/OCDS L1 77 Starting with Universal Debug Engine 77 Loading and Starting of an Executable 77 Automatic Variables Refresh 77 Trigger Functions 78 An Example with MPC5567 via JTAG 79 Starting with Universal Debug Engine 79 Loading and Starting of an Executable 79 Automatic Variables Refresh 79 Trigger Functions 80 Hints for using the MPC55xx via JTAG 81 An example for Linux kernel and application debugging 82 Preparations 82 Create a new workspace 82 Load the kernel ELF file 83 4 of 167 Overview Introduction Substitute kernel path 83 Debug a syscall kernel function 84 An Example for C166 debugging via 3Pin 85 Hardware Requirements 85 Useful hints for 3Pin Debugging 85 Monitor preparations 86 Starting the Universal Debug Engine 86 Setup Target Interface 87 Using the Simulated I/O channel 89 Creating new Target Configurations 90 Creating a new workspace 90 Invoking the Wizard 90 Select the controller derivative 91 Selecting Target Interface 91 Setup the Target Interface 92 Configuring the FLASH memory 93 Finish the wizard 94 Using the OCDS L2 Trace Board with the TriCore 95 Preparations 95 Recording the first Samples 95 Looking what happens when the Function exits 95 Measuring the Interval a Function is called 96 Conclusion 96 User's Guide 97 Introduction 97 Architecture of Universal Debug Engine 98 Using On-line Help 99 Project Management 100 Working with Projects 100 Creating a New Project 100 Select Target Configuration 101 Loading a Project 101 Saving Project Settings 101 Closing a Project 101 Command line options of UDE 102 Preparing a binary File 102 Compiler Support 102 Downloading the binary File 104 Examples of Debug Communication Channels 104 Selection of a Hardware Communication Channel 105 Overview about the Monitor programs 106 Preparing the Communication 106 Connect the target system 108 Download the application 108 Viewing Program Code 108 Workspace 108 Program Window 109 Running a program 111 Inline Assembler 111 Viewing and Modifying Registers 112 Kinds of Register Views 112 CPU View 112 SFR View 113 HTML View based on the UDE Object Model 114 Watching Variables 115 Watch View 115 Watch Expressions 115 Adding Variables and Expressions using Select Watch Dialog 117 Locals View 119 Automatically variable content refresh 119 Stepping and Breakpoints 119 Introduction Overview 5 of 167 Overview 119 Following the program flow 119 Stop the program at a specified location 120 Breakpoint dialog 121 Breakpoint identifier 122 Viewing Memory Locations 123 Writing data to target 123 Updating data from target 123 Printing of memory locations 124 Viewing Data as Scientific Chart 124 Basic features of the Graphic Display Window 124 Using Expressions 124 Graphical Display Window Properties 125 Viewing Call Stack 125 Program Execution Time Measuring 126 Trace, Visualization and Analyzing 127 Trace Analyzing Features and Views 128 Trace Profiling as Statistical Chart 129 Trace Profiling as Flow Chart 132 Code Coverage 133 MCDS, Nexus, CoreSight, ETM, ETB, OCDS L2 Trace View 134 Signal Trace - Real-Time Graphical Monitoring 139 ITM Trace 141 Activating and Using Add-Ins 142 Activating an Add-In 142 Removing an Add-In 142 Triggered Transfer Recorder 143 FLASH / OTP Programming 144 Supported Functions 144 Basic Concept 144 Definition of external FLASH Memories 147 Definition of on-chip FLASH Memories 147 Definition of Memory Access Filters 148 Enabling the FLASH Programming 148 FLASH Programming 149 Setup FLASH Programming options 150 UDE CAN Recorder 151 Supported Functions 151 Enabling the CAN Recorder 151 Send and Record CAN Messages 151 UDE RTX Viewer 152 Supported Functions 152 Enabling the RTX Viewer 152 Using the RTX Viewer 152 UDE rcX Viewer 153 Supported Functions 153 Enabling the rcX Viewer 153 Using the rcX Viewer 153 Eclipse IDE for UDE 154 Prepare Eclipse IDE for UDE Integration Package 154 Launching UDE Debug Session in Eclipse IDE 156 Add UDE Sample Project to Eclipse Helios C/C++ IDE 158 UDE Object Model 160 Overview 160 Example for TriCore 160 User Definable Enhancements 161 Reference 163 Index 164 6 of 167 Overview Introduction Introduction Overview Thank you for choosing Universal Debug Engine (UDE) 4, one of the most powerful development workbenches available for the 16-bit architectures C166, ST10, XC166, XC2000, XE166, C166CBC, C166S V2 and the 32-bit TriCore™, PowerPC , Cortex™, ARM7™, ARM9™, ARM11™, XScale™ and SuperH™ derivatives. The software which you are about to install is the UDE Standard License software. Included with the full licensed version comes a high-speed communication hardware which speeds up downloading your application into the target system. It offers a flexible way of communication via various communication channels to the supported microcontroller. UDE offers Linux kernel and application debugging.
Recommended publications
  • Chapter 8 Instruction Set

    Chapter 8 Instruction Set

    Chapter 8 Instruction Set 80 80 This chapter lists the PowerPC instruction set in alphabetical order by mnemonic. Note that each entry includes the instruction formats and a quick reference ‘legend’ that provides such information as the level(s) of the PowerPC architecture in which the instruction may be found—user instruction set architecture (UISA), virtual environment architecture U (VEA), and operating environment architecture (OEA); and the privilege level of the V instruction—user- or supervisor-level (an instruction is assumed to be user-level unless the O legend specifies that it is supervisor-level); and the instruction formats. The format diagrams show, horizontally, all valid combinations of instruction fields; for a graphical representation of these instruction formats, see Appendix A, “PowerPC Instruction Set Listings.” The legend also indicates if the instruction is 64-bit, , 64-bit bridge, and/or optional. A description of the instruction fields and pseudocode conventions are also provided. For more information on the PowerPC instruction set, refer to Chapter 4, “Addressing Modes and Instruction Set Summary.” Note that the architecture specification refers to user-level and supervisor-level as problem state and privileged state, respectively. 8.1 Instruction Formats Instructions are four bytes long and word-aligned, so when instruction addresses are U presented to the processor (as in branch instructions) the two low-order bits are ignored. Similarly, whenever the processor develops an instruction address, its two low-order bits are zero. Bits 0–5 always specify the primary opcode. Many instructions also have an extended opcode. The remaining bits of the instruction contain one or more fields for the different instruction formats.
  • Book E: Enhanced Powerpc™ Architecture

    Book E: Enhanced Powerpc™ Architecture

    Book E: Enhanced PowerPC Architecture Version 1.0 May 7, 2002 Third Edition (Dec 2001) The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS DOCUMENT “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. IBM does not warrant that the use of the information herein shall be free from third party intellectual property claims. IBM does not warrant that the contents of this document will meet your requirements or that the document is error-free. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the document. IBM may make improvements and or changes in the product(s) and/or program(s) described in this document at any time. This document does not imply a commitment by IBM to supply or make generally available the product(s) described herein. No part of this document may be reproduced or distributed in any form or by any means, or stored in a data base or retrieval system, without the written permission of IBM. Address comments about this document to: IBM Corporation Department B5H / Building 667 3039 Cornwallis Road P.O. Box 12195 Research Triangle Park, NC 27709 Portions of the information in this document may have been published previously in the following related documents: The PowerPC Architecture: A Specification for a New Family of RISC Processors, Second Edition (1994) The IBM PowerPC Embedded Environment: Architectural Specifications for IBM PowerPC Embedded Controllers, Second Edition (1998) IBM may have patents or pending patent applications covering the subject matter in this document.
  • Xilinx XAPP545 Statistical Profiler for Embedded IBM Powerpc, Application Note

    Xilinx XAPP545 Statistical Profiler for Embedded IBM Powerpc, Application Note

    Product Not Recommended for New Designs Application Note: Virtex-II Pro R Statistical Profiler for Embedded IBM PowerPC XAPP545 (v1.0) September 15, 2004 Author: Njuguna Njoroge Summary This application note describes how to generate statistical profiling information from the IBM PowerPC 405D, which is embedded in some Virtex-II Pro™ FPGAs. Specifically, the application note details how to convert trace output files generated from the Agilent Technologies Trace Port Analyzer into a gprof (GNU profiler) readable format. The gprof tool is capable of generating a histogram of a program's functions and a call-graph table of those functions. Introduction Profiling allows a programmer to assess where a program is spending most of its time and how frequently functions are being called. With this information, a programmer can gain insight as to what optimizations to make. In some cases, a programmer can identify bugs that would be otherwise undetectable. Using the RISCWatch application is a first step in profiling a program. Nonetheless, manually mulling through approximately 350 MB (or 8 million cycles) of trace data to discern the run-time profile of the program is a fruitless endeavor. In fact, the designers of RISCWatch realized this, so they standardized the trace output format to enable post processing of the trace. The regular format of the trace files allows scripts to parse through the trace and convert it to the gprof format. By converting the trace files into the gprof format, the widespread use of gprof in the profiling community
  • Schedule 14A Employee Slides Supertex Sunnyvale

    Schedule 14A Employee Slides Supertex Sunnyvale

    UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 SCHEDULE 14A Proxy Statement Pursuant to Section 14(a) of the Securities Exchange Act of 1934 Filed by the Registrant Filed by a Party other than the Registrant Check the appropriate box: Preliminary Proxy Statement Confidential, for Use of the Commission Only (as permitted by Rule 14a-6(e)(2)) Definitive Proxy Statement Definitive Additional Materials Soliciting Material Pursuant to §240.14a-12 Supertex, Inc. (Name of Registrant as Specified In Its Charter) Microchip Technology Incorporated (Name of Person(s) Filing Proxy Statement, if other than the Registrant) Payment of Filing Fee (Check the appropriate box): No fee required. Fee computed on table below per Exchange Act Rules 14a-6(i)(1) and 0-11. (1) Title of each class of securities to which transaction applies: (2) Aggregate number of securities to which transaction applies: (3) Per unit price or other underlying value of transaction computed pursuant to Exchange Act Rule 0-11 (set forth the amount on which the filing fee is calculated and state how it was determined): (4) Proposed maximum aggregate value of transaction: (5) Total fee paid: Fee paid previously with preliminary materials. Check box if any part of the fee is offset as provided by Exchange Act Rule 0-11(a)(2) and identify the filing for which the offsetting fee was paid previously. Identify the previous filing by registration statement number, or the Form or Schedule and the date of its filing. (1) Amount Previously Paid: (2) Form, Schedule or Registration Statement No.: (3) Filing Party: (4) Date Filed: Filed by Microchip Technology Incorporated Pursuant to Rule 14a-12 of the Securities Exchange Act of 1934 Subject Company: Supertex, Inc.
  • Tanium™ Client Deployment Guide

    Tanium™ Client Deployment Guide

    Tanium™ Client Deployment Guide Version 6.0.314.XXXX February 05, 2018 The information in this document is subject to change without notice. Further, the information provided in this document is provided “as is” and is believed to be accurate, but is presented without any warranty of any kind, express or implied, except as provided in Tanium’s customer sales terms and conditions. Unless so otherwise provided, Tanium assumes no liability whatsoever, and in no event shall Tanium or its suppliers be liable for any indirect, special, consequential, or incidental damages, including without limitation, lost profits or loss or damage to data arising out of the use or inability to use this document, even if Tanium Inc. has been advised of the possibility of such damages. Any IP addresses used in this document are not intended to be actual addresses. Any examples, command display output, network topology diagrams, and other figures included in this document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Please visit https://docs.tanium.com for the most current Tanium product documentation. Tanium is a trademark of Tanium, Inc. in the U.S. and other countries. Third-party trademarks mentioned are the property of their respective owners. © 2018 Tanium Inc. All rights reserved. © 2018 Tanium Inc. All Rights Reserved Page 2 Table of contents Overview 8 What is the Tanium Client? 8 Registration 9 Client peering 9 File distribution 11 Prerequisites 14 Host system requirements 14 Admin account 15 Network connectivity and firewall 16 Host system security exceptions 16 Deployment options summary 18 Using the Tanium Client Deployment Tool 21 Methods 21 Before you begin 21 Install the Client Deployment Tool 23 Deploy the Tanium Client 25 Check for Tanium Client updates 32 Troubleshooting 33 Logs 34 Advanced settings 34 Deploying the Tanium Client to Windows endpoints 36 Step 1: Create the installer 36 Step 2: Execute the installer 37 © 2018 Tanium Inc.
  • An Efficient and Portable SIMD Algorithm for Charge/Current Deposition in Particle-In-Cell Codes✩

    An Efficient and Portable SIMD Algorithm for Charge/Current Deposition in Particle-In-Cell Codes✩

    Computer Physics Communications 210 (2017) 145–154 Contents lists available at ScienceDirect Computer Physics Communications journal homepage: www.elsevier.com/locate/cpc An efficient and portable SIMD algorithm for charge/current deposition in Particle-In-Cell codesI H. Vincenti a,b,∗, M. Lobet a, R. Lehe a, R. Sasanka c, J.-L. Vay a a Lawrence Berkeley National Laboratory, 1 Cyclotron Road, Berkeley, CA, USA b Lasers Interactions and Dynamics Laboratory (LIDyL), Commissariat À l'Energie Atomique, Gif-Sur-Yvette, France c Intel Corporation, OR, USA a r t i c l e i n f o a b s t r a c t Article history: In current computer architectures, data movement (from die to network) is by far the most energy Received 9 January 2016 consuming part of an algorithm (≈20 pJ=word on-die to ≈10,000 pJ/word on the network). To increase Received in revised form memory locality at the hardware level and reduce energy consumption related to data movement, 10 August 2016 future exascale computers tend to use many-core processors on each compute nodes that will have Accepted 19 August 2016 a reduced clock speed to allow for efficient cooling. To compensate for frequency decrease, machine Available online 19 September 2016 vendors are making use of long SIMD instruction registers that are able to process multiple data with one arithmetic operator in one clock cycle. SIMD register length is expected to double every four years. As Keywords: Particle-In-Cell method a consequence, Particle-In-Cell (PIC) codes will have to achieve good vectorization to fully take advantage OpenMP of these upcoming architectures.
  • UDE Memtool FLASH/OTP Memory Programming Tool UDE Memtool Is a Tool for Programming On-Chip As Well As External FLASH/OTP and EPROM's

    UDE Memtool FLASH/OTP Memory Programming Tool UDE Memtool Is a Tool for Programming On-Chip As Well As External FLASH/OTP and EPROM's

    UDE MemTool FLASH/OTP Memory Programming Tool UDE MemTool is a tool for programming on-chip as well as external FLASH/OTP and EPROM's. It integrates seamlessly with the UDE Universal Debug Engine Integrated Development Environment. UDE MemTool comes as add-in for the Universal Debug Engine (UDE) and allows the FLASH/OTP programming during the development cycle inside of UDE. UDE MemTool is aware of the memory map and runs the programming algorithm when required. UDE MemTool can be used with a separate frontend interface as tool. All programming functions are available via standard COM automation interfaces, too. Using these interfaces, the features of UDE MemTool may be integrated into automatic production and testsystems or started via scripts. Additionally, UDE MemTool offers a batch mode and a command line interface for automation purposes. UDE GangProgrammer can program FLASH memory devices simultaneously to save time and optimize the resource usage in a production environment. Functions of UDE MemTool UDE MemTool offers the following functions (depending on the type of memory): Erasing the entire memory module or selected sectors of the memory module Loading Intel Hex and Motorola S-Record files Programming all or selected portions of the file into the memory module Comparing all or selected portions of the file to the current contents of the memory module Read back and save-to-disk of the current memory content Setting and Resetting the Chip/Sector Protection if applicable (on-chip only) UCB (User Configuration Blocks), ABM (Alternate Boot Mode), BMI (Boot Mode Index) header handling for some derivatives. UDE MemTool can handle more than one memory module, and is using on-chip RAM.
  • Implementing Powerpc Linux on System I Platform

    Implementing Powerpc Linux on System I Platform

    Front cover Implementing POWER Linux on IBM System i Platform Planning and configuring Linux servers on IBM System i platform Linux distribution on IBM System i Platform installation guide Tips to run Linux servers on IBM System i platform Yessong Johng Erwin Earley Rico Franke Vlatko Kosturjak ibm.com/redbooks International Technical Support Organization Implementing POWER Linux on IBM System i Platform February 2007 SG24-6388-01 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. Second Edition (February 2007) This edition applies to i5/OS V5R4, SLES10 and RHEL4. © Copyright International Business Machines Corporation 2005, 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team that wrote this redbook. ix Become a published author . xi Comments welcome. xi Chapter 1. Introduction to Linux on System i platform . 1 1.1 Concepts and terminology . 2 1.1.1 System i platform . 2 1.1.2 Hardware management console . 4 1.1.3 Virtual Partition Manager (VPM) . 10 1.2 Brief introduction to Linux and Linux on System i platform . 12 1.2.1 Linux on System i platform . 12 1.3 Differences between existing Power5-based System i and previous System i models 13 1.3.1 Linux enhancements on Power5 / Power5+ . 14 1.4 Where to go for more information . 15 Chapter 2. Configuration planning . 17 2.1 Concepts and terminology . 18 2.1.1 Processor concepts .
  • A Developer's Guide to the POWER Architecture

    A Developer's Guide to the POWER Architecture

    http://www.ibm.com/developerworks/linux/library/l-powarch/ 7/26/2011 10:53 AM English Sign in (or register) Technical topics Evaluation software Community Events A developer's guide to the POWER architecture POWER programming by the book Brett Olsson , Processor architect, IBM Anthony Marsala , Software engineer, IBM Summary: POWER® processors are found in everything from supercomputers to game consoles and from servers to cell phones -- and they all share a common architecture. This introduction to the PowerPC application-level programming model will give you an overview of the instruction set, important registers, and other details necessary for developing reliable, high performing POWER applications and maintaining code compatibility among processors. Date: 30 Mar 2004 Level: Intermediate Also available in: Japanese Activity: 22383 views Comments: The POWER architecture and the application-level programming model are common across all branches of the POWER architecture family tree. For detailed information, see the product user's manuals available in the IBM® POWER Web site technical library (see Resources for a link). The POWER architecture is a Reduced Instruction Set Computer (RISC) architecture, with over two hundred defined instructions. POWER is RISC in that most instructions execute in a single cycle and typically perform a single operation (such as loading storage to a register, or storing a register to memory). The POWER architecture is broken up into three levels, or "books." By segmenting the architecture in this way, code compatibility can be maintained across implementations while leaving room for implementations to choose levels of complexity for price/performances trade-offs. The levels are: Book I.
  • IBM Powerpc 970 (A.K.A. G5)

    IBM Powerpc 970 (A.K.A. G5)

    IBM PowerPC 970 (a.k.a. G5) Ref 1 David Benham and Yu-Chung Chen UIC – Department of Computer Science CS 466 PPC 970FX overview ● 64-bit RISC ● 58 million transistors ● 512 KB of L2 cache and 96KB of L1 cache ● 90um process with a die size of 65 sq. mm ● Native 32 bit compatibility ● Maximum clock speed of 2.7 Ghz ● SIMD instruction set (Altivec) ● 42 watts @ 1.8 Ghz (1.3 volts) ● Peak data bandwidth of 6.4 GB per second A picture is worth a 2^10 words (approx.) Ref 2 A little history ● PowerPC processor line is a product of the AIM alliance formed in 1991. (Apple, IBM, and Motorola) ● PPC 601 (G1) - 1993 ● PPC 603 (G2) - 1995 ● PPC 750 (G3) - 1997 ● PPC 7400 (G4) - 1999 ● PPC 970 (G5) - 2002 ● AIM alliance dissolved in 2005 Processor Ref 3 Ref 3 Core details ● 16(int)-25(vector) stage pipeline ● Large number of 'in flight' instructions (various stages of execution) - theoretical limit of 215 instructions ● 512 KB L2 cache ● 96 KB L1 cache – 64 KB I-Cache – 32 KB D-Cache Core details continued ● 10 execution units – 2 load/store operations – 2 fixed-point register-register operations – 2 floating-point operations – 1 branch operation – 1 condition register operation – 1 vector permute operation – 1 vector ALU operation ● 32 64 bit general purpose registers, 32 64 bit floating point registers, 32 128 vector registers Pipeline Ref 4 Benchmarks ● SPEC2000 ● BLAST – Bioinformatics ● Amber / jac - Structure biology ● CFD lab code SPEC CPU2000 ● IBM eServer BladeCenter JS20 ● PPC 970 2.2Ghz ● SPECint2000 ● Base: 986 Peak: 1040 ● SPECfp2000 ● Base: 1178 Peak: 1241 ● Dell PowerEdge 1750 Xeon 3.06Ghz ● SPECint2000 ● Base: 1031 Peak: 1067 Apple’s SPEC Results*2 ● SPECfp2000 ● Base: 1030 Peak: 1044 BLAST Ref.
  • 32-Bit TC1797

    32-Bit TC1797

    32-Bit TC1797 32-Bit Single-Chip Microcontroller Data Sheet V1.3 2014-08 Microcontrollers Edition 2014-08 Published by Infineon Technologies AG 81726 Munich, Germany © 2014 Infineon Technologies AG All Rights Reserved. Legal Disclaimer The information given in this document shall in no event be regarded as a guarantee of conditions or characteristics. With respect to any examples or hints given herein, any typical values stated herein and/or any information regarding the application of the device, Infineon Technologies hereby disclaims any and all warranties and liabilities of any kind, including without limitation, warranties of non-infringement of intellectual property rights of any third party. Information For further information on technology, delivery terms and conditions and prices, please contact the nearest Infineon Technologies Office (www.infineon.com). Warnings Due to technical requirements, components may contain dangerous substances. For information on the types in question, please contact the nearest Infineon Technologies Office. Infineon Technologies components may be used in life-support devices or systems only with the express written approval of Infineon Technologies, if a failure of such components can reasonably be expected to cause the failure of that life-support device or system or to affect the safety or effectiveness of that device or system. Life support devices or systems are intended to be implanted in the human body or to support and/or maintain and sustain and/or protect human life. If they fail, it is reasonable to assume that the health of the user or other persons may be endangered. 32-Bit TC1797 32-Bit Single-Chip Microcontroller Data Sheet V1.3 2014-08 Microcontrollers TC1797 TC1797 Data Sheet Revision History: V1.3, 2014-08 Previous Version: V1.2, 2009-09 Page Subjects (major changes since last revision) 6 add SAK-TC1797-512F180EF and SAK-TC1797-384F150EF.
  • 16/32-Bit XC2238M, XC2237M

    16/32-Bit XC2238M, XC2237M

    16/32-Bit Architecture XC2238M, XC2237M 16/32-Bit Single-Chip Microcontroller with 32-Bit Performance XC2000 Family / Base Line Data Sheet V2.1 2011-07 Microcontrollers Edition 2011-07 Published by Infineon Technologies AG 81726 Munich, Germany © 2011 Infineon Technologies AG All Rights Reserved. Legal Disclaimer The information given in this document shall in no event be regarded as a guarantee of conditions or characteristics. With respect to any examples or hints given herein, any typical values stated herein and/or any information regarding the application of the device, Infineon Technologies hereby disclaims any and all warranties and liabilities of any kind, including without limitation, warranties of non-infringement of intellectual property rights of any third party. Information For further information on technology, delivery terms and conditions and prices, please contact the nearest Infineon Technologies Office (www.infineon.com). Warnings Due to technical requirements, components may contain dangerous substances. For information on the types in question, please contact the nearest Infineon Technologies Office. Infineon Technologies components may be used in life-support devices or systems only with the express written approval of Infineon Technologies, if a failure of such components can reasonably be expected to cause the failure of that life-support device or system or to affect the safety or effectiveness of that device or system. Life support devices or systems are intended to be implanted in the human body or to support and/or maintain and sustain and/or protect human life. If they fail, it is reasonable to assume that the health of the user or other persons may be endangered.