DOCSLIB.ORG

T-HEAD RISC-V AS Manual.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
T-HEAD RISC-V AS Manual.Pdf Using as The gnu Assembler (GNU Binutils) Version 2.32 The Free Software Foundation Inc. thanks The Nice Computer Company of Australia for loaning Dean Elsner to write the first (Vax) version of as for Project gnu. The proprietors, management and staff of TNCCA thank FSF for distracting the boss while they gotsome work done. Dean Elsner, Jay Fenlason & friends Using as Edited by Cygnus Support Copyright c 1991-2019 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 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 the license is included in the section entitled \GNU Free Documentation License". i Table of Contents 1 Overview ::::::::::::::::::::::::::::::::::::::::: 1 1.1 Structure of this Manual::::::::::::::::::::::::::::::::::::::: 20 1.2 The GNU Assembler :::::::::::::::::::::::::::::::::::::::::: 21 1.3 Object File Formats ::::::::::::::::::::::::::::::::::::::::::: 21 1.4 Command Line :::::::::::::::::::::::::::::::::::::::::::::::: 21 1.5 Input Files :::::::::::::::::::::::::::::::::::::::::::::::::::: 21 1.6 Output (Object) File :::::::::::::::::::::::::::::::::::::::::: 22 1.7 Error and Warning Messages :::::::::::::::::::::::::::::::::: 22 2 Command-Line Options ::::::::::::::::::::::: 25 2.1 Enable Listings: -a[cdghlns] ::::::::::::::::::::::::::::::::: 25 2.2 --alternate :::::::::::::::::::::::::::::::::::::::::::::::::: 25 2.3 -D::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 26 2.4 Work Faster: -f ::::::::::::::::::::::::::::::::::::::::::::::: 26 2.5 .include Search Path: -I path:::::::::::::::::::::::::::::::: 26 2.6 Difference Tables: -K :::::::::::::::::::::::::::::::::::::::::: 26 2.7 Include Local Symbols: -L ::::::::::::::::::::::::::::::::::::: 26 2.8 Configuring listing output: --listing ::::::::::::::::::::::::: 26 2.9 Assemble in MRI Compatibility Mode: -M ::::::::::::::::::::: 27 2.10 Dependency Tracking: --MD :::::::::::::::::::::::::::::::::: 28 2.11 Output Section Padding :::::::::::::::::::::::::::::::::::::: 28 2.12 Name the Object File: -o :::::::::::::::::::::::::::::::::::: 29 2.13 Join Data and Text Sections: -R:::::::::::::::::::::::::::::: 29 2.14 Display Assembly Statistics: --statistics ::::::::::::::::::: 29 2.15 Compatible Output: --traditional-format ::::::::::::::::: 29 2.16 Announce Version: -v :::::::::::::::::::::::::::::::::::::::: 29 2.17 Control Warnings: -W, --warn, --no-warn, --fatal-warnings :: 29 2.18 Generate Object File in Spite of Errors: -Z ::::::::::::::::::: 30 3 Syntax :::::::::::::::::::::::::::::::::::::::::: 31 3.1 Preprocessing ::::::::::::::::::::::::::::::::::::::::::::::::: 31 3.2 Whitespace:::::::::::::::::::::::::::::::::::::::::::::::::::: 31 3.3 Comments::::::::::::::::::::::::::::::::::::::::::::::::::::: 31 3.4 Symbols ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 32 3.5 Statements :::::::::::::::::::::::::::::::::::::::::::::::::::: 32 3.6 Constants ::::::::::::::::::::::::::::::::::::::::::::::::::::: 33 3.6.1 Character Constants :::::::::::::::::::::::::::::::::::::: 33 3.6.1.1 Strings :::::::::::::::::::::::::::::::::::::::::::::: 33 3.6.1.2 Characters::::::::::::::::::::::::::::::::::::::::::: 34 3.6.2 Number Constants:::::::::::::::::::::::::::::::::::::::: 34 3.6.2.1 Integers:::::::::::::::::::::::::::::::::::::::::::::: 34 3.6.2.2 Bignums ::::::::::::::::::::::::::::::::::::::::::::: 35 3.6.2.3 Flonums ::::::::::::::::::::::::::::::::::::::::::::: 35 ii Using as 4 Sections and Relocation ::::::::::::::::::::::: 37 4.1 Background ::::::::::::::::::::::::::::::::::::::::::::::::::: 37 4.2 Linker Sections :::::::::::::::::::::::::::::::::::::::::::::::: 38 4.3 Assembler Internal Sections:::::::::::::::::::::::::::::::::::: 39 4.4 Sub-Sections :::::::::::::::::::::::::::::::::::::::::::::::::: 39 4.5 bss Section :::::::::::::::::::::::::::::::::::::::::::::::::::: 40 5 Symbols ::::::::::::::::::::::::::::::::::::::::: 43 5.1 Labels::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 43 5.2 Giving Symbols Other Values :::::::::::::::::::::::::::::::::: 43 5.3 Symbol Names :::::::::::::::::::::::::::::::::::::::::::::::: 43 5.4 The Special Dot Symbol ::::::::::::::::::::::::::::::::::::::: 45 5.5 Symbol Attributes ::::::::::::::::::::::::::::::::::::::::::::: 45 5.5.1 Value::::::::::::::::::::::::::::::::::::::::::::::::::::: 45 5.5.2 Type ::::::::::::::::::::::::::::::::::::::::::::::::::::: 46 5.5.3 Symbol Attributes: a.out :::::::::::::::::::::::::::::::: 46 5.5.3.1 Descriptor ::::::::::::::::::::::::::::::::::::::::::: 46 5.5.3.2 Other:::::::::::::::::::::::::::::::::::::::::::::::: 46 5.5.4 Symbol Attributes for COFF ::::::::::::::::::::::::::::: 46 5.5.4.1 Primary Attributes :::::::::::::::::::::::::::::::::: 46 5.5.4.2 Auxiliary Attributes ::::::::::::::::::::::::::::::::: 46 5.5.5 Symbol Attributes for SOM::::::::::::::::::::::::::::::: 46 6 Expressions ::::::::::::::::::::::::::::::::::::: 47 6.1 Empty Expressions :::::::::::::::::::::::::::::::::::::::::::: 47 6.2 Integer Expressions :::::::::::::::::::::::::::::::::::::::::::: 47 6.2.1 Arguments ::::::::::::::::::::::::::::::::::::::::::::::: 47 6.2.2 Operators :::::::::::::::::::::::::::::::::::::::::::::::: 47 6.2.3 Prefix Operator::::::::::::::::::::::::::::::::::::::::::: 47 6.2.4 Infix Operators ::::::::::::::::::::::::::::::::::::::::::: 48 7 Assembler Directives::::::::::::::::::::::::::: 51 7.1 .abort :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 51 7.2 .ABORT (COFF) ::::::::::::::::::::::::::::::::::::::::::::::: 51 7.3 .align abs-expr, abs-expr, abs-expr ::::::::::::::::::::::: 51 7.4 .altmacro :::::::::::::::::::::::::::::::::::::::::::::::::::: 52 7.5 .ascii "string"... :::::::::::::::::::::::::::::::::::::::::: 52 7.6 .asciz "string"... :::::::::::::::::::::::::::::::::::::::::: 52 7.7 .balign[wl] abs-expr, abs-expr, abs-expr ::::::::::::::::: 52 7.8 Bundle directives :::::::::::::::::::::::::::::::::::::::::::::: 53 7.8.1 .bundle_align_mode abs-expr::::::::::::::::::::::::::: 53 7.8.2 .bundle_lock and .bundle_unlock :::::::::::::::::::::: 53 7.9 .byte expressions ::::::::::::::::::::::::::::::::::::::::::: 54 7.10 CFI directives :::::::::::::::::::::::::::::::::::::::::::::::: 54 7.10.1 .cfi_sections section_list ::::::::::::::::::::::::::: 54 7.10.2 .cfi_startproc [simple] :::::::::::::::::::::::::::::: 54 iii 7.10.3 .cfi_endproc ::::::::::::::::::::::::::::::::::::::::::: 54 7.10.4 .cfi_personality encoding [, exp] ::::::::::::::::::: 54 7.10.5 .cfi_personality_id id ::::::::::::::::::::::::::::::: 55 7.10.6 .cfi_fde_data [opcode1 [, ...]]:::::::::::::::::::::: 55 7.10.7 .cfi_lsda encoding [, exp]:::::::::::::::::::::::::::: 55 7.10.8 .cfi_inline_lsda [align] ::::::::::::::::::::::::::::::: 55 7.10.9 .cfi_def_cfa register, offset:::::::::::::::::::::::: 55 7.10.10 .cfi_def_cfa_register register ::::::::::::::::::::: 55 7.10.11 .cfi_def_cfa_offset offset:::::::::::::::::::::::::: 55 7.10.12 .cfi_adjust_cfa_offset offset :::::::::::::::::::::: 55 7.10.13 .cfi_offset register, offset:::::::::::::::::::::::: 56 7.10.14 .cfi_val_offset register, offset ::::::::::::::::::: 56 7.10.15 .cfi_rel_offset register, offset ::::::::::::::::::: 56 7.10.16 .cfi_register register1, register2::::::::::::::::: 56 7.10.17 .cfi_restore register ::::::::::::::::::::::::::::::: 56 7.10.18 .cfi_undefined register ::::::::::::::::::::::::::::: 56 7.10.19 .cfi_same_value register :::::::::::::::::::::::::::: 56 7.10.20 .cfi_remember_state and .cfi_restore_state ::::::: 56 7.10.21 .cfi_return_column register :::::::::::::::::::::::: 57 7.10.22 .cfi_signal_frame :::::::::::::::::::::::::::::::::::: 57 7.10.23 .cfi_window_save ::::::::::::::::::::::::::::::::::::: 57 7.10.24 .cfi_escape expression[, . .] :::::::::::::::::::::::::: 57 7.10.25 .cfi_val_encoded_addr register, encoding, label :: 57 7.11 .comm symbol , length :::::::::::::::::::::::::::::::::::::: 57 7.12 .data subsection ::::::::::::::::::::::::::::::::::::::::::: 58 7.13 .dc[size] expressions ::::::::::::::::::::::::::::::::::::: 58 7.14 .dcb[size] number [,fill] ::::::::::::::::::::::::::::::::: 58 7.15 .ds[size] number [,fill] :::::::::::::::::::::::::::::::::: 59 7.16 .def name:::::::::::::::::::::::::::::::::::::::::::::::::::: 59 7.17 .desc symbol, abs-expression:::::::::::::::::::::::::::::: 59 7.18 .dim ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 59 7.19 .double flonums::::::::::::::::::::::::::::::::::::::::::::: 60 7.20 .eject ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 60 7.21 .else :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 60 7.22 .elseif:::::::::::::::::::::::::::::::::::::::::::::::::::::: 60 7.23 .end ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 60 7.24 .endef ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 60 7.25 .endfunc :::::::::::::::::::::::::::::::::::::::::::::::::::: 60 7.26 .endif ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 60 7.27 .equ symbol, expression:::::::::::::::::::::::::::::::::::: 60 7.28 .equiv symbol, expression ::::::::::::::::::::::::::::::::: 61 7.29 .eqv symbol, expression:::::::::::::::::::::::::::::::::::: 61 7.30 .err ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 61 7.31 .error "string"::::::::::::::::::::::::::::::::::::::::::::: 61 7.32 .exitm ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 61 7.33 .extern::::::::::::::::::::::::::::::::::::::::::::::::::::::
Load more

Recommended publications
  • 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]
  • MIPS IV Instruction Set
    MIPS IV Instruction Set Revision 3.2 September, 1995 Charles Price MIPS Technologies, Inc. All Right Reserved RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013 and / or in similar or successor clauses in the FAR, or in the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor / manufacturer is MIPS Technologies, Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94039-7311. R2000, R3000, R6000, R4000, R4400, R4200, R8000, R4300 and R10000 are trademarks of MIPS Technologies, Inc. MIPS and R3000 are registered trademarks of MIPS Technologies, Inc. The information in this document is preliminary and subject to change without notice. MIPS Technologies, Inc. (MTI) reserves the right to change any portion of the product described herein to improve function or design. MTI does not assume liability arising out of the application or use of any product or circuit described herein. Information on MIPS products is available electronically: (a) Through the World Wide Web. Point your WWW client to: http://www.mips.com (b) Through ftp from the internet site “sgigate.sgi.com”. Login as “ftp” or “anonymous” and then cd to the directory “pub/doc”. (c) Through an automated FAX service: Inside the USA toll free: (800) 446-6477 (800-IGO-MIPS) Outside the USA: (415) 688-4321 (call from a FAX machine) MIPS Technologies, Inc.
    [Show full text]
  • 2 MIPS Architecture 29
    See MIPS® Run Second Edition ThisPageIntentionallyLeftBlank See MIPS® Run Second Edition Dominic Sweetman AMSTERDAM • BOSTON • HEIDELBERG • LONDON NEW YORK • OXFORD • PARIS • SAN DIEGO SAN FRANCISCO • SINGAPORE • SYDNEY • TOKYO Morgan Kaufmann Publishers is an imprint of Elsevier Publisher: Denise E. M. Penrose Publishing Services Manager: George Morrison Senior Project Manager: Brandy Lilly Editorial Assistant: Kimberlee Honjo Cover Design: Alisa Andreola and Hannus Design Composition: diacriTech Technical Illustration: diacriTech Copyeditor: Denise Moore Proofreader: Katherine Antonsen Indexer: Steve Rath Interior Printer: The Maple-Vail Book Manufacturing Group, Inc. Cover Printer: Phoenix Color Morgan Kaufmann Publishers is an imprint of Elsevier. 500 Sansome Street, Suite 400, San Francisco, CA 94111 This book is printed on acid-free paper. © 2007 by Elsevier Inc. All rights reserved. MIPS, MIPS I, MIPS II, MIPS III, MIPS IV, MIPS V, MIPS16, MIPS16e, MIPS-3D, MIPS32, MIPS64, 4K, 4KE, 4KEc, 4KSc, 4KSd, M4K, 5K, 20Kc, 24K, 24KE, 24Kf, 25Kf, 34K, R3000, R4000, R5000, R10000, CorExtend, MDMX, PDtrace and SmartMIPS are trademarks or registered trademarks of MIPS Technologies, Inc. in the United States and other countries, and used herein under license from MIPS Technologies, Inc. MIPS, MIPS16, MIPS32, MIPS64, MIPS-3D and SmartMIPS, among others, are registered in the U.S. Patent and Trademark Office. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. Designations used by companies to distinguish their products are often claimed as trademarks or registered trade- marks. In all instances in which Morgan Kaufmann Publishers is aware of a claim, the product names appear in initial capital or all capital letters.
    [Show full text]
  • M32R Family Software Manual MITSUBISHI 32-BIT SINGLE-CHIP MICROCOMPUTER
    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]
  • Pluggable Interface Relays CR-M Miniature Relays
    Data sheet Pluggable interface relays CR-M Miniature relays Pluggable interface relays are used for electrical isolation, amplification and signal matching between the electronic controlling, e.g. PLC (programmable logic controller), PC or field bus systems and the sensor / actuator level. They don’t use additional internal protective circuits and thus are overload-proof against short-time variations like current or voltage peaks. 2CDC 291 002 S0015 Characteristics Approvals – Standard miniature relays with mechanical status indication H ANSI/UL 508, CAN/CSA C22.2 No.14 – 13 different rated control supply voltages: F CAN/CSA C22.2 No.14 DC versions: 12 V, 24 V, 48 V, 60 V, 110 V, 125 V, 220 V J VDE (except 125 V DC devices) AC versions: 24 V, 48 V, 60 V, 110 V, 120 V, 230 V EAC – Output: 2 c/o (SPDT) contacts (12 A), 3 c/o (SPDT) R contacts (10 A) or 4 c/o (SPDT) contacts (6 A) P Lloyds Register (only devices with 4 c/o (SPDT) – Available with or without LED contacts) CCC – 4 c/o (SPDT) contact version optionally equipped with E gold contacts, LED and free wheeling diode L RMRS (except 60 V and 125 V devices) – Integrated test button for manual actuation and locking of output contacts (DC coil = blue, AC coil = orange) that Marks can be removed if necessary a CE – Cadmium-free contact material – Suited for logical and standard sockets – Width on socket: 27 mm (1.063 in) – Pluggable function modules: reverse polarity protection/ free wheeling diode, LED indication, RC elements, overvoltage protection Order data Packing unit = 10 pieces
    [Show full text]
  • Embedded Electronic Coding System
    1 GUARD FOR BLIND PEOPLE GUARD FOR BLIND PEOPLE ELECTRONICS AND COMMUNICATION LITAM 2 GUARD FOR BLIND PEOPLE ABSTRACT Aim of this project is to design and develop the electronic guard for blind people on embedded plat form. This project was developed for keep the right way for blind people. It has two important units; they are object detecting sensor unit and micro-controller alarm unit. The object detecting sensor is sense the opposite objects, if the blind person is going to hit any object, the sensor sense that object and given to controller. The controller activates the driver circuit; it will produce the alarm sound, now the people easily identify the opposite object. ELECTRONICS AND COMMUNICATION LITAM 3 GUARD FOR BLIND PEOPLE CHAPTER 1 INTRODUCTION ELECTRONICS AND COMMUNICATION LITAM 4 GUARD FOR BLIND PEOPLE 1.1 METHODOLOGY OF STUDY An embedded based electronic code locking system is designed and implemented using PIC Micro controller to make security. The entire project was developed under embedded systems. EMBEDDED SYSTEMS: A system is something that maintains its existence and functions as a whole through the interaction of its parts. E.g. Body, Mankind, Access Control, etc A system is a part of the world that a person or group of persons during some time interval and for some purpose choose to regard as a whole, consisting of interrelated components, each component characterized by properties that are selected as being relevant to the purpose. • Embedded System is a combination of hardware and software used to achieve a single specific task. • Embedded systems are computer systems that monitor, respond to, or control an external environment.
    [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]
  • VISION Calibration and Data Acquisition Software Toolkits
    VISION TM Toolkits VISION • No-Hooks • OnTarget • MBC VISION Calibration and Data Acquisition Software Toolkits ATI VISION Calibration and Data Acquisition software is modular in design based. The modularity of VISION toolkits provides the ability to customize VISION based on a desired level of functionality. VISION toolkits are task based feature groups that are based on customer usage models in the calibration and data acquisition fields. A VISION toolkit configuration can range from a single toolkit to view and analyze recorded data to a full ECU calibration solution with Rapid Prototyping features. Cost effective packages can easily be created based on end user need. This document contains the available VISION toolkits as of VISION 6.0. VISION Toolkits and Descriptions: Part Number Name Description Base VISION 3 Build device tree (All devices can be added to the tree, but cannot go online with any particular device unless the necessary toolkit is enabled). 3 Configure ATI hardware. 3 Acquire data from ATI Data Acquisition hardware into VISION recorders and screen objects (Not ECU Interfaces unless the appropriate ECU Interface Toolkit is enabled). 3 View data on a Data List (This is the only screen object available to view data). 3 CAN Trace object (Only ATI branded CAN Interface unless VISION Third Party CAN Interface Toolkit is enabled). 3 Configure Network Hub Logger functionality (Limited to only ATI Data Acquisition items or CAN objects unless ECU Interface Toolkits are present to enable configuring acquisition of ECU data items). 3 Retrieve data files from Network Hub Logger (Including attaching a DBC file upon NONE VISION Base retrieving of the files to convert CAN messages to signals).
    [Show full text]
  • FM-ONE Flash Memory MCU PROGRAMMER for the Operation Procedures
    FM-ONE Flash memory MCU PROGRAMMER For the Operation Procedures CONTENTS◆ IMPORTANT ..................................................................................... 1 ON-BOARD PROGRAMMER ........................................................... 2 FM-ONE FUTURES ................................................ 2 SPECIFICATIONS .................................................... 2 【Package Style】 ................................................................. 2 【Product and contained accessories】................................. 3 【The provided CD includes】 ............................................... 3 【Brief specifications of the main body】 ............................... 4 【Specifications of FM－ONE Project File Maker】 ............... 4 【Parts names】 .................................................................... 5 【Side of body】 .................................................................... 5 Battery Holder Guidance ........................................................... 6 About some changes on display for upgrade ............................ 7 Preparation ................................................................................ 8 Installation of FM-ONE Project File Maker ............. 8 Target board ............................................................. 9 Connector and Cable ................................................ 9 CONNECTION IMAGE ............................................................ 9 Insertion of CF .......................................................... 9 RECOGNITION OF
    [Show full text]
  • Computer Architectures an Overview
    Computer Architectures An Overview PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sat, 25 Feb 2012 22:35:32 UTC Contents Articles Microarchitecture 1 x86 7 PowerPC 23 IBM POWER 33 MIPS architecture 39 SPARC 57 ARM architecture 65 DEC Alpha 80 AlphaStation 92 AlphaServer 95 Very long instruction word 103 Instruction-level parallelism 107 Explicitly parallel instruction computing 108 References Article Sources and Contributors 111 Image Sources, Licenses and Contributors 113 Article Licenses License 114 Microarchitecture 1 Microarchitecture In computer engineering, microarchitecture (sometimes abbreviated to µarch or uarch), also called computer organization, is the way a given instruction set architecture (ISA) is implemented on a processor. A given ISA may be implemented with different microarchitectures.[1] Implementations might vary due to different goals of a given design or due to shifts in technology.[2] Computer architecture is the combination of microarchitecture and instruction set design. Relation to instruction set architecture The ISA is roughly the same as the programming model of a processor as seen by an assembly language programmer or compiler writer. The ISA includes the execution model, processor registers, address and data formats among other things. The Intel Core microarchitecture microarchitecture includes the constituent parts of the processor and how these interconnect and interoperate to implement the ISA. The microarchitecture of a machine is usually represented as (more or less detailed) diagrams that describe the interconnections of the various microarchitectural elements of the machine, which may be everything from single gates and registers, to complete arithmetic logic units (ALU)s and even larger elements.
    [Show full text]
  • Electronic Products and Relays Selection Table Interface Relays CR-Range and R600 / R500 Range Pluggable Interface Relays
    Electronic Products and Relays Selection Table Interface Relays CR-Range and R600 / R500 Range Pluggable Interface Relays CR-M Range Order number number Order 1SVR 405 611 R4000 1SVR 405 611 R1000 1SVR 405 611 R6000 1SVR 405 611 R4200 1SVR 405 611 R8000 1SVR 405 611 R8200 1SVR 405 611 R9000 1SVR 405 611 R0000 1SVR 405 611 R5000 1SVR 405 611 R7000 1SVR 405 611 R2000 1SVR 405 611 R3000 1SVR 405 612 R4000 1SVR 405 612 R1000 1SVR 405 612 R6000 1SVR 405 612 R4200 1SVR 405 612 R8000 1SVR 405 612 R8200 1SVR 405 612 R9000 1SVR 405 612 R0000 1SVR 405 612 R5000 1SVR 405 612 R5200 1SVR 405 612 R7000 1SVR 405 612 R2000 1SVR 405 612 R3000 1SVR 405 613 R4000 1SVR 405 613 R1000 1SVR 405 613 R6000 1SVR 405 613 R4200 1SVR 405 613 R8000 1SVR 405 613 R8200 1SVR 405 613 R9000 1SVR 405 613 R0000 1SVR 405 613 R5000 1SVR 405 613 R7000 1SVR 405 613 R2000 1SVR 405 613 R3000 1SVR 405 611 R4100 1SVR 405 611 R1100 1SVR 405 611 R6100 1SVR 405 611 R4300 1SVR 405 611 R8100 1SVR 405 611 R8300 1SVR 405 611 R9100 1SVR 405 611 R0100 1SVR 405 611 R5100 1SVR 405 611 R7100 1SVR 405 611 R2100 1SVR 405 611 R3100 1SVR 405 612 R4100 1SVR 405 612 R1100 1SVR 405 612 R6100 1SVR 405 612 R4300 1SVR 405 612 R8100 1SVR 405 612 R8300 1SVR 405 612 R9100 1SVR 405 612 R0100 1SVR 405 612 R5100 1SVR 405 612 R7100 1SVR 405 612 R2100 1SVR 405 612 R3100 1SVR 405 613 R4100 1SVR 405 613 R1100 1SVR 405 613 R6100 1SVR 405 613 R4300 1SVR 405 613 R8100 1SVR 405 613 R8300 1SVR 405 613 R9100 1SVR 405 613 R0100 1SVR 405 613 R5100 1SVR 405 613 R7100 1SVR 405 613 R2100 1SVR 405 613 R3100 1SVR 405 614 R1100
    [Show full text]
  • Using and Porting the GNU Compiler Collection
    Using and Porting the GNU Compiler Collection Richard M. Stallman Last updated 14 June 2001 for gcc-3.0 Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001 Free Software Foundation, Inc. For GCC Version 3.0 Published by the Free Software Foundation 59 Temple Place - Suite 330 Boston, MA 02111-1307, USA Last printed April, 1998. Printed copies are available for $50 each. ISBN 1-882114-37-X 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 the Invariant Sections being “GNU General Public License”, the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled “GNU Free Documentation License”. (a) The FSF’s Front-Cover Text is: A GNU Manual (b) The FSF’s Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. Short Contents Introduction......................................... 1 1 Compile C, C++, Objective C, Fortran, Java ............... 3 2 Language Standards Supported by GCC .................. 5 3 GCC Command Options ............................. 7 4 Installing GNU CC ............................... 111 5 Extensions to the C Language Family .................. 121 6 Extensions to the C++ Language ...................... 165 7 GNU Objective-C runtime features .................... 175 8 gcov: a Test Coverage Program ...................... 181 9 Known Causes of Trouble with GCC ................... 187 10 Reporting Bugs.................................
    [Show full text]