DOCSLIB.ORG

VAX 6000 Model 600 System Technical User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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 VIEW 1–6 1.4 SYSTEM REAR VIEW 1–8 1.5 SUPPORTED ADAPTERS 1–10 CHAPTER 2 KA66A CPU MODULE 2–1 2.1 OVERVIEW AND BLOCK DIAGRAM 2–2 2.1.1 NVAX CPU Chip 2–3 2.1.1.1 Ibox • 2–4 2.1.1.2 Ebox and Microsequencer • 2–5 2.1.1.3 Fbox • 2–5 2.1.1.4 Mbox • 2–5 2.1.1.5 Cbox • 2–6 2.1.2 Backup Cache 2–6 2.1.3 NEXMI Chip, System Support, and XMI Interface 2–7 2.2 CPU SECTION 2–8 2.2.1 Data Types 2–8 2.2.2 Instruction Set 2–9 2.2.3 Physical Address Space 2–10 2.2.4 Memory Management 2–11 2.2.4.1 Translation Buffer • 2–12 2.2.4.2 Memory Management Control Registers • 2–13 iii Contents 2.2.5 Exceptions and Interrupts 2–14 2.2.5.1 Interrupts • 2–15 2.2.5.2 Exceptions • 2–17 2.2.5.3 Unique Exceptions • 2–18 2.2.5.4 Console Halt • 2–23 2.2.6 System Control Block 2–25 2.2.7 Process Structure 2–28 2.3 CACHE OVERVIEW 2–30 2.3.1 Writeback Cache and Ownership Concepts 2–30 2.3.2 Virtual Instruction Cache 2–31 2.3.3 Primary Cache 2–32 2.3.4 Backup Cache 2–32 2.3.4.1 Backup Cache Operating Modes • 2–33 2.3.4.2 Cbox Internal Processor Registers • 2–33 2.3.4.3 Tag Store and Data RAM Control • 2–36 2.3.4.4 Backup Cache Is OFF • 2–36 2.3.4.5 Backup Cache Is in Force Hit Mode • 2–37 2.3.4.6 Backup Cache Is in Error Transition Mode • 2–37 2.3.4.7 How to Turn the B-Cache Off • 2–38 2.3.4.8 How to Turn the B-Cache On • 2–39 2.3.5 Cache Initialization 2–40 2.4 NVAX BOX DESCRIPTIONS 2–42 2.4.1 Ibox 2–42 2.4.1.1 Effects of Ibox Pipelining • 2–42 2.4.1.2 Branch Prediction Unit • 2–43 2.4.2 Ebox 2–43 2.4.3 Fbox 2–44 2.4.4 Mbox 2–44 2.4.4.1 Translation Buffer Tag Fills • 2–45 2.4.4.2 Translation Buffer PTE Fills • 2–45 2.4.4.3 Recording Mbox Errors • 2–47 2.4.5 Cbox 2–47 2.5 KA66A TOY CLOCK AND INTERVAL TIMER 2–49 2.5.1 Time-of-Day Register (TODR) 2–49 2.5.2 Programmable Interval Clock 2–49 2.5.3 Time-of-Year Clock 2–50 2.6 XMI INTERFACE 2–54 2.6.1 XMI Address Space 2–54 2.6.1.1 XMI Memory Space • 2–54 2.6.1.2 XMI I/O Space • 2–54 iv Contents 2.6.2 XMI Transaction Generation/Response Tables 2–56 2.6.3 Invalidates 2–57 2.6.4 Writeback Queues 2–58 2.6.5 Lockout Avoidance 2–58 2.6.6 Interrupts and IDENTs 2–59 2.6.6.1 Responding to XMI Interrupts • 2–59 2.6.6.2 Generating the IDENT • 2–59 2.6.6.3 XMI Device Interrupt Priority • 2–60 2.6.6.4 Implied Vector Interrupts (IVINTR) • 2–60 2.6.6.4.1 IVINTR Mask Generation • 2–60 2.6.6.4.2 Interprocessor IVINTR (IP IVINTR) Response • 2–60 2.6.6.4.3 Write Error IVINTR (WE IVINTR) Response • 2–61 2.6.7 XMI Registers 2–61 2.7 KA66A CPU MODULE REGISTERS 2–63 2.7.1 IPR and Cache Addressing 2–63 2.7.2 Internal Processor Registers 2–67 CPU IDENTIFICATION REGISTER (CPUID) 2–71 INTERVAL CLOCK CONTROL AND STATUS REGISTER (ICCS) 2–72 NEXT INTERVAL COUNT REGISTER (NICR) 2–74 INTERVAL COUNT REGISTER (ICR) 2–75 CONSOLE RECEIVER CONTROL AND STATUS REGISTER (RXCS) 2–76 CONSOLE RECEIVER DATA BUFFER REGISTER (RXDB) 2–78 CONSOLE TRANSMITTER CONTROL AND STATUS REGISTER (TXCS) 2–80 CONSOLE TRANSMITTER DATA BUFFER REGISTER (TXDB) 2–82 MACHINE CHECK ERROR SUMMARY REGISTER (MCESR) 2–83 CONSOLE SAVED PROGRAM COUNTER REGISTER (SAVPC) 2–84 CONSOLE SAVED PROCESSOR STATUS LONGWORD (SAVPSL) 2–85 I/O RESET REGISTER (IORESET) 2–90 SYSTEM IDENTIFICATION REGISTER (SID) 2–91 PATCHABLE CONTROL STORE CONTROL REGISTER (PCSCR) 2–93 EBOX CONTROL REGISTER (ECR) 2–96 CBOX CONTROL REGISTER (CCTL) 2–99 BACKUP CACHE DATA ECC REGISTER (BCDECC) 2–103 BACKUP CACHE ERROR TAG STATUS REGISTER (BCETSTS) 2–105 BACKUP CACHE ERROR TAG INDEX REGISTER (BCETIDX) 2–108 BACKUP CACHE ERROR TAG REGISTER (BCETAG) 2–109 BACKUP CACHE ERROR DATA STATUS REGISTER (BCEDSTS) 2–111 BACKUP CACHE ERROR DATA INDEX REGISTER (BCEDIDX) 2–114 v Contents BACKUP CACHE ERROR DATA ECC REGISTER (BCEDECC) 2–115 CBOX ERROR FILL ADDRESS REGISTER (CEFADR) 2–117 CBOX ERROR FILL STATUS REGISTER (CEFSTS) 2–118 NDAL ERROR STATUS REGISTER (NESTS) 2–123 NDAL ERROR OUTPUT ADDRESS REGISTER (NEOADR) 2–126 NDAL ERROR OUTPUT COMMAND REGISTER (NEOCMD) 2–127 NDAL ERROR DATA HIGH REGISTER (NEDATHI) 2–130 NDAL ERROR DATA LOW REGISTER (NEDATLO) 2–132 NDAL ERROR INPUT COMMAND REGISTER (NEICMD) 2–133 VIC MEMORY ADDRESS REGISTER (VMAR) 2–135 VIC TAG REGISTER (VTAG) 2–137 VIC DATA REGISTER (VDATA) 2–139 IBOX CONTROL AND STATUS REGISTER (ICSR) 2–140 PHYSICAL ADDRESS MODE REGISTER (PAMODE) 2–142 MEMORY MANAGEMENT EXCEPTION ADDRESS REGISTER (MMEADR) 2–143 MEMORY MANAGEMENT EXCEPTION PTE ADDRESS REGISTER (MMEPTE) 2–144 MEMORY MANAGEMENT EXCEPTION STATUS REGISTER (MMESTS) 2–145 TB PARITY ADDRESS REGISTER (TBADR) 2–148 TB PARITY STATUS REGISTER (TBSTS) 2–149 P-CACHE PARITY ADDRESS REGISTER (PCADR) 2–153 P-CACHE STATUS REGISTER (PCSTS) 2–154 P-CACHE CONTROL REGISTER (PCCTL) 2–157 2.7.3 XMI Registers 2–160 NDAL CONTROL AND STATUS REGISTER (NCSR) 2–162 NEXMI INPUT PORT REGISTER (IPORT) 2–168 NEXMI OUTPUT PORT0 REGISTER (OPORT0) 2–170 NEXMI OUTPUT PORT1 REGISTER (OPORT1) 2–172 DEVICE REGISTER (XDEV) 2–173 BUS ERROR REGISTER (XBER) 2–174 FAILING ADDRESS REGISTER (XFADR) 2–181 XMI GENERAL PURPOSE REGISTER (XGPR) 2–185 NODE-SPECIFIC CONTROL AND STATUS REGISTER (NSCSR) 2–186 XMI CONTROL REGISTER (XCR) 2–188 FAILING ADDRESS EXTENSION REGISTER (XFAER) 2–194 BUS ERROR EXTENSION REGISTER (XBEER) 2–197 WRITEBACK 0 FAILING ADDRESS REGISTER (WFADR0) 2–201 WRITEBACK 1 FAILING ADDRESS REGISTER (WFADR1) 2–202 2.8 KA66A CPU MODULE INITIALIZATION, SELF-TEST, AND BOOTING 2–203 2.8.1 Initialization Overview 2–203 vi Contents 2.8.2 Detailed Initialization Description 2–205 2.8.2.1 NVAX CPU Hardware/Microcode Initialization • 2–208 2.8.2.2 Console Initialization • 2–208 2.8.2.3 Unnecessary Explicit Initialization • 2–210 2.8.2.4 Warm Start Initialization • 2–210 2.8.2.5 Node Reset • 2–210 2.8.2.6 Boot Processor Determination • 2–211 2.8.2.7 Memory Configuration • 2–211 2.8.2.7.1 Selection of Interleave • 2–211 2.8.2.7.2 Memory Testing and the Bitmap • 2–212 2.8.2.8 DWMBB Configuration • 2–213 2.8.2.9 DWMVA Configuration • 2–213 2.8.3 Bootstrapping or Restarting the Operating System 2–214 2.8.3.1 Operating System Restart • 2–214 2.8.3.2 Failing Restart • 2–215 2.8.3.3 Restart Parameters • 2–216 2.8.3.4 Operating System Bootstrap • 2–216 2.8.3.5 Boot Algorithm • 2–217 2.8.3.6 Boot Parameters • 2–218 2.8.3.7 Bootstrap Software Sequence • 2–219 2.9 INTERPROCESSOR COMMUNICATION THROUGH THE CONSOLE PROGRAM 2–220 2.9.1 Required Communications Paths 2–220 2.9.2 Console Communications Area 2–221 2.9.3 Sending a Message to Another Processor 2–229 2.10 ERROR HANDLING 2–231 2.10.1 Error State Collection 2–233 2.10.2 Error Analysis 2–236 2.10.3 Error Recovery 2–237 2.10.3.1 Special Considerations when Memory Management Is Off • 2–238 2.10.3.2 Cache Coherence in Error Handling • 2–239 2.10.3.2.1 Disabling and Flushing the Caches (Leaving the B-Cache in ETM) • 2–240 2.10.3.2.2 Enabling the Caches • 2–241 2.10.3.3 Special Writeback Cache Recovery • 2–241 2.10.3.3.1 B-Cache Uncorrectable Error During Writeback • 2–241 2.10.3.3.2 Memory State • 2–241 2.10.3.3.2.1 Accessing Memory State • 2–242 2.10.3.3.2.2 Repairing Memory State (Fill Errors) • 2–242 2.10.3.3.2.3 Repairing Memory State (Tagged-Bad Locations) • 2–243 2.10.3.3.3 Extracting Data from the B-Cache • 2–243 2.10.3.3.4 Address Determination Procedure for Recovery from Uncorrectable B-Cache Data RAM Errors • 2–243 2.10.3.3.5 Special Address Determination Procedure for Recovery from Uncorrectable B-Cache Tag Store Errors • 2–244 2.10.3.4 Cache and TB Test Procedures • 2–245 vii Contents 2.10.3.5 NEXMI Error Handling • 2–245 2.10.4 Error Retry 2–246 2.10.4.1 General Multiple Error Handling Philosophy • 2–246 2.10.4.2 Retry Special Cases • 2–247 2.10.5 Console Halt and Halt Interrupt 2–247 2.10.6 Machine Check Exception 2–249 2.10.6.1 MCHK_UNKNOWN_MSTATUS • 2–259 2.10.6.2 MCHK_INT.ID_VALUE • 2–259 2.10.6.3 MCHK_CANT_GET_HERE • 2–259 2.10.6.4 MCHK_MOVC.STATUS • 2–259 2.10.6.5 MCHK_ASYNC_ERROR • 2–259 2.10.6.5.1 TB Parity Errors • 2–260 2.10.6.5.2 Ebox Stage 3 STALL Timeout Error • 2–260 2.10.6.6 MCHK_SYNC_ERROR • 2–260 2.10.6.6.1 VIC Parity Errors • 2–261 2.10.6.6.2 B-Cache Data RAM Uncorrectable
Load more

Recommended publications
  • 18-447 Computer Architecture Lecture 6: Multi-Cycle and Microprogrammed Microarchitectures
    18-447 Computer Architecture Lecture 6: Multi-Cycle and Microprogrammed Microarchitectures Prof. Onur Mutlu Carnegie Mellon University Spring 2015, 1/28/2015 Agenda for Today & Next Few Lectures n Single-cycle Microarchitectures n Multi-cycle and Microprogrammed Microarchitectures n Pipelining n Issues in Pipelining: Control & Data Dependence Handling, State Maintenance and Recovery, … n Out-of-Order Execution n Issues in OoO Execution: Load-Store Handling, … 2 Reminder on Assignments n Lab 2 due next Friday (Feb 6) q Start early! n HW 1 due today n HW 2 out n Remember that all is for your benefit q Homeworks, especially so q All assignments can take time, but the goal is for you to learn very well 3 Lab 1 Grades 25 20 15 10 5 Number of Students 0 30 40 50 60 70 80 90 100 n Mean: 88.0 n Median: 96.0 n Standard Deviation: 16.9 4 Extra Credit for Lab Assignment 2 n Complete your normal (single-cycle) implementation first, and get it checked off in lab. n Then, implement the MIPS core using a microcoded approach similar to what we will discuss in class. n We are not specifying any particular details of the microcode format or the microarchitecture; you can be creative. n For the extra credit, the microcoded implementation should execute the same programs that your ordinary implementation does, and you should demo it by the normal lab deadline. n You will get maximum 4% of course grade n Document what you have done and demonstrate well 5 Readings for Today n P&P, Revised Appendix C q Microarchitecture of the LC-3b q Appendix A (LC-3b ISA) will be useful in following this n P&H, Appendix D q Mapping Control to Hardware n Optional q Maurice Wilkes, “The Best Way to Design an Automatic Calculating Machine,” Manchester Univ.
    [Show full text]
  • System Design for a Computational-RAM Logic-In-Memory Parailel-Processing Machine
    System Design for a Computational-RAM Logic-In-Memory ParaIlel-Processing Machine Peter M. Nyasulu, B .Sc., M.Eng. A thesis submitted to the Faculty of Graduate Studies and Research in partial fulfillment of the requirements for the degree of Doctor of Philosophy Ottaw a-Carleton Ins titute for Eleceical and Computer Engineering, Department of Electronics, Faculty of Engineering, Carleton University, Ottawa, Ontario, Canada May, 1999 O Peter M. Nyasulu, 1999 National Library Biôiiothkque nationale du Canada Acquisitions and Acquisitions et Bibliographie Services services bibliographiques 39S Weiiington Street 395. nie WeUingtm OnawaON KlAW Ottawa ON K1A ON4 Canada Canada The author has granted a non- L'auteur a accordé une licence non exclusive licence allowing the exclusive permettant à la National Library of Canada to Bibliothèque nationale du Canada de reproduce, ban, distribute or seU reproduire, prêter, distribuer ou copies of this thesis in microform, vendre des copies de cette thèse sous paper or electronic formats. la forme de microficbe/nlm, de reproduction sur papier ou sur format électronique. The author retains ownership of the L'auteur conserve la propriété du copyright in this thesis. Neither the droit d'auteur qui protège cette thèse. thesis nor substantial extracts fkom it Ni la thèse ni des extraits substantiels may be printed or otherwise de celle-ci ne doivent être imprimés reproduced without the author's ou autrement reproduits sans son permission. autorisation. Abstract Integrating several 1-bit processing elements at the sense amplifiers of a standard RAM improves the performance of massively-paralle1 applications because of the inherent parallelism and high data bandwidth inside the memory chip.
    [Show full text]
  • 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.
    [Show full text]
  • P4080 Development System User's Guide
    Freescale Semiconductor Document Number: P4080DSUG User Guide Rev. 0, 07/2010 P4080 Development System User’s Guide by Networking and Multimedia Group Freescale Semiconductor, Inc. Austin, TX Contents 1Overview 1. Overview . 1 2. Features Summary . 2 The P4080 development system (DS) is a high-performance 3. Block Diagram and Placement . 4 computing, evaluation, and development platform 4. Evaluation Support . 6 supporting the P4080 Power Architecture® processor. The 5. Architecture . 8 P4080 development system’s official designation is 6. Configuration . 40 7. Programming Model . 45 P4080DS, and may be ordered using this part number. 8. Revision History . 58 The P4080DS is designed to the ATX form-factor standard, A. References . 58 allowing it to be used in 2U rack-mount chassis, as well as in a standard ATX chassis. The system is lead-free and RoHS-compliant. © 2011 Freescale Semiconductor, Inc. All rights reserved. Features Summary 2 Features Summary The features of the P4080DS development board are as follows: • Support for the P4080 processor — Core processors – Eight e500mc cores – 45 nm SOI process technology — High-speed serial port (SerDes) – Eighteen lanes, dividable into many combinations – Five controllers support five add-in card slots. – Supports PCI Express, SGMII, Nexus/Aurora debug, XAUI, and Serial RapidIO®. — Dual DDR memory controllers – Designed for DDR3 support – One-per-channel 240-pin sockets that support standard JEDEC DIMMs — Triple-speed Ethernet/ USB controller – One 10/100/1G port uses on-board VSC8244 PHY
    [Show full text]
  • VAX 4000 V96-2.3—10 Feb 1997
    TM VAX 4000 V96-2.3—10 Feb 1997 DIGITAL Systems and Options Catalog Product Description VAX 4000 systems provide commercial systems performance, high availability, and a compact footprint. They support a wide range of applications and options, including FDDI networks and Q-bus peripherals. System enclosure supports internal storage and Q-bus expansion through a B400X expansion cabinet. VAX 4000 systems come in three packages: Desktop Model 106A, Desktop/Deskside Model 108, and Pedestal/Deskside Model 505A/705A DSSI and Ethernet adapter chips—each driven by a 10-MIP on-chip RISC processor—are tightly integrated on the CPU module with direct access to memory. Digital's DSSI to SCSI HSD10 storage solutions replace DSSI RF36 disk technology in all VAX 4000 systems. Digital’s HSD10 DSSI-to-SCSI controller. mounted internally in system cabinet, supports standard RZxx SCSI storage on VAX 4000 systems while still supporting DSSI clustering. External StorageWorks HSD10 controllers are supported. VAX 4000 Model 106A offers performance of 10-ns NVAX chip. Systems achieve 215 transactions per second (TPS). With internal support for the HSD10, DSSI-to-SCSI controller, VAX 4000 customers can take advantage of low-cost, more flexible and open StorageWorks solutions. VAX 4000 Model 108 offers identical performance, is compatible with Model 106A, but is housed in a new Desktop/Deskside minitower enclosure. In addition, these systems offer enchancements in the memory and storage capacity, supporting up to 512 MB of standard SIMM memory and six storage devices in the system enclosure. VAX 4000 Model 505A and 705A offer 12 ns and 9 ns performance, respectively in a Q-bus Pedestal package.
    [Show full text]
  • Digital Technical Journal, Number 7, August 1988: CVAX
    Digital Technical Tournal Digital Equipment Corporation Managing Editor Richard W Beam Edltor Jane C. Dlak Pcoductloa St& Production Editor - Helen 1 Partenon Designer - Charlotte Bell Typographers -Jonathan M. Bohy Macgaret Burdine lllusultor - Deborah Kc~lcy Advisoiy Board Samuel H. Fuller, Chairman Robert M. Glorioso John W. McCredle Mahendra R. Patel F. Grant Saviers William D. Srrcckr Victor A. Vyssutsky The Digital Technical Journal is published by Digital Equipment Corporatloa, 77 Reed Road, Hudson, Magsachu~etts0 1749. Changes of address should be sent to Digital Equipment Corporation. attention: List Maintenance. I0 Forbes Road, Northboro, MA 01532 Please indude the address label wlth changes marked. Comments on the content of any paper arc welcomed. Write to the editor at Mall Stop HL02.3/K11 at the published~bpaddress. Comments can ahbe sent on the BNET to RDVAX: :BIAKEor on the ARPANET to B~%RDVAX.DE~DE~. Copyright @ 1988 Digital Equipment Corporation. Copying without fee is permitted provided that such copies are made for use in educational lnstltutions by faculty members and are nor distributed for commercial advantage. Abstncting with credit of Digital Equipment Corporation's authorship is permltted. Requests for other copies for a Pee may br made to Digiul Press of Digital Equipment Corporation. A11 rights reserved. The information in this journal is subject to change without notice and should not bc construed as a com- mltment by Digital Equipment Corporation. Digital Equipment Corpmtion assumes no responslbllity for any errors that may appcss in this document ISSN 0898.901X Documentatlcm Number EY-6742H-DP The following are wademarks of Digital Gquipmcnt Corporation: ALL.IN-I.
    [Show full text]
  • Micro-Sequencer Based Control Unit Design for a Central Processing Unit
    MICRO-SEQUENCER BASED CONTROL UNIT DESIGN FOR A CENTRAL PROCESSING UNIT TAN CHANG HAI A project report submitted in partial fulfillment of the requirement for the award of the degree of Master of Engineering (Computer & Microelectronic Systems) Faculty of Electrical Engineering Universiti Teknologi Malaysia APRIL 2007 iii DEDICATION To my beloved wife, parents and family members iv ACKNOLEDGEMENT In preparing this thesis, I was in contact with many people, researchers and academicians. They have contributed towards my understanding and thoughts. In particular, I wish to express my sincere appreciation to my thesis supervisor, Professor Dr. Mohamed Khalil Hani, for encouragement, guidance and friendships. I am also very thankful to my friends and family members for their great support, advices and motivation. Without their continued support and interest, this thesis would not have been as presented here. v ABSTRACT Central Processing Unit (CPU) is a processing unit that controls the computer operations. The current in house CPU design was not complete therefore the purpose of this research was to enhance the current CPU design in such a way that it can handle hardware interrupt operation, stack operations and subroutine call. Register transfer logic (RTL) level design methodology namely top level RTL architecture, RTL control algorithm, data path unit design, RTL control sequence table, micro- sequencer control unit design, integration of control unit and data path unit, and the functional simulation for the design verification are included in this research. vi ABSTRAK Unit pusat pemprosesan (CPU) merupakan sebuah mesin yang berfungsi untuk menjana fungsi komputer. Buat masa kini, rekaan CPU masih belum sempurna.
    [Show full text]
  • Alpha and VAX Comparison Based on Industry-Standard Benchmark
    Alpha and VAX Comparison based on Industry-standard Benchmark Results Digital Equipment Corporation December 1994 EC-N3909-10 Version 3.0 December 1994 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. Digital conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1 )(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227 7013. Copyright© 1994 Digital Equipment Corporation All rights reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: AlphaServer, AlphaStation, AlphaGeneration, DEC, OpenVMS, VMS, ULTRIX, and the DIGITAL logo. The following are third-party trademarks: MIPS is a trademark of MIPS Computer Systems, Inc. TPC-A is a trademark of the Transaction Processing Performance Council. INFORMIX is a registered trademark of lnformix Software, Inc. OSF/1 is a registered trademark of the Open Software Foundation, Inc. ORACLE is a registered trademark of Oracle Corporation. SPEC, SPECfp92, and SPECratio are trademarks of Standard Performance Evaluation Corporation. MIPS is a trademark of MIPS Computer Systems, Inc. All other trademarks and registered
    [Show full text]
  • EEL 4914 Senior Design Gator Μprocessor Spring 2007 Submitted By
    EEL 4914 Senior Design Gator µProcessor Spring 2007 Submitted by: Kevin Phillipson Project Abstract The Gator microprocessor or GµP is a central processing unit to be used for education and research at the University of Florida. This processor will be realized on a development board that will be constructed in the course of this project. The board will contain a programmable gate array, in this case a FPGA. Using this FPGA we can dynamically build and test the CPU by describing and synthesizing it using a hardware description language. The processor will be instruction set & machine code compatible with the Motorola/Freescale 68xx microprocessors. This will allow us to use the extensive library of compliers, assemblers and other tools already available. Introduction The ultimate goal is to create a tool which could be used to bridge between Microprocessor Applications (EEL4744C) and Digital Design (EEL4712C) while enhancing both classes. Currently, the courses implement two separate boards. EEL4744C uses a board based on the Freescale 68HC12 micro-controller (Figure 1). It is supported by an EEPROM containing a monitor program, a 4MHz crystal oscillator, a serial port connection, an Altera CPLD, bus drivers and various supporting resistors and capacitors. Most devices are through-hole mounted. EEL4712C uses the BT-U board produced by Binary Technologies which is based on an Altera Cyclone FPGA (Figure 2). The board also features VGA & PS2 interfaces, switch banks and LED displays. The board comes pre-assembled. Figure 1: Current 4744 board Figure 2: Current 4712 board The GµP would be a bridge between these two designs, implementing a 68xx compatible CPU core in an Altera Cyclone II FPGA.
    [Show full text]
  • VAX 6000 Series Installation Guide
    VAX 6000 Series Installation Guide Order Number EK–600EB–IN.002 This guide is intended for use by Digital customer service engineers and self-maintenance customers installing a VAX 6000 series system. digital equipment corporation maynard, massachusetts First Printing, October 1990 Revised, November 1991 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 ©1990, 1991 by Digital Equipment Corporation. All Rights Reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DEC PDP VAXcluster DEC LANcontroller ULTRIX VAXELN DECnet UNIBUS VMS DECUS VAX XMI DWMVA VAXBI FCC NOTICE: The equipment described in this manual generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference when operated in a commercial environment. Operation of this equipment in a residential area may cause interference, in which case the user at his own expense may be required to take measures to correct the interference.
    [Show full text]
  • VAX 6000 Platform Technical User's Guide
    VAX 6000 Platform Technical User’s Guide Order Number: EK–600EA–TM-001 This manual serves as a reference for field-level repair or programming for systems based on the VAX 6000 platform. The manual describes the platform architecture, the XMI system bus, the DWMBB XMI-to-VAXBI adapter, and the power and cooling systems found in the H9657-CA/CB/CU cabinet. Digital Equipment Corporation First Printing, May 1991 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 ©1991 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: DEMNA PDP VAXcluster DEC ULTRIX VAXELN DEC LANcontroller UNIBUS VMS DECnet VAX XMI DECUS VAXBI dt This document was prepared using VAX DOCUMENT, Version 1.2 Contents PREFACE xiii CHAPTER 1 THE VAX 6000 PLATFORM OVERVIEW 1–1 1.1 SPECIFICATIONS 1–2 1.2 SYSTEM FRONT VIEW 1–4
    [Show full text]
  • Digital Technical Journal, Number 7, August 1988: CVAX-Based Systems
    CVAX-based Systems Digital Technical Journal Digital Equipment Corporation umhcr 7 August I9R8 Managing Editor Richard W Beane Editor jane C. Blake Production Staff Produnion Editor- Helen L. Paucrson Designer- Charlo!!<: Bell Typographers- Jonathan !\·f. Uohy Margart:t Burdine lllustrawr- Dt:borah Keeley Advisory Board Samuel H. Fuller, Chairman Robert M. Glorioso John W McCredie Mahendra R. Patel F. Grant Saviers William D. Strecker Victor A. Vyssotsky The Digital Tecbnical jnumal is published by Digital Equipmt:nt Corporation. 77 Reed Road. Hudson. Massachuscus 01749. Changes of address should be sent to Digital E quipment Corporation. aut:ntion: List Maintenance. I 0 Forbes Road. Northboro. MA 015j2. Please includt: the address label with changes marked. Comments on the content of any paper are wclcomt:d. Write to the editor at Mail Stop 1-lLOl-.�/Kil at the published-by address. Comments can also be sent on the ENET to RDV�'X::OIAKE or on the ARPANET to BLA.K.E'X,RDVAX. DEC�)l)ECWRL. Copyright © 1988 Digital Equ ipment Corporation. Copying without fee is permiued providt:d that such copies are made for use in t:duc:uional institmions by faculty members and arc not distributed for commercial advamage. Abstracting with credit of Digital Equipment Corporation's authorship is pcrmiued. Requests for other copies for a fee may be made 10 Digital Press of Digital Equipmem Corporation. All rights reserved. The information in this journal is subject to change without notice and should not be construed as a com­ miunem by Digital E quipment Corporation. Digital Equipment Corporation assumt:s no responsibility for any errors that may appear in this document.
    [Show full text]