DOCSLIB.ORG

New Measurement Concepts for Internal ECU Signals Enable High

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
New Measurement Concepts for Internal ECU Signals Enable High High-speed Measurements for Electric and Hybrid Vehicles New Measurement Concepts Enable High Data Rates and Frequent Sampling Times In the development of electric and hybrid vehicles, in particular, the requirements for instrumentation used to measure internal ECU signals are very high. Nonetheless, measurement data rates of up to 30 Mbyte/s and the necessary sampling rates of 100 kHz can be achieved with the latest generations of microcontrollers and an intelligent measuring instrumen- tation solution. The ECU’s CPU is not loaded here. The drives of electric or hybrid vehicles are generally con- pins and the POD is 10 cm. Communication between the trolled by pulse-width modulation (PWM) signals. The ad- measuring instrumentation module and the test PC is over vantage of PWM technology is that it incurs very low power XCP on Ethernet in accordance with the MCD-1 XCP stan- losses at power switches, because they only need to be dard from ASAM. The physical connection is made by a operated in two operating states: fully conducting or fully standard CAT-5 Ethernet cable. Essentially, two different blocking. The frequency of the PMW signals typically lies in measurement methods are distinguished: the “RAM copy the 10 – 20 kHz range, and in exceptional cases up to method” and the “data trace method.” They are presented 100 kHz. Maximum sampling rates of only 1 kHz are achiev- in this article, together with their advantages and disad- able for internal ECU signals when XCP – a widely used vantages, based on current microcontrollers and new standardized measurement and calibration protocol for ve- microcontrollers that will be available soon. The different hicle development – is used together with communication data trace methods refer to two types of 32-bit microcon- over the CAN or FlexRay bus system. PMW signals cannot trollers that are primarily used in powertrain ECUs and be acquired in this method. their successors: Freescale PowerPC (primary market: That is why the debug and data trace interfaces are used USA) and Infineon TriCore (primary market: Europe). for fast access to ECU variables. These interfaces can vary significantly depending on the type of microcontroller that RAM Copy Method is implemented. The measurement hardware is interfaced The RAM copy method is a generic method, and can be to the ECU over a “Plug-On Device” (POD). The maximum used for current and future generations of 32-bit microcon- allowable distance between the microcontroller’s debug trollers from various manufacturers. For the Infineon 1 TriCore or XC2000, access is via the Device Access Port where new changes are saved in a First In, First Out (FIFO) (DAP) interface; for the PowerPC devices from Freescale or buffer in RAM. The measurement is initiated by one of up to V850 E2 processors from Renesas, access is via the Nexus 256 different software triggers, and the contents of the Class 2+ interface. In this method, the ECU software initi- mirrored RAM are “frozen”. Based on the measurement ates a RAM copy function according to the cycle time of the configuration, the signals are read out from the mirrored various ECU tasks. The measurement signals must be RAM in the base module for measurement data and are preconfigured over XCP on Ethernet. The mapping of signal sent to the measurement and calibration tool over XCP on names and RAM addresses is described in an A2L file (ASAM Ethernet (Figure 2). standardized ECU description file for signal-oriented RAM Advantages of the Nexus Class 3 solution: accesses). Once all measurement signals have been copied, > The maximum measurement data rate of 30 Mbyte/s is the signals are transmitted to the base module for mea- a factor of 30 times larger than with Nexus Class 2+ and surement data according to the existing debug interfaces 600 times larger than with XCP on CAN. (Figure 1). This concept is referred to as “Online Data > The CPU is typically not loaded by the measurement. Acquisition” (OLDA). > All PWM drive signals can be measured at the 100 kHz Compared to CAN, the measurement data rate and sam- sampling rate without any problems. pling rate are improved by a factor of 20, i.e. 0.5 to 1 Mbyte/s of measurement data can be acquired with a sampling rate The disadvantage of this solution lies in the fact that signif- of 10 – 20 kHz. The copying operation loads the CPU approx. icant effort is involved in connecting the POD with its 25 4% at 1 Mbyte/s. pins to the microcontroller, and it must process a very large raw data stream of 100 Mbyte/s. Data Trace Concept for Nexus Class 3 – Current Freescale PowerPC Data Trace Concept for Next Generation Microcontrollers Most devices of the current Freescale PowerPC series sup- The main disadvantage of the Nexus Class 3 solution will be port the data trace method of Nexus Class 3. In this case, the eliminated in next generation microcontrollers, because the developer configures one or two monitoring windows with pin count has been reduced from 25 to 5. However, the a maximum total size of 512 kByte in the ECU RAM. Any measurement data rate and sampling rate will remain at changes within these monitoring windows are transmitted the same unchanged high level. This data trace solution will to the POD via Nexus Class 3 without any additional CPU also be supported by future processors from the Infineon load. Transmission rates for raw data of up to 100 MByte/s and Freescale companies. The raw data stream von are possible over the High Speed Serial Link cable. The ad- 100 Mbyte/s must still be processed. vantage of this concept is that the base module for mea- surement data always contains a consistent mirrored RAM Data Trace Concept for the Current Infineon TriCore of the ECU’s RAM. An ECU software trigger interrupts the A concept comparable to Nexus Class 3 may also be used data flow within the measurement data base module, for DAP. This involves reserving a 256 kByte memory range Figure 1: Data flow concept for measurement signals by the RAM copy method and Nexus Class 2+ interface 2 Figure 2: Data flow concept of measurement signals by the data trace concept and Nexus Class 3 interface of the ED-RAM (Emulation Device RAM) for measurement One advantage lies in its higher raw data transmission data acquisition. In contrast to the 100 MByte/s of the rate, which is now 20 MByte/s in contrast to the previous Nexus Class 3 concept, the trace transmission rate for raw 5 MByte/s. This is attained by the higher frequency of data must be limited to 5 MByte/s; just 4 pins suffice in- 160 MHz at the DAP interface instead of the previous stead of 25 pins. A maximum of four RAM monitoring win- 80 MHz and by a new type of three-line concept, which dows may be configured. They must be configured so that permits parallel transmission on two lines. there is no overrun of the trace data. Generally, this per- The greatest improvement to the DAP2 interface is that it mits monitoring of just 10–20 kByte of memory instead of now lets users set up hardware-based data trace filters 512 kByte and measurement of signals in this memory with extremely fine granularity. This significantly reduces without processor loading. Signals outside of these trace the transmission of unnecessary data trace information monitored memory areas can be measured by the RAM from the microcontroller to the POD. Despite the maxi- copy method. mum measurement data rate of 10 Mbyte/s, it is only nec- Advantages of the Infineon DAP data trace solution: essary to process 15 instead of 100 Mbyte/s of raw data > The maximum measurement data rate of 3 Mbyte/s is a (Figure 3). Due to the considerably reduced requirements factor of 3 larger than in the RAM copy method. for processing the measurement data, cost-optimized > The microcontroller is not loaded by the measurement. measuring instrumentation can be used for DAP2. > All known PWM drive signals can be measured at a 100 kHz sampling rate without any problems. Summary Many aspects of modern drive concepts for vehicles with Data Trace Concept for Future Infineon controllers pure or hybrid electric motors make it necessary to develop In the next generation of microcontrollers, Infineon is also new strategies for measurement data acquisition. Existing offering the latest generation Device Access Port (DAP). measuring instrumentation concepts for internal ECU sig- Figure 3: In the data trace concept, fine grain filters reduce the raw data stream to 15 Mbyte/s over the DAP2 interface. 3 High-speed Measurements for Electric and Hybrid Vehicles nals often reach their limits in terms of data rate or sam- pling rate. The sampling rates of up to 100 kHz that are necessary for electric drive systems can be implemented for existing and future microcontrollers using the VX1000 measurement and calibration hardware from Vector. Over the course of this year, new controller generations will be available from Freescale and Infineon, which can perform their tasks with a data trace that requires significantly fewer connection pins. In combination with the high-speed VX1131 measurement module from Vector – which will be available in the second half of 2012 – they will enable mea- surement data rates of 30 Mbyte/s without CPU loading. In the case of Infineon, DAP2 with finely granulated signal filters in the microcontroller make it possible to reduce the raw data stream from 100 to 15 Mbyte/s, which permits the use of very cost-efficient measurement hardware to achieve high data rates.
Load more

Recommended publications
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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 .
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • Solaris Powerpc Edition: Installing Solaris Software—May 1996 What Is a Profile
    SolarisPowerPC Edition: Installing Solaris Software 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. A Sun Microsystems, Inc. Business Copyright 1996 Sun Microsystems, Inc., 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Portions of this product may be derived from the UNIX® system, licensed from Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. UNIX is a registered trademark in the United States and other countries and is exclusively licensed by X/Open Company Ltd. Third-party software, including font technology in this product, is protected by copyright and licensed from Sun’s suppliers. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. Sun, Sun Microsystems, the Sun logo, Solaris, Solstice, SunOS, OpenWindows, ONC, NFS, DeskSet are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
    [Show full text]
  • 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.
    [Show full text]
  • V850 Series Development Environment Pamphlet
    To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding. Renesas Electronics website: http://www.renesas.com April 1st, 2010 Renesas Electronics Corporation Issued by: Renesas Electronics Corporation (http://www.renesas.com) Send any inquiries to http://www.renesas.com/inquiry. Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples.
    [Show full text]
  • Palmice3 V850 Apr
    Product Summary PALMiCE3 V850 Apr. 1, 2014 (1/1) JTAG emulator PALMiCE3 V850 PALMiCE3 V850 is a JTAG emulator that incorporates on-chip debugging function in Renesas Electronics-made V850. It supports USB2.0 (High-speed) as the host interface, and the Vbus which requires no power supply. Furthermore, PALMiCE3 V850 has a palm-sized, light and compact body, providing excellent portability to support you with debugging. As for the debugger, it surely incorporates CSIDE, which provides a user-friendly debugging environment. CSIDE supports not only high-level language debugging of a range of C languages but also a wide range of debugging environments by optional debug libraries. Support for SuperH family and H8S/H8SX family are also available with optional CSIDEs. ■ Supports V850 ■ Real-time watcher feature (Optional) ■ Supports USB2.0(High-speed), allowing high-speed ■ Simulated I/O feature processing ■ Allows access to memory and I/O during break ■ A palm-sized, compact body ■ Supports debugging on on-chip/external flash memories ■ Requires no power supply with Vbus support Main Specifications Supporting model HUDI141(JTAG) model Supported CPUs *1 V850E2/MN4, V850E2/ML4 JTAG clock Can be set freely in 1MHz increments between 1MHz and 25MHz. Voltage 1.65V - 5.5V (Follows target) Measures by sampling and shows the results with accuracy of 50mV Target I/F Voltage measurement and precision showing 2 decimal places. Connector 14-pin MIL connector Supports referencing/editing of register and downloading to memory during break. Register, memory, I/O operation It supports referencing/editing of memory and I/O even during execution of the user program.
    [Show full text]
  • RISC-V Geneology
    RISC-V Geneology Tony Chen David A. Patterson Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2016-6 http://www.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-6.html January 24, 2016 Copyright © 2016, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. Introduction RISC-V is an open instruction set designed along RISC principles developed originally at UC Berkeley1 and is now set to become an open industry standard under the governance of the RISC-V Foundation (www.riscv.org). Since the instruction set architecture (ISA) is unrestricted, organizations can share implementations as well as open source compilers and operating systems. Designed for use in custom systems on a chip, RISC-V consists of a base set of instructions called RV32I along with optional extensions for multiply and divide (RV32M), atomic operations (RV32A), single-precision floating point (RV32F), and double-precision floating point (RV32D). The base and these four extensions are collectively called RV32G. This report discusses the historical precedents of RV32G. We look at 18 prior instruction set architectures, chosen primarily from earlier UC Berkeley RISC architectures and major proprietary RISC instruction sets. Among the 122 instructions in RV32G: ● 6 instructions do not have precedents among the selected instruction sets, ● 98 instructions of the 116 with precedents appear in at least three different instruction sets.
    [Show full text]
  • OVP Presentation
    OpenOpen VirtualVirtual PlatformsPlatforms (OVP)(OVP) AnAn IntroductionIntroduction andand OverviewOverview [email protected] Dec 2011 Page 1 © 2011 Imperas, Open Virtual Platforms, www.OVPworld.org, v1211 TheThe growinggrowing challengechallenge SW content of electronic products grows dramatically Millions and millions lines code In 2007 SW dev costs exceeds HW design costs for SoC ICs Examining the economics of building next-generation mobile handsets with Linux By: Bill Weinber, Jun. 14, 2005 11:00 AM, linux.sys-con.com and the software needs to run faster and faster to provide more and more functionality Source: Xilinx Page 3 © 2011 Imperas, Open Virtual Platforms, www.OVPworld.org, v1211 TheThe realreal solutionsolution isis MultiMulti--CoreCore “Von Neumann is a poor use of scaling – all the energy is going on the communication between the processor and the memory. Its much better to use 20 microprocessors running at 100MHz than one at 2GHz” Hugo de Man, IMEC Early movers have been building multi-core standard processors And more and more System on Chips (SoCs) and Platform chips are becoming multicore Page 4 © 2011 Imperas, Open Virtual Platforms, www.OVPworld.org, v1211 ProcessorProcessor countcount predictedpredicted toto increaseincrease dramaticallydramatically Source: ITRS 2006 Update ITRS 2006 Source: Engine DPE: Data Processing Page 5 © 2011 Imperas, Open Virtual Platforms, www.OVPworld.org, v1211 EmbeddedEmbedded SoftwareSoftware forfor MPSoCsMPSoCs:: AnAn extremeextreme challenge!challenge! “30 to 50 per cent of R&D budgets are spent on software, and the cost is rising 20 per cent a year. The software effort overtakes the hardware effort at 130nm.” Jack Browne, MIPS Technologies “Some say we are at a crisis stage with the software side overwhelming the hardware side.
    [Show full text]