DOCSLIB.ORG

Working Successfully Behind the Scenes

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

What’s new at Embedded Systems Conference 2008 Working successfully behind the scenes Embedded systems have shown rapid development embedded systems industry cannot imagine work in the last 15 years. There was a time when they without TRACE32. Whether in Europe, the USA, were only to be found in complex technical products or Asia, TRACE32 is recognized as the premier that were never used in the average household, but product and the world’s leading brand in micropro- now they are everywhere. The general public may cessor development tools, which is borne out by be unaware of them since they are embedded and some very impressive fi gures: In 2007 alone, over 7000 new workplaces worldwide were equipped with TRACE32! WinCE TRACE32 stands for continuity, but mainly for progress and inventive- UML CFI RTOS SMP ness. One or the other is always in the foreground, depending on the branch of industry. In this coming year, we Auto- Nexus DigRF intend to push ahead strongly in the TRACE32 Focus development of our products and in- vest in solid growth so that you can TI DSP continue to rely on Lauterbach as an Power Saving Combi Probe innovative partner. The past year, 2007, was of course not STM ITM a year of standing still. In this news- letter for 2008, we wish to show you the technological progress we have made during the last year. We would like to work behind the scenes, but we in the “embedded encourage you to try some of these new features community” know that every ordinary member of for your development to improve your effi ciency. society comes into contact with them every day. We will be presenting many of these innovations at Whether in the car, cell phone, MP3 player, home the ESC Silicon Valley, to which, as every year, we cinema, washing machine, or cooker – embedded cordially invite you. systems are in daily use in almost all technical de- vices, using one or more microcontrollers, digital signal processors, and of course their respective Contents software. And we, the “embedded community”, have to make sure that everything works perfectly Hardware debugging in UML 3 and without any fuss. New supported processors 8 TRACE32 – a premium product Debugging with power-saving modes 9 Lauterbach was founded 29 years ago in the pio- neering age of embedded systems. It has managed New debugging concept for SMP 13 to turn the challenges of this market into techno- systems logical and economic success by a mixture of the New preprocessors / NEXUS adapters 17 right know-how and enormous commitment. Just as we can no longer imagine items of daily use CombiProbe 18 without embedded systems, a developer in the www.lauterbach.com NEWS 2008 DEBUGGER, REAL-TIME TRACE, LOGIC ANALYZER TRACE32 for Virtual Prototypes Virtual Prototypes PowerView Today, fast and effi cient software development is CoWare® CoWare ARM often the decisive factor in the launching of new Virtual Platform products. To avoid having to wait for the fi rst hard- ware prototypes at the start of the development PowerDebug Synopsys® Virtual Platform ARM phase, Virtual Prototypes (software models of the (formerly Virtio) XScale hardware) are becoming increasingly common. Virtual Prototype VaST ™ VaST ARM As soon as a is available for the PowerTrace target hardware, work can start on debugging the Virtual System OAK drivers, the operating system, and the application. Prototype PowerPC/eTPU So that we can offer our customers the profes- SH2A PowerProbe sional development environment TRACE32 in this StarCore early phase of their project, Lauterbach has been TeakLite supporting the debugging of software models TriCore/PCP since 2007. The debugging interface used here is Power- V850 the debugging API of the Virtual Prototype. Integrator TRACE32 as GDB front end GDB front end Other innovations ARM Available In the 2007 Newsletter, Lauterbach announced I386 Available “Integrated run- & stop-mode debugging for em- MIPS32 Available bedded Linux applications”. This year this is fol- lowed by a new concept for debugging SMP Linux PowerPC Available (see page 13). SH4 Planned XScale Available TRACE32 GUI Since early 2007, the TRACE32 GUI can also be used for process debugging with GDB. The sup- Ethernet / RS-232 ported communication interfaces to the target Embedded LINUX hardware are Ethernet or RS-232. t32server Debugging application processes GDB GDB GDB To debug two or more application processes simul- server 1 server 2 server 3 taneously, Lauterbach provides its own debugging agent – t32server, which is started fi rst in the Linux terminal window. Subsequently via the TRACE32 Task Task Task GUI several GDB servers for testing application 1 2 3 processes can be started. The t32server service is then responsible for data exchange between the Fig. 1: The t32server service, enabling simultaneous debugging of TRACE32 GUI and the GDB servers (see Fig. 1). two or more application processes 2 www.lauterbach.com NEWS 2007 NEWS 2008 DEBUGGER, REAL-TIME TRACE, LOGIC ANALYZER Integration, testing, and debugging of C code together with UML-generated sources PowerView Old C code At the outset, we have a fi nished project in C code. The following example uses a traffi c light system PowerDebug (which is a favorite of software designers due to its simplicity). There is a standard intersection with four sets of traffi c lights. The traffi c lights located opposite each other are controlled in parallel. The PowerTrace traffi c lights at the right angle to them are, of course, controlled complementary. The different traffi c light phases are: red – red and yellow – green – yellow – red. During the red phase of one set of traffi c lights, PowerProbe right of way switches to the opposite direction. As a result, there is a short period when the lights Fig. 2: Adding tram traffi c lights to a traffi c intersection facing in all directions are on red (this is important, Power- as we shall see later). Integrator Introduction This circuit is coded in C as a simple control (switch- It will soon no longer be possible to master the case) in a continuous loop (while (1)). This continu- growing complexity of software without the use of ous loop is found directly in the “main()” routine of CASE tools. UML, especially, has enabled the uni- the application, and is called immediately after ini- form design of modular software components, in- tialization (see Fig. 3). cluding automatic code generation, which prevents common coding errors right from the start. ... However many companies shy away from the per- int main (void) { ceived effort required for the changeover to these horizontal = vertical = red; new techniques. They have a code base that has state = closed_to_h; been built up over decades and although the soft- while (1) ware has been constantly extended and improved. { This has also led to the creation of more and more switch (state) “spaghetti code”. Millions of functioning lines of { case closed_to_h: code would need to be analyzed, re-programmed, wait (1); and fi nally re-tested. horizontal = yellowred; state = yellowred_h; In most cases these fears are unfounded. Existing break; C code can be transferred to a UML model element with almost no changes necessary. Future exten- case yellowred_h: wait (3); sions can then be written as UML models, gener- horizontal = green ated, and integrated with the “old” C code. As a state = green_h; result, an easy and progressive transition from C to break; UML is possible. The following example explains ... these procedures: Fig. 3: Existing C code for traffi c-light control; the “main()” routine 1. Transfer from “old” C code to UML. includes a continuous loop that contains the logic as a switch- case construct. 2. Integration of a new functionality coded in UML. 3. Uniform testing and debugging in UML, C++ New requirements and C. The street planners have decided that a tramline should cross the intersection in both directions 〉〉 www.lauterbach.com 3 NEWS 2008 DEBUGGER, REAL-TIME TRACE, LOGIC ANALYZER (vertically as well as horizontally, refer to Fig. 2 on main() is already part of the framework and there- page 3). Therefore, the trams must be stopped at fore has to be omitted. Instead, “main()” is renamed PowerView the intersection by their own set of traffi c lights. At “processJunction()”, and this becomes our new the request of the tram driver, the intersection is starting point. The end point of the function will be blocked for cars at the next red light phase, and the the phase when all traffi c lights are on red. Now, if PowerDebug tram is given right of way. required, we can execute additional actions during this red phase (see Fig. 5). – And that’s it. UML wrapper for C code We could, of course, just “patch” these require- UML design for new requirements PowerTrace ments into our C code. But doing so would only Now we can take care of the design for the new make the function larger and more complicated, requirements. We build a class called “Junction”, which is exactly what we want to avoid. So instead which contains the old traffi c light controls, called PowerProbe of this, we will take a modular approach to the “CarJunction”, as well as two new tram traffi c lights problem and solve it with the help of UML. (Fig. 6). The design is now fi nished, and we can Firstly, we need to “trans- focus on the behavior of the extended intersection, Power- fer” the existing appli- using a state transition diagram. Integrator cation over to our UML model, which is easier than it sounds: We create one class, called “Car- Fig. 4: The “CarJunction” Junction”, which contains class, containing the com- the complete “old” appli- plete “old” application cation (see Fig.
Recommended publications
  • ARM Architecture

    ARM Architecture

    ARM Architecture Comppgzuter Organization and Assembly ygg Languages Yung-Yu Chuang with slides by Peng-Sheng Chen, Ville Pietikainen ARM history • 1983 developed by Acorn computers – To replace 6502 in BBC computers – 4-man VLSI design team – Its simp lic ity comes from the inexper ience team – Match the needs for generalized SoC for reasonable power, performance and die size – The first commercial RISC implemenation • 1990 ARM (Advanced RISC Mac hine ), owned by Acorn, Apple and VLSI ARM Ltd Design and license ARM core design but not fabricate Why ARM? • One of the most licensed and thus widespread processor cores in the world – Used in PDA, cell phones, multimedia players, handheld game console, digital TV and cameras – ARM7: GBA, iPod – ARM9: NDS, PSP, Sony Ericsson, BenQ – ARM11: Apple iPhone, Nokia N93, N800 – 90% of 32-bit embedded RISC processors till 2009 • Used especially in portable devices due to its low power consumption and reasonable performance ARM powered products ARM processors • A simple but powerful design • A whlhole filfamily of didesigns shiharing siilimilar didesign principles and a common instruction set Naming ARM •ARMxyzTDMIEJFS – x: series – y: MMU – z: cache – T: Thumb – D: debugger – M: Multiplier – I: EmbeddedICE (built-in debugger hardware) – E: Enhanced instruction – J: Jazell e (JVM) – F: Floating-point – S: SthiiblSynthesizible version (source code version for EDA tools) Popular ARM architectures •ARM7TDMI – 3 pipe line stages (ft(fetc h/deco de /execu te ) – High code density/low power consumption – One of the most used ARM-version (for low-end systems) – All ARM cores after ARM7TDMI include TDMI even if they do not include TDMI in their labels • ARM9TDMI – Compatible with ARM7 – 5 stages (fe tc h/deco de /execu te /memory /wr ite ) – Separate instruction and data cache •ARM11 ARM family comparison year 1995 1997 1999 2003 ARM is a RISC • RISC: simple but powerful instructions that execute within a single cycle at high clock speed.
  • Micro-Circuits for High Energy Physics*

    Micro-Circuits for High Energy Physics*

    MICRO-CIRCUITS FOR HIGH ENERGY PHYSICS* Paul F. Kunz Stanford Linear Accelerator Center Stanford University, Stanford, California, U.S.A. ABSTRACT Microprogramming is an inherently elegant method for implementing many digital systems. It is a mixture of hardware and software techniques with the logic subsystems controlled by "instructions" stored Figure 1: Basic TTL Gate in a memory. In the past, designing microprogrammed systems was difficult, tedious, and expensive because the available components were capable of only limited number of functions. Today, however, large blocks of microprogrammed systems have been incorporated into a A input B input C output single I.e., thus microprogramming has become a simple, practical method. false false true false true true true false true true true false 1. INTRODUCTION 1.1 BRIEF HISTORY OF MICROCIRCUITS Figure 2: Truth Table for NAND Gate. The first question which arises when one talks about microcircuits is: What is a microcircuit? The answer is simple: a complete circuit within a single integrated-circuit (I.e.) package or chip. The next question one might ask is: What circuits are available? The answer to this question is also simple: it depends. It depends on the economics of the circuit for the semiconductor manufacturer, which depends on the technology he uses, which in turn changes as a function of time. Thus to understand Figure 3: Logical NOT Circuit. what microcircuits are available today and what makes them different from those of yesterday it is interesting to look into the economics of producing microcircuits. The basic element in a logic circuit is a gate, which is a circuit with a number of inputs and one output and it performs a basic logical function such as AND, OR, or NOT.
  • Computer Architecture Out-Of-Order Execution

    Computer Architecture Out-Of-Order Execution

    Computer Architecture Out-of-order Execution By Yoav Etsion With acknowledgement to Dan Tsafrir, Avi Mendelson, Lihu Rappoport, and Adi Yoaz 1 Computer Architecture 2013– Out-of-Order Execution The need for speed: Superscalar • Remember our goal: minimize CPU Time CPU Time = duration of clock cycle × CPI × IC • So far we have learned that in order to Minimize clock cycle ⇒ add more pipe stages Minimize CPI ⇒ utilize pipeline Minimize IC ⇒ change/improve the architecture • Why not make the pipeline deeper and deeper? Beyond some point, adding more pipe stages doesn’t help, because Control/data hazards increase, and become costlier • (Recall that in a pipelined CPU, CPI=1 only w/o hazards) • So what can we do next? Reduce the CPI by utilizing ILP (instruction level parallelism) We will need to duplicate HW for this purpose… 2 Computer Architecture 2013– Out-of-Order Execution A simple superscalar CPU • Duplicates the pipeline to accommodate ILP (IPC > 1) ILP=instruction-level parallelism • Note that duplicating HW in just one pipe stage doesn’t help e.g., when having 2 ALUs, the bottleneck moves to other stages IF ID EXE MEM WB • Conclusion: Getting IPC > 1 requires to fetch/decode/exe/retire >1 instruction per clock: IF ID EXE MEM WB 3 Computer Architecture 2013– Out-of-Order Execution Example: Pentium Processor • Pentium fetches & decodes 2 instructions per cycle • Before register file read, decide on pairing Can the two instructions be executed in parallel? (yes/no) u-pipe IF ID v-pipe • Pairing decision is based… On data
  • Parallel Computing

    Parallel Computing

    Lecture 1: Computer Organization 1 Outline • Overview of parallel computing • Overview of computer organization – Intel 8086 architecture • Implicit parallelism • von Neumann bottleneck • Cache memory – Writing cache-friendly code 2 Why parallel computing • Solving an × linear system Ax=b by using Gaussian elimination takes ≈ flops. 1 • On Core i7 975 @ 4.0 GHz,3 which is capable of about 3 60-70 Gigaflops flops time 1000 3.3×108 0.006 seconds 1000000 3.3×1017 57.9 days 3 What is parallel computing? • Serial computing • Parallel computing https://computing.llnl.gov/tutorials/parallel_comp 4 Milestones in Computer Architecture • Analytic engine (mechanical device), 1833 – Forerunner of modern digital computer, Charles Babbage (1792-1871) at University of Cambridge • Electronic Numerical Integrator and Computer (ENIAC), 1946 – Presper Eckert and John Mauchly at the University of Pennsylvania – The first, completely electronic, operational, general-purpose analytical calculator. 30 tons, 72 square meters, 200KW. – Read in 120 cards per minute, Addition took 200µs, Division took 6 ms. • IAS machine, 1952 – John von Neumann at Princeton’s Institute of Advanced Studies (IAS) – Program could be represented in digit form in the computer memory, along with data. Arithmetic could be implemented using binary numbers – Most current machines use this design • Transistors was invented at Bell Labs in 1948 by J. Bardeen, W. Brattain and W. Shockley. • PDP-1, 1960, DEC – First minicomputer (transistorized computer) • PDP-8, 1965, DEC – A single bus
  • Realtime Capabilities of Low-End Powerpc and ARM Boards for Embedded Systems

    Realtime Capabilities of Low-End Powerpc and ARM Boards for Embedded Systems

    Realtime capabilities of low-end PowerPC and ARM boards for embedded systems Alexander Bauer PHYTEC Messtechnik Gmbh Robert-Koch-Str.39, 55129 Mainz, Germany [email protected] Abstract With the stepwise integration of the Realtime Preemption Patches (RT-Preempt) into the Mainline Linux kernel and their support for architectures other than Intel and AMD, there are now a number of choices which board to use for a particular embedded realtime project running Mainline Linux. In order to select the appropriate processor and clock frequency, it would be desirable to have some generally applicable ranges of worst-case latencies that can be obtained using the various processor types and conditions. We, therefore, determined the internal worst-case latency of PowerPC and ARM boards running Linux 2.6.20 and above patched with RT-Preempt. The PowerPC-board (Phytec phyCORE-MPC5200B) was running at 266 and 400 MHz, the ARM board (Phytec phyCORE-PXA270) was running at 266 and 520 MHz. This article will provide the details of the various measurement set-ups, present the results and discuss them with respect to the design differences between PowerPC and ARM. 1 Introduction This paper presents the results of the latency tests and discusses the results with respect of the different In the embedded market there is a wide range of processor designs. processors to choose from. A processor is typically selected for a customer design because of it features, e.g. video interface and peripherals, and the clock 2 Latency Tests frequency. With the growing importance of Linux and especially realtime Linux for customer designs For the latency tests based on MPC5200 we used in the embedded market, it is also essential to choose the PHYTEC phyCORE MPC5200 board with 400 the right processor that will cope with the realtime MHz as a reference platform.
  • SEWIP Program Leverages COTS P 36 P 28 an Interview with Deon Viergutz, Vice President of Cyber Solutions at Lockheed Martin Information Systems & Global Solutions

    SEWIP Program Leverages COTS P 36 P 28 an Interview with Deon Viergutz, Vice President of Cyber Solutions at Lockheed Martin Information Systems & Global Solutions

    @military_cots John McHale Obsolescence trends 8 Special Report Shipboard displays 44 Mil Tech Trends Predictive analytics 52 Industry Spotlight Aging avionics software 56 MIL-EMBEDDED.COM September 2015 | Volume 11 | Number 6 RESOURCE GUIDE 2015 P 62 Navy SEWIP program leverages COTS P 36 P 28 An interview with Deon Viergutz, Vice President of Cyber Solutions at Lockheed Martin Information Systems & Global Solutions Military electronics market overview P 14 Volume 11 Number 6 www.mil-embedded.com September 2015 COLUMNS BONUS – MARKET OVERVIEW Editor’s Perspective 14 C4ISR funding a bright spot in military 8 Tech mergers & military electronics electronics market obsolescence By John McHale, Editorial Director By John McHale Q&A EXECUTIVE OUTLOOK Field Intelligence 10 Metadata: When target video 28 Defending DoD from cyberattacks, getting to data is not enough the left of the boom By Charlotte Adams 14 An interview with Deon Viergutz, Vice President of Cyber Solutions at Lockheed Martin Information Mil Tech Insider Systems & Global Solutions 12 Broadwell chip boosts GPU performance for COTS SBCs 32 RF and microwave innovation drives military By Aaron Frank radar and electronic warfare applications An interview with Bryan Goldstein, DEPARTMENTS General Manager of the Aerospace and Defense, Analog Devices 22 Defense Tech Wire By Mariana Iriarte SPECIAL REPORT 60 Editor’s Choice Products Shipboard Electronics 112 University Update 36 U.S. Navy’s electronic warfare modernization On DARPA’s cybersecurity radar: 36 effort centers on COTS Algorithmic and side-channel attacks By Sally Cole, Senior Editor By Sally Cole 114 Connecting with Mil Embedded 44 Key to military display technologies: Blog – The fascinating world of System integration By Tom Whinfrey, IEE Inc.
  • Programmable Digital Microcircuits - a Survey with Examples of Use

    Programmable Digital Microcircuits - a Survey with Examples of Use

    - 237 - PROGRAMMABLE DIGITAL MICROCIRCUITS - A SURVEY WITH EXAMPLES OF USE C. Verkerk CERN, Geneva, Switzerland 1. Introduction For most readers the title of these lecture notes will evoke microprocessors. The fixed instruction set microprocessors are however not the only programmable digital mi• crocircuits and, although a number of pages will be dedicated to them, the aim of these notes is also to draw attention to other useful microcircuits. A complete survey of programmable circuits would fill several books and a selection had therefore to be made. The choice has rather been to treat a variety of devices than to give an in- depth treatment of a particular circuit. The selected devices have all found useful ap• plications in high-energy physics, or hold promise for future use. The microprocessor is very young : just over eleven years. An advertisement, an• nouncing a new era of integrated electronics, and which appeared in the November 15, 1971 issue of Electronics News, is generally considered its birth-certificate. The adver• tisement was for the Intel 4004 and its three support chips. The history leading to this announcement merits to be recalled. Intel, then a very young company, was working on the design of a chip-set for a high-performance calculator, for and in collaboration with a Japanese firm, Busicom. One of the Intel engineers found the Busicom design of 9 different chips too complicated and tried to find a more general and programmable solu• tion. His design, the 4004 microprocessor, was finally adapted by Busicom, and after further négociation, Intel acquired marketing rights for its new invention.
  • RISC-V Geneology

    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.
  • Design of the RISC-V Instruction Set Architecture

    Design of the RISC-V Instruction Set Architecture

    Design of the RISC-V Instruction Set Architecture Andrew Waterman Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2016-1 http://www.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-1.html January 3, 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. Design of the RISC-V Instruction Set Architecture by Andrew Shell Waterman A dissertation submitted in partial satisfaction of the requirements for the degree of Doctor of Philosophy in Computer Science in the Graduate Division of the University of California, Berkeley Committee in charge: Professor David Patterson, Chair Professor Krste Asanovi´c Associate Professor Per-Olof Persson Spring 2016 Design of the RISC-V Instruction Set Architecture Copyright 2016 by Andrew Shell Waterman 1 Abstract Design of the RISC-V Instruction Set Architecture by Andrew Shell Waterman Doctor of Philosophy in Computer Science University of California, Berkeley Professor David Patterson, Chair The hardware-software interface, embodied in the instruction set architecture (ISA), is arguably the most important interface in a computer system. Yet, in contrast to nearly all other interfaces in a modern computer system, all commercially popular ISAs are proprietary.
  • Computer Architectures an Overview

    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.
  • A Bibliography of Publications in IEEE Micro

    A Bibliography of Publications in IEEE Micro

    A Bibliography of Publications in IEEE Micro Nelson H. F. Beebe University of Utah Department of Mathematics, 110 LCB 155 S 1400 E RM 233 Salt Lake City, UT 84112-0090 USA Tel: +1 801 581 5254 FAX: +1 801 581 4148 E-mail: [email protected], [email protected], [email protected] (Internet) WWW URL: http://www.math.utah.edu/~beebe/ 16 September 2021 Version 2.108 Title word cross-reference -Core [MAT+18]. -Cubes [YW94]. -D [ASX19, BWMS19, DDG+19, Joh19c, PZB+19, ZSS+19]. -nm [ABG+16, KBN16, TKI+14]. #1 [Kah93i]. 0.18-Micron [HBd+99]. 0.9-micron + [Ano02d]. 000-fps [KII09]. 000-Processor $1 [Ano17-58, Ano17-59]. 12 [MAT 18]. 16 + + [ABG+16]. 2 [DTH+95]. 21=2 [Ste00a]. 28 [BSP 17]. 024-Core [JJK 11]. [KBN16]. 3 [ASX19, Alt14e, Ano96o, + AOYS95, BWMS19, CMAS11, DDG+19, 1 [Ano98s, BH15, Bre10, PFC 02a, Ste02a, + + Ste14a]. 1-GHz [Ano98s]. 1-terabits DFG 13, Joh19c, LXB07, LX10, MKT 13, + MAS+07, PMM15, PZB+19, SYW+14, [MIM 97]. 10 [Loc03]. 10-Gigabit SCSR93, VPV12, WLF+08, ZSS+19]. 60 [Gad07, HcF04]. 100 [TKI+14]. < [BMM15]. > [BMM15]. 2 [Kir84a, Pat84, PSW91, YSMH91, ZACM14]. [WHCK18]. 3 [KBW95]. II [BAH+05]. ∆ 100-Mops [PSW91]. 1000 [ES84]. 11- + [Lyl04]. 11/780 [Abr83]. 115 [JBF94]. [MKG 20]. k [Eng00j]. µ + [AT93, Dia95c, TS95]. N [YW94]. x 11FO4 [ASD 05]. 12 [And82a]. [DTB01, Dur96, SS05]. 12-DSP [Dur96]. 1284 [Dia94b]. 1284-1994 [Dia94b]. 13 * [CCD+82]. [KW02]. 1394 [SB00]. 1394-1955 [Dia96d]. 1 2 14 [WD03]. 15 [FD04]. 15-Billion-Dollar [KR19a].
  • The ARM Instruction Set Architecture

    The ARM Instruction Set Architecture

    EE382N-4 Embedded Systems Architecture The ARM Instruction Set Architecture Mark McDermott With help from our good friends at ARM Fall 2008 8/22/2008 EE382N-4 Embedded Systems Architecture Main features of the ARM Instruction Set All instructions are 32 bits long. Most instructions execute in a single cycle. Most instructions can be conditionally executed. A load/store architecture – Data processing instructions act only on registers • Three operand format • Combined ALU and shifter for high speed bit manipulation – Specific memory access instructions with powerful auto‐indexing addressing modes. • 32 bit and 8 bit data types – and also 16 bit data types on ARM Architecture v4. • Flexible multiple register load and store instructions Instruction set extension via coprocessors Very dense 16‐bit compressed instruction set (Thumb) 8/22/2008 2 EE382N-4 Embedded Systems Architecture Coprocessors – Up to 16 coprocessors can be defined – Expands the ARM instruction set – Each coprocessor can have up to 16 private registers of any reasonable size – Load‐store architecture 3 EE382N-4 Embedded Systems Architecture Thumb Thumb is a 16‐bit instruction set – Optimized for code density from C code – Improved performance form narrow memory – Subset of the functionality of the ARM instruction set Core has two execution states –ARM and Thumb – Switch between them using BX instruction Thumb has characteristic features: – Most Thumb instruction are executed unconditionally – Many Thumb data process instruction use a 2‐address format – Thumb instruction