NVAX Plus CPU Chip Functional Specification

Total Page:16

File Type:pdf, Size:1020Kb

NVAX Plus CPU Chip Functional Specification NVAX Plus CPU Chip Functional Specification The NVAX Plus CPU Chip is a high-performance, single-chip implementation of the VAX Architecture for use in low-end and mid-range systems. Revision/Update Information: This is Revision 0.1 of this specification, the initial external release DIGITAL RESTRICTED DISTRIBUTION This information shall not be disclosed to persons other than DIGITAL employees or generally distributed within DIGITAL. Distribution is restricted to persons authorized and designated by the originating organization. This document shall not be transmitted electronically, copied unless authorized by the originating organization, or left unattended. When not in use, this document shall be stored in a locked storage area. These restrictions are enforced until this document is reclassified by the originating organization. Semiconductor Engineering Group Digital Equipment Corporation, Hudson, Massachusetts This is copy number February 1991 The drawings and specifications in this document are the property of Digital Equipment Corporation and shall not be reproduced or copied or used in whole or in part as the basis for the manufacture or sale of items without written permission. The information in this document may be changed without notice and is not a commitment by Digital Equipment Corporation. Digital Equipment Corporation is not responsible for any errors in this document. This specification does not describe any program or product that is currently available from Digital Equipment Corporation, nor is Digital Equipment Corporation committed to implement this specification in any program or product. Digital Equipment Corporation makes no commitment that this document accurately describes any product it might ever make. Copyright ©1991 by Digital Equipment Corporation All Rights Reserved Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DEC ULTRIX VAXstation DECnet ULTRIX–32 VMS DECUS UNIBUS VT MicroVAX VAX MicroVMS VAXBI TM PDP VAXcluster d i g i t a l Contents CHAPTER 1 INTRODUCTION 1–1 1.1 SCOPE AND ORGANIZATION OF THIS SPECIFICATION 1–1 1.2 RELATED DOCUMENTS 1–1 1.3 TERMINOLOGY AND CONVENTIONS 1–2 1.3.1 Numbering 1–2 1.3.2 UNPREDICTABLE and UNDEFINED 1–2 1.3.3 Ranges and Extents 1–2 1.3.4 Must be Zero (MBZ) 1–2 1.3.5 Should be Zero (SBZ) 1–2 1.3.6 Register Format Notation 1–3 1.3.7 Timing Diagram Notation 1–5 1.4 REVISION HISTORY 1–6 CHAPTER 2 ARCHITECTURAL SUMMARY 2–1 2.1 OVERVIEW 2–1 2.2 VISIBLE STATE 2–1 2.2.1 Virtual Address Space 2–1 2.2.2 Physical Address Space 2–2 2.2.2.1 Physical Address Control Registers • 2–4 2.2.3 Registers 2–4 2.3 DATA TYPES 2–6 2.4 INSTRUCTION FORMATS AND ADDRESSING MODES 2–8 2.4.1 Opcode Formats 2–8 2.4.2 Addressing Modes 2–8 2.4.3 Branch Displacements 2–11 2.5 INSTRUCTION SET 2–11 2.6 MEMORY MANAGEMENT 2–25 2.6.1 Memory Management Control Registers 2–25 2.6.2 System Space Address Translation 2–26 2.6.3 Process Space Address Translation 2–27 2.6.3.1 P0 Region Address Translation • 2–27 2.6.3.2 P1 Region Address Translation • 2–28 2.6.4 Page Table Entry 2–30 2.6.5 Translation Buffer 2–31 2.7 EXCEPTIONS AND INTERRUPTS 2–32 2.7.1 Interrupts 2–32 2.7.1.1 Interrupt Control Registers • 2–33 DIGITAL RESTRICTED DISTRIBUTION iii Contents 2.7.2 Exceptions 2–34 2.7.2.1 Arithmetic Exceptions • 2–35 2.7.2.2 Memory Management Exceptions • 2–36 2.7.2.3 Emulated Instruction Exceptions • 2–37 2.7.2.4 Machine Check Exceptions • 2–39 2.7.2.5 Console Halts • 2–39 2.8 SYSTEM CONTROL BLOCK 2–40 2.8.1 System Control Block Vectors 2–40 2.8.2 System Control Block Layout 2–41 2.9 CPU IDENTIFICATION 2–43 2.10 SYSTEM IDENTIFICATION 2–43 2.11 PROCESS STRUCTURE 2–45 2.12 MAILBOX STRUCTURE 2–47 2.12.1 Mailbox Operation 2–49 2.13 PROCESSOR REGISTERS 2–51 2.14 REVISION HISTORY 2–62 CHAPTER 3 EXTERNAL INTERFACE 3–1 3.1 OVERVIEW 3–1 3.2 SIGNALS 3–1 3.2.1 Clocks 3–3 3.2.2 DC_OK and Reset 3–4 3.2.3 Initialization and Diagnostic Interface 3–5 3.2.4 Address Bus 3–5 3.2.5 Data Bus 3–6 3.2.6 External Cache Control 3–7 3.2.6.1 The TagAdr RAM • 3–7 3.2.6.2 The TagCtl RAM • 3–8 3.2.6.3 The Data RAM • 3–8 3.2.6.4 Backmaps • 3–9 3.2.6.5 External Cache Access • 3–9 3.2.6.5.1 HoldReq and HoldAck • 3–9 3.2.6.5.2 TagOk • 3–10 3.2.7 External Cycle Control 3–11 3.2.8 Primary Cache Invalidate 3–13 3.2.9 Interrupts 3–14 3.2.10 Electrical Level Configuration 3–14 3.2.11 Testing 3–14 3.3 64-BIT MODE 3–14 3.4 TRANSACTIONS 3–14 3.4.1 Reset 3–14 3.4.2 Fast External Cache Read Hit 3–15 3.4.3 Fast External Cache Write Hit 3–16 3.4.4 Fast External Cache Byte/Word Write Hit 3–16 3.4.5 Transfer to SysClk for External tranactions 3–17 iv DIGITAL RESTRICTED DISTRIBUTION Contents 3.4.6 READ_BLOCK Transaction 3–17 3.4.7 Write Block 3–18 3.4.8 LDxL Transaction 3–19 3.4.9 STxC Transaction 3–20 3.4.10 BARRIER Transaction 3–21 3.4.11 FETCH Transaction 3–21 3.4.12 FETCHM Transaction 3–21 3.5 SUMMARY OF NVAX PLUS OPTIONS 3–21 3.6 REVISION HISTORY 3–22 CHAPTER 4 CHIP OVERVIEW 4–1 4.1 NVAX PLUS CPU CHIP BOX AND SECTION OVERVIEW 4–1 4.1.1 The Ibox 4–2 4.1.2 The Ebox and Microsequencer 4–3 4.1.3 The Fbox 4–3 4.1.4 The Mbox 4–4 4.1.5 The Cbox 4–4 4.1.6 Major Internal Buses 4–4 4.2 REVISION HISTORY 4–5 CHAPTER 5 MACROINSTRUCTION AND MICROINSTRUCTION PIPELINES 5–1 5.1 INTRODUCTION 5–1 5.2 PIPELINE FUNDAMENTALS 5–1 5.2.1 The Concept of a Pipeline 5–1 5.2.2 Pipeline Flow 5–3 5.2.3 Stalls and Exceptions in an Instruction Pipeline 5–5 5.3 NVAX PLUS CPU PIPELINE OVERVIEW 5–6 5.3.1 Normal Macroinstruction Execution 5–8 5.3.1.1 The Ibox • 5–8 5.3.1.2 The Microsequencer • 5–9 5.3.1.3 The Ebox • 5–9 5.3.1.4 The Fbox • 5–10 5.3.1.5 The Mbox • 5–10 5.3.1.6 The Cbox • 5–11 5.3.2 Stalls in the Pipeline 5–11 5.3.2.1 S0 Stalls • 5–12 5.3.2.2 S1 Stalls • 5–12 5.3.2.3 S2 Stalls • 5–13 5.3.2.4 S3 Stalls • 5–14 5.3.2.5 S4 Stalls • 5–15 5.3.3 Exception Handling 5–16 5.3.3.1 Interrupts • 5–17 5.3.3.2 Integer Arithmetic Exceptions • 5–17 5.3.3.3 Floating Point Arithmetic Exceptions • 5–17 5.3.3.4 Memory Management Exceptions • 5–18 5.3.3.5 Translation Buffer Miss • 5–19 5.3.3.6 Reserved Addressing Mode Faults • 5–19 5.3.3.7 Reserved Operand Faults • 5–20 DIGITAL RESTRICTED DISTRIBUTION v Contents 5.3.3.8 Exceptions Occurring as the Consequence of an Instruction • 5–20 5.3.3.9 Trace Fault • 5–20 5.3.3.10 Conditional Branch Mispredict • 5–20 5.3.3.11 First Part Done Handling • 5–21 5.3.3.12 Cache and Memory Hardware Errors • 5–21 5.4 REVISION HISTORY 5–22 CHAPTER 6 MICROINSTRUCTION FORMATS 6–1 6.1 EBOX MICROCODE 6–1 6.1.1 Data Path Control 6–1 6.1.2 Microsequencer Control 6–3 6.2 IBOX CSU MICROCODE 6–4 6.3 REVISION HISTORY 6–5 CHAPTER 7 THE IBOX 7–1 7.1 OVERVIEW 7–1 7.1.1 Introduction 7–1 7.1.2 Functional Overview 7–2 7.2 VIC CONTROL AND ERROR REGISTERS 7–4 7.3 VIC PERFORMANCE MONITORING HARDWARE 7–6 7.4 IBOX IPR TRANSACTIONS 7–7 7.4.1 IPR Reads 7–7 7.4.2 IPR Writes 7–7 7.5 BRANCH PREDICTION IPR REGISTER 7–8 7.6 TESTABILITY 7–9 7.6.1 Overview 7–9 7.6.2 Internal Scan Register and Data Reducer 7–9 7.6.3 Parallel Port 7–10 7.6.4 Architectural Features 7–10 7.6.5 Metal 3 Nodes 7–10 7.6.6 Issues 7–10 7.7 PERFORMANCE MONITORING HARDWARE 7–10 7.7.1 Signals 7–10 7.8 REVISION HISTORY 7–11 CHAPTER 8 THE EBOX 8–1 8.1 CHAPTER OVERVIEW 8–1 8.2 INTRODUCTION 8–1 8.3 EBOX OVERVIEW 8–4 8.3.1 Microword Fields 8–4 8.3.1.1 Microsequencer Control Fields • 8–6 8.3.2 The Register File 8–6 vi DIGITAL RESTRICTED DISTRIBUTION Contents 8.3.3 ALU and Shifter 8–6 8.3.3.1 Sources of ALU and Shifter Operands • 8–6 8.3.3.2 ALU Functions • 8–6 8.3.3.3 Shifter Functions • 8–6 8.3.3.4 Destinations of ALU and Shifter Results • 8–7 8.3.4 Ibox-Ebox Interface 8–7 8.3.5 Other Registers and States 8–8 8.3.6 Ebox Memory Access 8–9 8.3.7 CPU Control Functions 8–9 8.3.8 Ebox Pipeline 8–9 8.3.9 Pipeline Stalls 8–10 8.3.10 Microtraps, Exceptions, and Interrupts 8–11 8.3.11 Ebox IPRs 8–12 8.3.11.1 IPR 124, Patchable Control Store Control Register • 8–12 8.3.11.2 IPR 125, Ebox Control Register • 8–13 8.3.12 Initialization 8–14 8.3.13 Testability 8–14 8.3.13.1 Parallel Port Test Features • 8–14 8.3.13.2 Observe Scan • 8–15 8.3.13.3 E%WBUS<31:0> LFSR • 8–15 8.3.14 Revision History 8–15 CHAPTER 9 THE MICROSEQUENCER 9–1 9.1 OVERVIEW 9–1 9.2 FUNCTIONAL DESCRIPTION 9–1 9.2.1 Introduction 9–2 9.2.2 Control Store 9–2 9.2.2.1 Patchable Control Store • 9–2 9.2.2.2 Microsequencer Control Field of Microcode • 9–2 9.2.2.3 MIB Latches • 9–4 9.2.3 Next Address Logic 9–5 9.2.3.1 CAL and CAL INPUT BUS • 9–5 9.2.3.1.1 Microtest Bus • 9–5 9.2.3.2 Microtrap Logic • 9–7 9.2.3.3 Last Cycle Logic • 9–7 9.2.3.4 Microstack • 9–8 9.2.4 Stall Logic 9–8 9.3 INITIALIZATION 9–8 9.4 MICROCODE RESTRICTIONS 9–8 9.5 TESTABILITY 9–9 9.5.1 Test Address 9–9 9.5.2 MIB Scan Chain 9–10 9.6 REVISION HISTORY 9–10 DIGITAL RESTRICTED DISTRIBUTION vii Contents CHAPTER 10 THE INTERRUPT SECTION 10–1 10.1 OVERVIEW 10–1 10.2 INTERRUPT SUMMARY 10–1 10.2.1 External Interrupt Requests Received by Level-Sensitive Logic 10–2 10.2.2 Internal Interrupt Requests 10–2 10.2.3 Special Considerations for Interval Timer Interrupts 10–3 10.2.4 Priority of Interrupt Requests 10–3 10.3 INTERRUPT SECTION STRUCTURE 10–5 10.3.1 Synchronization Logic 10–5 10.3.2 Interrupt State Register 10–6 10.3.3 Interrupt Generation Logic 10–7 10.4 EBOX MICROCODE INTERFACE 10–8 10.5 PROCESSOR REGISTER INTERFACE 10–10 10.6 INTERRUPT SECTION INTERFACES 10–11 10.6.1 Ebox Interface 10–11 10.6.1.1 Signals From Ebox • 10–11 10.6.1.2 Signals To Ebox • 10–11 10.6.2 Microsequencer Interface 10–11 10.6.2.1 Signals from Microsequencer • 10–11 10.6.2.2 Signals To Microsequencer • 10–11 10.6.3
Recommended publications
  • Engineering Specification for the KA43 Processor Module Revision 1.0 1–May–1989 COMPANY CONFIDENTIAL RESTRICTED DISTRIBUTION
    Engineering Specification for the KA43 Processor Module Revision 1.0 1–May–1989 COMPANY CONFIDENTIAL RESTRICTED DISTRIBUTION COPYRIGHT (c) 1989 by DIGITAL EQUIPMENT CORPORATION This information shall not be disclosed to non-Digital personnel or generally distributed within Digital. Distribution is restricted to persons authorized and designated by the responsible en- gineer or manager. This document shall not be left unattended, and when not in use shall be stored in a locked storage container. The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may occur in this document. The information in this document does not describe any program or product currently available from Digital Equipment Corporation. Nor does Digital Equipment Corporation commit to imple- ment this specification in any program or product. Digital Equipment Corporation makes no commitment that this document accurately describes any product which it might ever make. Digital Equipment Corporation CONTENTS Preface . ........................................................... v Chapter 1 INTRODUCTION .............................................. 1 1.1 Scope of Document ................................................... 1 1.2 General Description .................................................. 1 1.3 Applicable Documents ................................................. 2 Chapter 2 KA43 ROM MEMORY ........................................
    [Show full text]
  • VAX-Computer
    wdv-notes Stand: 24.JUL.1993 (4.) 188 VAX Computer: Modell-Übersicht. Wiss.Datenverarbeitung © 1980–1993 Karl-Heinz Dittberner FREIE UNIVERSITÄT BERLIN Hard Mit der folgenden Liste wird versucht, die ID-Bezeichnung, die relative (auf die Als Quellen wurden diverse DEC-Pu- alle von der Firma Digital Equipment VAX-11/780 bezogene) Leistungsfähig- blikationen verwendet sowie die Beschrei- Corporation (DEC) produzierten Modelle keit in VUPS, die in etwa dem MIPS bungen von SYS$GETSYI in der VMS- der Computer-Familien der VAX und der entspricht, die Typen der vorhandenen I/ Dokumentation und von $PRDEF, $VAX- Alpha AXP in einer konzentrierten Form O-Busse, der Modell-Name sowie der DEF und $ALPHADEF in der System zu erfassen. Tarnname (code name). Macro Library. Das Verzeichnis wurde im Die Übersicht ist nach Prozessor-Fa- Bei den Bus-Bezeichnungen bedeu- März 1993 der im UseNET von Paul Hardy milien und innerhalb dieser nach Subtypen ten: U = UniBus, M = MassBus, C = CI- (Email: [email protected]) veröffentlichten (X bzw. S) gegliedert. Angegeben sind für Bus, Q = Q-Bus, B = BI-Bus, D = DSSI, X Liste angepaßt. Alle zur Zeit noch aktuel- die einzelnen Computer-Modelle die SID- = XMI, T = TurboChannel, S = SCSI, F = len Modelle sind hinter dem Code-Namen Bezeichnung, die den CPU-Typ enthält, FutureBus+, E = EISA-Bus. mit einem * versehen. SID X ID VUPS Bus Model Name Code Name SID X ID VUPS Bus Model Name Code Name —— 1977: 700 series ———————————————————————————— —— 1991: NVAX+ chip series ———– Decimal SID = 385875968 ———————— 0100xxxx – 780 1.0
    [Show full text]
  • VAX VMS at 20
    1977–1997... and beyond Nothing Stops It! Of all the winning attributes of the OpenVMS operating system, perhaps its key success factor is its evolutionary spirit. Some would say OpenVMS was revolutionary. But I would prefer to call it evolutionary because its transition has been peaceful and constructive. Over a 20-year period, OpenVMS has experienced evolution in five arenas. First, it evolved from a system running on some 20 printed circuit boards to a single chip. Second, it evolved from being proprietary to open. Third, it evolved from running on CISC-based VAX to RISC-based Alpha systems. Fourth, VMS evolved from being primarily a technical oper- ating system, to a commercial operat- ing system, to a high availability mission-critical commercial operating system. And fifth, VMS evolved from time-sharing to a workstation environment, to a client/server computing style environment. The hardware has experienced a similar evolution. Just as the 16-bit PDP systems laid the groundwork for the VAX platform, VAX laid the groundwork for Alpha—the industry’s leading 64-bit systems. While the platforms have grown and changed, the success continues. Today, OpenVMS is the most flexible and adaptable operating system on the planet. What start- ed out as the concept of ‘Starlet’ in 1975 is moving into ‘Galaxy’ for the 21st century. And like the universe, there is no end in sight. —Jesse Lipcon Vice President of UNIX and OpenVMS Systems Business Unit TABLE OF CONTENTS CHAPTER I Changing the Face of Computing 4 CHAPTER II Setting the Stage 6 CHAPTER
    [Show full text]
  • Thesis May Never Have Been Completed
    UvA-DARE (Digital Academic Repository) Digital Equipment Corporation (DEC): A case study of indecision, innovation and company failure Goodwin, D.T. Publication date 2016 Document Version Final published version Link to publication Citation for published version (APA): Goodwin, D. T. (2016). Digital Equipment Corporation (DEC): A case study of indecision, innovation and company failure. General rights It is not permitted to download or to forward/distribute the text or part of it without the consent of the author(s) and/or copyright holder(s), other than for strictly personal, individual use, unless the work is under an open content license (like Creative Commons). Disclaimer/Complaints regulations If you believe that digital publication of certain material infringes any of your rights or (privacy) interests, please let the Library know, stating your reasons. In case of a legitimate complaint, the Library will make the material inaccessible and/or remove it from the website. Please Ask the Library: https://uba.uva.nl/en/contact, or a letter to: Library of the University of Amsterdam, Secretariat, Singel 425, 1012 WP Amsterdam, The Netherlands. You will be contacted as soon as possible. UvA-DARE is a service provided by the library of the University of Amsterdam (https://dare.uva.nl) Download date:26 Sep 2021 Digital Equipment Corporation (DEC) (DEC) Corporation Digital Equipment David Thomas David Goodwin Digital Equipment Corporation (DEC): A Case Study of Indecision, Innovation and Company Failure David Thomas Goodwin Digital Equipment Corporation (DEC): A Case Study of Indecision, Innovation and Company Failure David Thomas Goodwin 1 Digital Equipment Corporation (DEC): A Case Study of Indecision, Innovation and Company Failure ACADEMISCH PROEFSCHRIFT ter verkrijging van de graad van doctor aan de Universiteit van Amsterdam op gezag van de Rector Magnificus prof.
    [Show full text]
  • The Design of the VAX 4000 Model 100 and Microvax 3100 Model 90 Desktop Systems by Jonathan C. Crowell and David W. Maruska
    The Design of the VAX 4000 Model 100 and MicroVAX 3100 Model 90 Desktop Systems By Jonathan C. Crowell and David W. Maruska 1 Abstract The MicroVAX 3100 Model 90 and VAX 4000 Model 100 systems were designed to meet the growing demand for low-cost, high-performance desktop servers and timesharing systems. Both systems are based on the NVAX CPU chip and a set of VLSI support chips, which provide outstanding CPU and I/O performance. Housed in like desktop enclosures, the two systems provide 24 times the CPU performance of the original VAX-11/780 computer. With over 2.5 gigabytes of disk storage and 128 megabytes of main memory, the complete base system fits in less than one cubic foot of space. The system design was highly leveraged from existing designs to help meet an aggressive schedule. 2 Introduction The demand for low-cost, high-performance desktop servers and timesharing systems is increasing rapidly. The MicroVAX 3100 Model 90 and VAX 4000 Model 100 systems were designed to meet this demand. Both systems are based on the NVAX CPU chip and a set of very large-scale integration (VLSI) support chips, which provide outstanding CPU and I/O performance.[1] Each member of the MicroVAX 3100 family of systems constitutes a low- cost, general-purpose, multiuser VAX system in an enclosure that fits on the desktop. This enclosure supports all the required components of a typical system, including the main memory, synchronous and asynchronous communication lines, thick-wire and ThinWire Ethernet, and up to five small computer system interface (SCSI)-based storage devices.
    [Show full text]
  • VAX 6000 Model 600 System Technical User's Guide
    VAX 6000 Model 600 System Technical User’s Guide Order Number: EK–660EA–TM.001 This manual serves as a reference on how to write software to this machine and covers the information needed to do field-level repair or programming customized to the CPU. It includes information on interrupts, error handling, and detailed theory of operation. Digital Equipment Corporation First Printing, January 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software, if any, described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Copyright ©1992 by Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. The postpaid READER’S COMMENTS form on the last page of this document requests the user’s critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC PDP VAXcluster DEC LANcontroller ULTRIX VAXELN DECnet UNIBUS VMS DECUS VAX XMI DWMVA VAXBI dt This document was prepared using VAX DOCUMENT, Version 1.2 Contents PREFACE xv CHAPTER 1 THE VAX 6000 MODEL 600 SYSTEM 1–1 1.1 SYSTEM ARCHITECTURE 1–2 1.2 SAMPLE SYSTEM 1–4 1.3 SYSTEM FRONT
    [Show full text]
  • Database Integration
    I DATABASE INTEGRATION ALPHA SERVERS & WORKSTATIONS Digital ALPHA 21164 CPU Technical Journal Editorial The Digital TechnicalJournal is a refereed Cyrix is a trademark of Cyrix Corporation. Jane C. Blake, Managing Editor journal published quarterly by Digital dBASE is a trademark and Paradox is Helen L. Patterson, Editor Equipment Corporation, 30 Porter Road a registered trademark of Borland Kathleen M. Stetson, Editor LJ02/D10, Littleton, Massachusetts 01460. International, Inc. Subscriptionsto the Journal are $40.00 Circulation (non-U.S. $60) for four issues and $75.00 EDA/SQL is a trademark of Information Catherine M. Phillips, Administrator (non-U.S. $115) for eight issues and must Builders, Inc. Dorothea B. Cassady, Secretary be prepaid in U.S. funds. University and Encina is a registered trademark of Transarc college professors and Ph.D. students in Corporation. Production the electrical engineering and computer Excel and Microsoft are registered pde- Terri Autieri, Production Editor science fields receive complimentary sub- marks and Windows and Windows NT are Anne S. Katzeff, Typographer scriptions upon request. Orders, inquiries, trademarks of Microsoft Corporation. Joanne Murphy, Typographer and address changes should be sent to the Peter R Woodbury, Illustrator Digital TechnicalJournal at the published- Hewlett-Packard and HP-UX are registered by address. Inquiries can also be sent elec- trademarks of Hewlett-Packard Company. Advisory Board tronically to [email protected]. Single copies INGRES is a registered trademark of Ingres Samuel H. Fuller, Chairman and back issues are available for $16.00 each Corporation. Richard W. Beane by calling DECdirect at 1-800-DIGITAL Donald Z. Harbert (1-800-344-4825).
    [Show full text]
  • Circuit Implementation of a 300-Mhz 64-Bit Second-Generation CMOS Alpha CPU by William J
    Circuit Implementation of a 300-MHz 64-bit Second-generation CMOS Alpha CPU by William J. Bowhill, Shane L. Bell, Bradley J. Benschneider, Andrew J. Black, Sharon M. Britton, Ruben W. Castelino, Dale R. Donchin, John H. Edmondson, Harry R. Fair, III, Paul E. Gronowski, Anil K. Jain, Patricia L. Kroesen, Marc E. Lamere, Bruce J. Loughlin, Shekhar Mehta, Robert O. Mueller, Ronald P. Preston, Sribalan Santhanam, Timothy A. Shedd, Michael J. Smith, Stephen C. Thierauf ABSTRACT A 300-MHz, custom 64-bit VLSI, second-generation Alpha CPU chip has been developed. The chip was designed in a 0.5-um CMOS technology using four levels of metal. The die size is 16.5 mm by 18.1 mm, contains 9.3 million transistors, operates at 3.3 V, and supports 3.3-V/5.0-V interfaces. Power dissipation is 50 W. It contains an 8-KB instruction cache; an 8-KB data cache; and a 96-KB unified second-level cache. The chip can issue four instructions per cycle and delivers 1,200 mips/600 MFLOPS (peak). Several noteworthy circuit and implementation techniques were used to attain the target operating frequency. INTRODUCTION The Alpha 21164 chip is a 300-megahertz (MHz), quad-issue, custom very large-scale integration (VLSI) implementation of the Alpha architecture that delivers peak performance of 1,200 million instructions per second (mips)/600 million floating-point operations per second (MFLOPS). The chip is designed in a 0.5-micrometer (um) complementary metal-oxide semiconductor (CMOS) technology using four levels of metal. The die measures 16.5 millimeters (mm) by 18.1 mm and contains 9.3 million transistors.
    [Show full text]
  • DEC: the Mistakes That Led to Its Downfall
    DEC: The mistakes that led to its downfall David T. Goodwin, Roger G. Johnson Birkbeck College, University of London [email protected] , [email protected] In 1987 Digital Equipment Corporation (DEC) was the number two computer manufacturer in the world with its founder being named the “‘most successful entrepreneur in the history of American business” by Fortune magazine. This paper looks at the later history of Digital Equipment Corporation and asks how an organisation that was so successful in 1988 could sink to become a takeover target for a PC hardware company ten years later. The management styles and company culture have been extensively described in Edgar Schein’s book “DEC is dead, long live DEC” but there is much more to the story. The technology that the company developed and the business decisions made in the development and the direction of that technology had a major bearing on the fate of the company. Many mistakes were made over the last fifteen years of the company’s existence and this paper offers a suggestion as to what those mistakes were. In this paper, extensive use is made of interviews with people involved at the time as well as material from the Ken Olsen Archives at Gordon College which contain many of the memos that Ken Olsen sent in his long career at DEC. It considers DEC as a case study set in the context of literature on business change and the impact of downsizing. It looks at DEC’s initial attempt to break into the business market for personal computers in 1983, the personalities involved and the competing products that the company developed.
    [Show full text]
  • Digital Technical Journal, Volume 4, Number 3: NVAX-Microprocessor VAX Systems
    Editorial Jane C. Blake, Editor Kathleen M. Stetson, Associate Editor Helen L. Patterson, Associate Editor Circulation Catherine M. Phillips, Administrator Sherry L. Gonzalez Production Terri Autieri, Production Editor Anne S. Katzeff, ppographer Peter R. Woodbury, Illustrator Advisory Board Samuel H. Fuller, Chairman Richard W Beane Richard J. Hollingsworth Alan G. Nemeth Victor A. Vyssotsky Gayn B. Winters The Digital TechnicalJournal is published quarterly by Digital Equipment Corporation, 146 Main Street MLO 1-3/B68,Maynard, Massachusetts 01754-2571. Subscriptions to the Journal are $40.00 for four issues and must be prepaid in U.S. funds. University and college professors and Ph.D. students in the electrical engineering and computer science fields receive complimentary subscriptions upon request. Orders, inquiries, and address changes should be sent to the Digital TechnicalJournal at the published-by address. Inquiries can also be sent electronically to [email protected]. Single copies and back issues are available for $16.00 each from Digital Press of Digital Equipment Corporation, 1 Burlington Woods Drive, Burlington, MA 01830-4597 Digital employees may send subscription orders on the ENET to RDVAX::JOURNAL or by interoffice mail to mailstop ML01-3/B68. Orders should include badge number, site location code, and address. All employees must advise of changes of address. Comments on the content of any paper are welcomed and may be sent to the editor at the published-by or network address. Copyright O 1992 Digital Equipment Corporation. Copying without fee is permitted provided that such copies are made for use in educational institutions by faculty members and are not distributed for commercial advantage.
    [Show full text]
  • Vaxstation-Overview.Pdf
    VA$station - Wikipedia, the free encyclopedia Page 1 of 3 VAXstation From Wikipedia, the free encyclopedia The VAXstation was a family of workstation computers developed and manufactured by Digital Equipment Corporation DEC) using processors implementing the VA$ instruction set architecture ISA). Contents ( 1 VA$station I ( 2 VA$station II ( 2.1 VA$station II/,P$ ( . VA$station 2000 ( 0 VA$station 3100 Series ( 4.1 VA$station 3100 1odel 30 ( 4.2 VA$station 3100 1odel .2 ( 4.. VA$station 3100 1odel 40 ( 4.0 VA$station 3100 1odel 02 ( 4.3 VA$station 3100 1odel 45 ( 3 VA$station 3200 and VA$station 3500 ( 5 VA$station 3520 and VA$station .30/ ( 7 VA$station 4000 Series ( 7.1 VA$station 4000 1odel 30 ( 7.2 VA$station 4000 1odel 60 ( 7.. VA$station 4000 1odel 90 ( 7.0 VA$station 4000 1odel 90A ( 7.3 VA$station 4000 1odel 65 ( 2 VA$station 8000 ( 9 V$T 2000 ( 10 VA$station 100 ( 10.1 VA$station 500 ( 11 Software ( 12 References VAXstation I Introduced in 8ctober 1984, it was code named 9 Seahorse 9, and used the KD32 CP: module containing a 4 1Hz 250 ns) 1icroVA$ I processor. VAXstation II Code named 9Mayflower 9, it used the KA630 CP: module containing a 5 1Hz 200 ns) 1icroVA$ 78032 microprocessor. It was essentially a 1icroVA$ II in a workstation configuration. VAXstation II/GPX Introduced in December 1985, it was code named 9 Caylith 9, and was a variant of the VA$station II with hardware- enhanced, high-performance color graphics.
    [Show full text]
  • VAX 6000 Model 600 System Technical User's Guide
    VAX 6000 Model 600 System Technical User’s Guide Order Number: EK–660EA–TM.001 This manual serves as a reference on how to write software to this machine and covers the information needed to do field-level repair or programming customized to the CPU. It includes information on interrupts, error handling, and detailed theory of operation. Digital Equipment Corporation First Printing, January 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software, if any, described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Copyright ©1992 by Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. The postpaid READER’S COMMENTS form on the last page of this document requests the user’s critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC PDP VAXcluster DEC LANcontroller ULTRIX VAXELN DECnet UNIBUS VMS DECUS VAX XMI DWMVA VAXBI This document was prepared using VAX DOCUMENT, Version 1.2 Contents PREFACE xv CHAPTER 1 THE VAX 6000 MODEL 600 SYSTEM 1–1 1.1 SYSTEM ARCHITECTURE 1–2 1.2 SAMPLE SYSTEM 1–4 1.3 SYSTEM FRONT VIEW
    [Show full text]