MVME3100 Single Board Computer Programmer's Reference

Total Page:16

File Type:pdf, Size:1020Kb

MVME3100 Single Board Computer Programmer's Reference MVME3100 Single Board Computer Programmer’s Reference P/N: 6806800G37C September 2019 © 2019 SMART Embedded Computing™, Inc. All Rights Reserved. Trademarks The stylized "S" and "SMART" is a registered trademark of SMART Modular Technologies, Inc. and “SMART Embedded Computing” and the SMART Embedded Computing logo are trademarks of SMART Modular Technologies, Inc. All other names and logos referred to are trade names, trademarks, or registered trademarks of their respective owners. These materials are provided by SMART Embedded Computing as a service to its customers and may be used for informational purposes only. Disclaimer* SMART Embedded Computing (SMART EC) assumes no responsibility for errors or omissions in these materials. These materials are provided "AS IS" without warranty of any kind, either expressed or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SMART EC further does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SMART EC shall not be liable for any special, indirect, incidental, or consequential damages, including without limitation, lost revenues or lost profits, which may result from the use of these materials. SMART EC may make changes to these materials, or to the products described therein, at any time without notice. SMART EC makes no commitment to update the information contained within these materials. Electronic versions of this material may be read online, downloaded for personal use, or referenced in another document as a URL to a SMART EC website. The text itself may not be published commercially in print or electronic form, edited, translated, or otherwise altered without the permission of SMART EC. It is possible that this publication may contain reference to or information about SMART EC products, programming, or services that are not available in your country. Such references or information must not be construed to mean that SMART EC intends to announce such SMART EC products, programming, or services in your country. Limited and Restricted Rights Legend If the documentation contained herein is supplied, directly or indirectly, to the U.S. Government, the following notice shall apply unless otherwise agreed to in writing by SMART Embedded Computing. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (b)(3) of the Rights in Technical Data clause at DFARS 252.227-7013 (Nov. 1995) and of the Rights in Noncommercial Computer Software and Documentation clause at DFARS 252.227-7014 (Jun. 1995). SMART Embedded Computing, Inc. 2900 S. Diablo Way, Suite 190 Tempe, Arizona 85282 USA *For full legal terms and conditions, visit www.smartembedded.com/ec/legal Table of Contents About this Manual ................................................................7 1 Board Description and Memory Maps ...........................................13 1.1 Introduction .............................................................13 1.2 Ordering and Support Information ...........................................13 1.3 MemoryMaps...........................................................17 1.3.1 Default Processor Memory Map........................................17 1.3.2 MOTLoad’s Processor Memory Map ....................................18 1.3.3 VME Memory Map ..................................................19 1.3.4 System I/O Memory Map .............................................19 1.3.5 System Status Register ..............................................21 1.3.6 System Control Register .............................................22 1.3.7 System Indicator Register ............................................23 1.3.8 Flash Control/Status Register .........................................24 1.3.9 PCI Bus Status Registers.............................................25 1.3.10 Interrupt Detect Register .............................................28 1.3.11 Presence Detect Register ............................................28 1.3.12 PLD Revision Register ...............................................29 1.3.13 PLD Data Code Register .............................................30 1.3.14 Test Register 1.....................................................30 1.3.15 Test Register 2.....................................................31 1.3.16 External Timer Registers .............................................31 1.3.16.1 Prescalar Register ..........................................31 1.3.16.2 Control Registers ...........................................32 1.3.16.3 Compare Registers .........................................33 1.3.16.4 Counter Registers ..........................................33 1.3.17 Geographical Address Register ........................................34 2 Programming Details .........................................................35 2.1 Introduction .............................................................35 2.2 MPC8540 Reset Configuration ..............................................36 2.3 MPC8540 Interrupt Controller ...............................................40 2.4 Local Bus Controller Chip Select Assignments .................................41 2.5 Two-Wire Serial Interface ..................................................41 2.6 User Configuration EEPROM ...............................................42 2.7 VPD EEPROM ..........................................................42 MVME3100 Single Board Computer Programmer’s Reference (6806800G37C) 3 Table of Contents 2.8 RTM VPD EEPROM ......................................................43 2.9 Ethernet PHY Address ....................................................43 2.10 Flash Memory ...........................................................43 2.11 PCI IDSEL Definition .....................................................44 2.12 PCI Arbitration Assignments ................................................46 2.13 Clock Distribution ........................................................47 2.14 MPC8540 Real-Time Clock Input ............................................48 2.15 MPC8540 LBC Clock Divisor ...............................................48 A Related Documentation .......................................................49 A.1 SMART Embedded Computing Documentation .................................49 A.2 Manufacturers’ Documents .................................................49 A.3 Related Specifications ....................................................51 4 MVME3100 Single Board Computer Programmer’s Reference (6806800G37C) List of Tables Table 1-1 MVME3100 Features Summary .........................................15 Table 1-2 MVME712-101 RTM Features Summary ..................................17 Table 1-3 Default Processor Address Map .........................................18 Table 1-4 MOTLoad’s Processor Address Map .....................................18 Table 1-5 System I/O Memory Map ..............................................19 Table 1-6 System Status Register ...............................................21 Table 1-7 System Control Register ...............................................22 Table 1-8 System Indicator Register ..............................................23 Table 1-9 Flash Control/Status Register ...........................................24 Table 1-10 PCI Bus A Status Register .............................................25 Table 1-11 PCI Bus B Status Register .............................................26 Table 1-12 PCI Bus C Status Register .............................................27 Table 1-13 Interrupt Detect Register ...............................................28 Table 1-14 Presence Detect Register ..............................................28 Table 1-15 PLD Revision Register ................................................29 Table 1-16 PLD Data Code Register ..............................................30 Table 1-17 Test Register 1 ......................................................30 Table 1-18 Test Register 2 ......................................................31 Table 1-19 Prescalar Register ...................................................31 Table 1-20 Tick Timer Control Registers ............................................32 Table 1-21 Tick Timer Compare Registers ..........................................33 Table 1-22 Tick Timer Counter Registers ...........................................33 Table 2-1 MPC8540 Power-on Reset Configuration Settings ...........................36 Table 2-2 MPC8540 Interrupt Controller ...........................................40 Table 2-3 LBC Chip Select Assignments ..........................................41 Table 2-4 I2C Bus Device Addressing ............................................41 Table 2-5 PHY Types and MII Management Bus Addresses ...........................43 Table 2-6 Flash Options .......................................................43 Table 2-7 IDSEL and Interrupt Mapping for PCI Devices ..............................44 Table 2-8 Planar PCI Device Identification .........................................46 Table 2-9 PCI Arbitration Assignments ............................................46 Table 2-10 Clock Assignments ...................................................47 Table A-1 SMART EC Documents ...............................................49 Table A-2 Manufacturers’ Documents .............................................49 Table A-3 Related Specifications ................................................51
Recommended publications
  • Recovering from Operating System Crashes
    Recovering from Operating System Crashes Francis David Daniel Chen Department of Computer Science Department of Electrical and Computer Engineering University of Illinois at Urbana-Champaign University of Illinois at Urbana-Champaign Urbana, USA Urbana, USA Email: [email protected] Email: [email protected] Abstract— When an operating system crashes and hangs, it timers and processor support techniques [12] are required to leaves the machine in an unusable state. All currently running detect such crashes. program state and data is lost. The usual solution is to reboot the It is accepted behavior that when an operating system machine and restart user programs. However, it is possible that after a crash, user program state and most operating system state crashes, all currently running user programs and data in is still in memory and hopefully, not corrupted. In this project, volatile memory is lost and unrecoverable because the proces- we use a watchdog timer to reset the processor on an operating sor halts and the system needs to be rebooted. This is inspite system crash. We have modified the Linux kernel and added of the fact that all of this information is available in volatile a recovery routine that is called instead of the normal boot up memory as long as there is no power failure. This paper function when the processor is reset by a watchdog. This resumes execution of user processes after killing the process that was explores the possibility of recovering the operating system executing when the watchdog fired. We have implemented this using the contents of memory in order to resume execution on the ARM architecture and we use a periodic watchdog kick of user programs without any data loss.
    [Show full text]
  • Acronis True Image 2021
    Acronis True Image 2021 USER GUIDE Table of contents 1 Introduction ....................................................................................................................7 1.1 What is Acronis® True Image™? ................................................................................................ 7 1.2 New in this version .................................................................................................................... 7 1.3 Backups created in Acronis True Image 2020 or later ............................................................... 8 1.4 System requirements and supported media ............................................................................. 9 1.4.1 Minimum system requirements .................................................................................................................... 9 1.4.2 Supported operating systems ...................................................................................................................... 10 1.4.3 Supported file systems .................................................................................................................................. 10 1.4.4 Supported Internet connection types ......................................................................................................... 11 1.4.5 Supported storage media ............................................................................................................................. 11 1.5 Installing Acronis True Image 2021 ..........................................................................................12
    [Show full text]
  • A Method for the Recovery of Data After a Computer System Failure: The
    Iowa State University Capstones, Theses and Retrospective Theses and Dissertations Dissertations 1992 A method for the recovery of data after a computer system failure: the development of Constant Random Access Memory (CRAM) Recovery System Renford Adolphus Benito Brevett Iowa State University Follow this and additional works at: https://lib.dr.iastate.edu/rtd Part of the Computer Sciences Commons, and the Engineering Education Commons Recommended Citation Brevett, Renford Adolphus Benito, "A method for the recovery of data after a computer system failure: the development of Constant Random Access Memory (CRAM) Recovery System " (1992). Retrospective Theses and Dissertations. 9977. https://lib.dr.iastate.edu/rtd/9977 This Dissertation is brought to you for free and open access by the Iowa State University Capstones, Theses and Dissertations at Iowa State University Digital Repository. It has been accepted for inclusion in Retrospective Theses and Dissertations by an authorized administrator of Iowa State University Digital Repository. For more information, please contact [email protected]. INFORMATION TO USERS This manuscript has been reproduced from the microfilm master. UMI films the text directly from the original or copy submitted. Thus, some thesis and dissertation copies are in typewriter face, while others may be from any type of computer printer. The quality of this reproduction is dependent upon the quality of the copy submitted. Broken or indistinct print, colored or poor quality illustrations and photographs, print bleedthrough, substandard margins, and improper alignment can adversely affect reproduction. In the unlikely event that the author did not send UMI a complete manuscript and there are missing pages, these will be noted.
    [Show full text]
  • (BSD) Release Notes
    Intel® QuickAssist Technology Software for Free Berkeley Software Distribution* (FreeBSD*) Release Notes - Software version Package Version: QAT1.7.B.3.7.0-00008 June 2020 Document Number: 621446-004 You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein. Intel technologies' features and benefits depend on system configuration and may require enabled hardware, software, or service activation. Learn more at intel.com, or from the OEM or retailer. No computer system can be absolutely secure. Check with your system manufacturer or retailer or learn more at intel.com. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. Tests document performance of components on a particular test, in specific systems. Differences in hardware, software, or configuration will affect actual performance. Consult other sources of information to evaluate performance as you consider your purchase. For more complete information about performance and benchmark results, visit www.intel.com/performance. Intel does not control or audit third-party benchmark data or the web sites referenced in this document. You should visit the referenced web site and confirm whether referenced data are accurate. Copies of documents which have an order number and are referenced in this document may be obtained by calling 1-800-548-4725 or by visiting www.intel.com/design/literature.htm. Intel, the Intel logo, and Xeon are trademarks of Intel Corporation in the United States and other countries.
    [Show full text]
  • (BSD) Release Notes
    Intel® QuickAssist Technology Software for Free Berkeley Software Distribution* (FreeBSD*) Release Notes - Software version Package Version: QAT.B.3.9.0-00009 February 2021 Intel Confidential Document Number: 621446-006 You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein. Intel technologies' features and benefits depend on system configuration and may require enabled hardware, software, or service activation. Learn more at intel.com, or from the OEM or retailer. No computer system can be absolutely secure. Check with your system manufacturer or retailer or learn more at intel.com. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. Tests document performance of components on a particular test, in specific systems. Differences in hardware, software, or configuration will affect actual performance. Consult other sources of information to evaluate performance as you consider your purchase. For more complete information about performance and benchmark results, visit www.intel.com/performance. Intel does not control or audit third-party benchmark data or the web sites referenced in this document. You should visit the referenced web site and confirm whether referenced data are accurate. Copies of documents which have an order number and are referenced in this document may be obtained by calling 1-800-548- 4725 or by visiting www.intel.com/design/literature.htm. Intel, the Intel logo, and Xeon are trademarks of Intel Corporation in the United States and other countries.
    [Show full text]
  • Help!My Computer Is Broken
    HELP! MY COMPUTER IS BROKEN (How do I fix it?) BY BARRY COLLINS THE INTOLERANT PERSON’S GUIDE TO 1KEEPING YOUR COMPUTER COMPUTING 2 HELP! MY COMPUTER IS BROKEN BARRY COLLINS 3 First published in 2020 by Raspberry Pi Trading Ltd, Maurice Wilkes Building, St. John’s Innovation Park, Cowley Road, Cambridge, CB4 0DS Publishing Director: Russell Barnes • Editors: Phil King, Simon Brew • Sub Editor: Nicola King Design: Critical Media • Illustrations: Sam Alder with Brian O Halloran CEO: Eben Upton ISBN: 978-1-912047-90-1 The publisher, and contributors accept no responsibility in respect of any omissions or errors relating to goods, products or services referred to or advertised in this book. The publisher cannot accept responsibility for any injuries, damage to equipment, or costs incurred from advice, tutorials or suggestions in this publication. 4 CONTENTS About the author 9 About this book 10 Why is my laptop not turning on? 13 Why is my desktop computer not turning on? 15 Why is my laptop’s keyboard not working? 18 What are those black dots on my screen? 20 Why is my computer making strange beeps when I switch 22 it on? How can I tell if my computer is overheating? 24 Why is my laptop’s touchpad not working? 26 Why is there no sound coming from my laptop’s built-in 28 speakers? Why is there no sound coming from my computer’s external 30 speakers? Why is my mouse not working? 32 Why are games running really slowly on my computer? 35 Can I make my laptop faster by upgrading its memory? 37 Why won’t the USB port on my computer charge my phone?
    [Show full text]
  • Hangfix: Automatically Fixing Software Hang Bugs for Production
    HangFix: Automatically Fixing Soware Hang Bugs for Production Cloud Systems Jingzhu He Ting Dai North Carolina State University IBM Research [email protected] [email protected] Xiaohui Gu Guoliang Jin North Carolina State University North Carolina State University [email protected] [email protected] ABSTRACT ACM Reference Format: Software hang bugs are notoriously difficult to debug, which Jingzhu He, Ting Dai, Xiaohui Gu, and Guoliang Jin. 2020. HangFix: often cause serious service outages in cloud systems. In this Automatically Fixing Software Hang Bugs for Production Cloud Systems. In Symposium on Cloud Computing (SoCC ’20), October 19– paper, we present HangFix, a software hang bug fixing frame- 21, 2020, Virtual Event, USA. ACM, New York, NY, USA, 14 pages. work which can automatically fix a hang bug that is trig- https://doi.org/10.1145/3419111.3421288 gered and detected in production cloud environments. Hang- Fix first leverages stack trace analysis to localize the hang function and then performs root cause pattern matching to classify hang bugs into different types based on likely 1 INTRODUCTION root causes. Next, HangFix generates effective code patches Many production server systems (e.g., Cassandra [6], HBase based on the identified root cause patterns. We have imple- [2], Hadoop [7]) are migrated into cloud environments for mented a prototype of HangFix and evaluated the system lower upfront costs. However, when a production software on 42 real-world software hang bugs in 10 commonly used bug is triggered in cloud environments, it is often difficult cloud server applications. Our results show that HangFix to diagnose and fix due to the lack of debugging informa- can successfully fix 40 out of 42 hang bugs in seconds.
    [Show full text]
  • What Is System Hang and How to Handle It
    What is System Hang and How to Handle it Yian Zhu1, Yue Li2, Jingling Xue2, Tian Tan3, Jialong Shi1, Yang Shen3, Chunyan Ma3 1School of Computer Science, Northwestern Polytechnical University, Xi’an, P.R.China 2School of Computer Science and Engineering, University of New South Wales, Sydney, Australia 3School of Software and Microelectronics, Northwestern Polytechnical University, Xi’an, P.R.China {zhuya,machunyan}@nwpu.edu.cn {yueli,jingling}@cse.unsw.edu.au {silverbullettt,jialong.tea,yangfields}@gmail.com Abstract by operating system (OS) (except for some severe cases detected only partially by watchdog mechanisms Almost every computer user has encountered an un- provided by some modern OSes). This leaves the user responsive system failure or system hang, which leaves no choice but to power the system off. As a result, the user no choice but to power off the computer. In the OS fails to provide continuous services, causing this paper, the causes of such failures are analyzed in the user to lose some valuable data. Worse still, if the detail and one empirical hypothesis for detecting sys- computer system is deployed in some mission-critical tem hang is proposed. This hypothesis exploits a small applications, e.g., nuclear reactors, system hang may set of system performance metrics provided by the OS lead to devastating consequences. itself, thereby avoiding modifying the OS kernel and By observing existing studies dealing with system introducing additional cost (e.g., hardware modules). hang, we draw two conclusions. First, most studies, Under this hypothesis, we propose SHFH, a self- although being effective in certain cases, could only healing framework to handle system hang, which can address certain system hang scenarios [1]–[5].
    [Show full text]
  • Assessment and Improvement of Hang Detection in the Linux Operating System
    2009 28th IEEE International Symposium on Reliable Distributed Systems Assessment and Improvement of Hang Detection in the Linux Operating System Domenico Cotroneo∗, Roberto Natella∗†, and Stefano Russo∗† ∗Dipartimento di Informatica e Sistemistica, Università degli Studi di Napoli Federico II, Via Claudio 21, Naples, Italy †Laboratorio CINI-ITEM “Carlo Savy”, Complesso Universitario Monte Sant’Angelo, Ed.1, Via Cinthia, Naples, Italy {cotroneo, roberto.natella, stefano.russo}@unina.it Abstract—We propose a fault injection framework to assess detection mechanisms within OSs can fail, and they may hang detection facilities within the Linux Operating System lead to missing, misleading, or false detections. This is the (OS). The novelty of the framework consists in the adoption of case of hang failures, which are caused by a significant a more representative faultload than existing ones, and in the effectiveness in terms of number of hang failures produced; part of software faults in OS code [15]; they cause the OS representativeness is supported by a field data study on the to get partially or completely stalled, and to not provide Linux OS. Using the proposed fault injection framework, any response to user-space applications. It is difficult to along with realistic workloads, we find that the Linux OS detect hang failures, because they hamper the execution is unable to detect hangs in several cases. We experience a of the OS, and, unlike other types of failures (e.g., illegal relative coverage of 75%. To improve detection facilities, we propose a simple yet effective hang detector, which periodically memory access), they are not notified by the hardware.
    [Show full text]