DOCSLIB.ORG

ZCPR3 the Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
ZCPR3 the Manual TH E MANUAL RICHARD CONN NEW YORK ZOETROPE ZCPR3 The Manual Copyright 1985, New York Zoetrope, Inc. All rights reserved. Reproduction by any means, electronic, photographic, or otherwise, is strictly forbidden under U.S. and International copyright laws without the express written consent of the publisher. Library of Congress Cataloging in Publication Number: 84-061790 ISBN 0-918432-59-6 New York Zoetrope 80 East 11th Street New York, NY 10003 ZCPR3 The Manual was set in H-P Times Roman. The book was printed and bound by Maple-Vail Book Manufacturing Group at their York, PA. plant. Production: Mitch Knauffs, Chris Terry, Richard White. Printed in the United States of America First Printing: June, 1985 5 4 3 2 1 FOREWORD This book has been greatly needed since the release of ZCPR3 about six months ago. It took about eight months to write ZCPR3 and its online documentation. Surprisingly, it took six months to produce this book; to say the least, this book took much more effort and time than anticipated. But I feel it was worth it, and I thank the community of users who have patiently waited for the book to be completed. I thank Chris Terry for his monumental effort in performing the technical editing for this book. I also thank Frank Gaude of Echelon for his support. Finally, I thank my parents and my second family for the support and encouragement they gave me throughout the trial of creating the book. I believe that the end result is worth it. DEDICATED to my parents and my second family Richard Conn December 17, 1984 TABLE OF CONTENTS Section 1 Using ZCPR3 and Command Definitions 1 ZCPR3 and CP/M 3 2 Basic ZCPR3 Concepts 7 3 TOOLSET of ZCPR3 21 ALIAS (Version 1.1) 21 CD (Version 3.0) 23 CLEANDIR (Version 1.0) 24 CMD (Version 1.0) 25 CMDRUN 26 COMMENT (Version 2.0) 26 CP (SYSRCP) 27 CPSEL (Version 1.0) 28 CRC (Version 2.0) 29 DEV (Version 1.0) 30 DEVICE (Version 1.0) 31 DIFF (Version 2.0) 31 DIR (Version 1.0) 33 DIR (CP-Resident) 34 DIR (RCP-Resident, provided in SYS.RCP) 34 DPROG (Version 1.0) 35 DU/DIR Forms 42 DU3 (Version 1.0) 43 ECHO (Version 1.0) 44 ECHO (CP-Resident or RCP-Resident) 45 ELSE (from SYSFCP Version 1.0) 45 ERA (CP-Resident) 46 ERA (RCP-Resident) 46 ERASE (Version 5.0) 47 ERROR1 (Version 1.0) 48 ERROR2 (Version 1.0) 48 ERROR3 (Version 1.0) 49 ERROR4 (Version 1.0) 49 ERRORX (Version 1.0) 49 FI (from SYSFCP 1.0) 50 FINDF (Version 2.0) 50 GET (CP-Resident) 51 GO (CP-Resident or RCP-Resident) 52 GOTO (Version 1.0) 52 HELP (Version 5.0) 54 HELPCK (Version 1.0) 55 HELPPR (Version 1.0) 56 IF (Version 1.1) 56 IF (FCP-Resident) 58 IFSTAT (Version 1.0) 59 JUMP (CP-Resident) 59 LDR (Version 1.0) 60 LIST (CP-Resident) 61 LIST (RCP-Resident) 61 MCOPY (Version 1.4) 62 MENU (Version 3.2) 64 MKDIR (Version 3.0) 65 MU (RCP-Resident) 65 MU3 (Version 1.0) 66 NOTE 69 P (RCP-Resident) 69 PAGE (Version 2.0) 70 PATH (Version 3.0) 71 POKE (RCP-Resident) 72 PRINT (Version 2.0) 73 PROT (RCP-Resident) 74 PROTECT (Version 2.0) 75 PWD (Version 1.0) 76 QUIET (Version 1.0) 77 RECORD (Version 3.0) 77 REG (Version 1.0) 79 REG (RCP-Resident) 79 REN (CP-Resident) 80 REN (RCP-Resident) 80 RENAME (Version 3.0) 80 SAK (Version 2.0) 81 SAVE (CP-Resident) 82 SETFILE (Version 1.0) 83 SH (Version 1.0) 84 SHCTRL (Version 1.0) 84 SHDEFINE (Version 1.0) 85 SHFILE (Version 1.0) 85 SHOW (Version 1.0) 86 SHSET (Version 1.0) 86 SHVAR (Version 1.0) 88 SUB (Version 3.0) 88 TCCHECK (Version 1.0) 91 TCMAKE (Version 1.0) 91 TCSELECT 97 TYPE (CP-Resident) 101 TYPE (RCP-Resident) 101 UNERASE (Version 1.0) 101 VFILER (Version 1.0) 103 VMENU (Version 1.0) 103 WHEEL (Version 3.0) 104 WHL (RCP-Resident) 105 XD (Version 1.2) 105 XDIR (Version 2.0) 107 XIF (Version 1.0) 111 Z3INS (Version 1.0) 112 Z3LOC (Version 1.0) 113 ZEX (Version 3.0) 113 4 On-Line HELP Subsystem 121 5 Menu Subsystem 133 (V)MENU Programming Command Summary 144 (V)MENU Error Messages 147 VMENUCK (Version 1.0) 147 MENUCK (Version 1.0) 147 6 Shell Subsystem 149 7 VFILER and File Maintenance 153 VFILER Command Summary 154 User Functions 155 8 DU3 Disk Utility 161 Section 2 Inside ZCPR3 9 Inside the ZCPR3 Command Processor 183 10 Inside the ZCPR3 System Segments 211 11 Inside the ZCPR3 Message Buffers 219 12 Inside ZEX 223 13 Inside the ZCPR3 Shells 225 14 Inside the ZCPR3 Error Handlers 227 15 Inside the ZCPR3 Tools 229 Section 3 Installation 16 Overview of ZCPR3 Installation 233 17 Step 1: Selcting the Features 243 18 Step 2: Planning the ZCPR3 247 19 Installation Steps 3 - 6 253 Step 3: Modifying the BIOS Cold Boot Routine 253 Step 4: Editing Z3HDR.LIB 269 Step 5: Overlaying the old BIOS and the CCP 280 Step 6: Implanting the OperatingSystem Image 280 Sample Session 280 20 Step 7: System Segment Installation 291 21 Step 8: Utility Installation 305 22 TCAP Facility 309 Appendices A Glossary of Terms 329 B Documentation 333 C References 335 ZCPR3 and SYSLIB2 Publications and Documentation ZCPR3 Manuals SYSLIB2 Manuals Software Upgrades to SYSLIB2 and ZCPR2 Sources CP/M Books ZCPR3 Sources Selected Computer Clubs ACGNJ and SIG/M New York Amateur Computer Club Echelon, Inc. New York Zoetrope, Inc. Magazine Articles on ZCPR3 ZCPR3 Newsletters ZCPR3 Configuration Management ZCPR3 Electronic Bulletin Board D Obtaining Free Software 339 Index 347 S e c t io n 1 Using ZCPR3 and Command Definitions "As long as there were no machines, programming was not a problem at all; when we had a few weak computers, programming became a mild problem and now that we have gigantic computers, programming has become an equally gigantic problem. In this sense the electronic industry has not solved a single problem, it has only created them—it has created the problem of using its product." E.W. Dijkstra, ACM Turing Award Lecture, 1972 "In the development of our understanding of complex phenomena, the most powerful tool available to the human intellect is abstraction. Abstraction arises from a recognition of similarities between certain objects, situations, or processes in the real world, and the decision to concentrate on these similarities, and to ignore for the time being the differences." C.A.R. Hoare, Notes on Data Structuring. This book is divided into three sections. Section 1 deals with learning and using the system. In Chapters 1-2, the philosophy of ZCPR3 is presented, ZCPR3 and CP/M 2.2 are compared, and the basic concepts of ZCPR3 are outlined. Chapter 3 presents the ZCPR3 Toolset in detail; all of the commands are listed in alphabetic order, with their syntax, their application, and examples of how to use them. After reading these chapters, a person should be ready to use the ZCPR3 System. Chapters 4 through 8 discuss the online Help, Menu, and Shell subsystems, together with two of the major tools (YFILER and DU3) in somewhat more detail than could be given in Chapter 3. Section 2 discusses the internal structure and workings of some parts of ZCPR3; this section, comprising Chapters 9 through 15, is aimed at the systems programmer who will be using, installing, and adapting to his own needs a ZCPR system. Section 3 contains detailed instructions for installing a ZCPR3 system. Chapter 16 presents an overview of the installation process, which is complex and requires familiarity with assembly language programming and the interface requirements of CP/M. Chapter 17 offers guidance on how to select the many features available if you don’t have enough memory or disk space to accommodate all of them. Chapters 18 through 22 describe in detail the installation procedures and the ZCPR3 tools that make life easier for the installer. Do not be put off by the complexities of Section 3. If you merely want to use ZCPR3 with all its flexibility and added power, you can obtain a self-installing version, called Z3-DOT-COM from Echelon, Inc. This version pokes and pries into your own system until it has all the required information, and then begins the installation process automatically, reporting on your console as it completes installation of each feature and utility. Two very simple commands entered from the keyboard do all the work for you. But if you are installing ZCPR3 from the source files, or if you want to adapt the system to meet special needs of your own, then you will need to study Section 3 very l 2 Using ZCPR3 and Command Definitions Sec. 1 closely. Throughout this book a working knowledge of CP/M 2.2 is assumed. Further, since ZCPR3 is not compatible with CP/M versions earlier than 2.2, the reader should assume that all references to "CP/M" mean "CP/M version 2.2." Using ZCPR3 and Command Definitions Sec. 1 3 1 ZCPR3 AND CP/M This chapter explains the ideas and motivation behind ZCPR3. It describes, in some detail, what ZCPR3 offers to the user and what the user needs to understand in order to make effective use of ZCPR3.
Load more

Recommended publications
  • Hacker's Handbook for Ringzer0 Training, by Steve Lord
    Hacker’s Handbook For Ringzer0 Training, by Steve Lord This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. Copyright ©2021 Raw Hex Ltd. All Rights Reserved. Retro Zer0 is a trademark of Ring Zer0 Training. Raw Hex is a trademark of Raw Hex Ltd. All other trademarks are the property of their respective owners. Raw Hex Ltd reserve the right to make changes or improvements to equipment, software and documentation herein described at any time and without notice. Notice: Please be advised that your Retro Zer0 has no warranty, and that tampering with the internal hardware and software of your Ring Zer0 is widely encouraged as long as you do so with appropriate regard to safety. Contents 1 Preface 5 1.1 Safety ........................... 6 1.2 Understanding This Document ............ 6 2 Before You Start 7 2.1 Check You Have Everything .............. 7 2.2 Back Up The SD Card ................. 8 2.3 Connecting Up Your Retro Zer0 ............ 8 2.4 Powering Up ....................... 10 2.5 Resetting Your Retro Zer0 . 10 2.6 Powering Down ..................... 10 3 First Steps 11 3 4 CONTENTS 3.1 Testing The Keyboard . 11 3.2 Using CP/M ....................... 12 3.3 Would You Like To Play A Game? . 14 3.4 MultiCPM Extras ..................... 17 3.5 Useful Tools ....................... 19 3.6 What’s On The Card? . 20 3.7 Putting It All Together . 23 3.8 Where To Read More . 25 4 Being Productive With Retro Zer0 27 4.1 WordStar .........................27 4.2 Supercalc .........................30 4.3 DBase ...........................32 4.4 Microsoft BASIC .....................32 4.5 Turbo Pascal .......................34 4.6 Forth 83 .........................36 4.7 ZDE ............................38 4.8 Z80 Assembler .....................39 4.9 Hi-Tech C .........................43 4.10 XLisp ...........................46 CONTENTS 5 4.11 Installing New Software .
    [Show full text]
  • Practical C++ Programming Copyright 2003 O'reilly and Associates Page 1 I/O Packages
    Chapter - 16 File Input/ Output Practical C++ Programming Copyright 2003 O'Reilly and Associates Page 1 I/O Packages There are 3 different I/O packages available to the C++ programmer: • The C++ streams package. This package is used for most I/O. • The unbuffered I/O package. Used primarily for large file I/O and other special operations. • The C stdio package. Many older, C-- programs use this package. (A C-- program is a C program that has been updated to compile with a C++ compiler, but uses none of the new features of the new language.) This package is useful for some special operations. Practical C++ Programming Copyright 2003 O'Reilly and Associates Page 2 C++ I/O C++ provides four standard class variables for standard I/O. Variable Use std::cin Console in (standard input) std::cout Console output (standard output) std::cerr Console error (standard error) std::clog Console log Normally std::cin reads from the keyboard, and std::cout, cerr, and clog go to the screen. Most operating systems allow I/O redirection my_prog <file.in my_prog >file.out Practical C++ Programming Copyright 2003 O'Reilly and Associates Page 3 File I/O File I/O is accomplished using the <fstream.h> package. Input is done with the ifstream class and output with the ofstream class. Example: ifstream data_file; // File for reading the data from data_file.open("numbers.dat"); for (i = 0; i < 100; ++i) data_file >> data_array[i]; data_file.close(); Open can be consolidated with the constructor. ifstream data_file("numbers.dat"); The close will automatically be done by the destructor.
    [Show full text]
  • HUMBUG® 68000 Version
    HUMBUG® 68000 Version by Peter A. Stark Copyright © 1986 - 1990 by Peter A. Stark Star-K Software Systems Corporation P. O. Box 209 Mt. Kisco, N. Y. 10549 All rights reserved Copyright © 1986 - 1990 by Peter A. Stark All Star-K computer programs are licensed on an "as is" basis without warranty. Star-K Software Systems Corporation shall have no liability or responsibility to customer or any other person or entity with respect to any liability, loss or damage caused or alleged to be caused directly or indirectly by computer equipment or programs sold by Star-K, including but not limited to any interruption of service, loss of business or anticipatory profits or consequential damages resulting from the use or operation of such computer or computer programs. Good data processing procedure dictates that the user test the program, run and test sample sets of data, and run the system in parallel with the system previously in use for a period of time adequate to insure that results of operation of the computer or program are satisfactory. SOFTWARE LICENSE A. Star-K Software Systems Corp. grants to customer a non-exclusive, paid up license to use on customer's computer the Star-K computer software received. Title to the media on which the software is recorded (cassette and/or disk) or stored (ROM) is transferred to customer, but not title to the software. B. In consideration of this license, customer shall not reproduce copies of Star-K software except to reproduce the number of copies required for use on customer's computer and shall include the copyright notice on all copies of software reproduced in whole or in part.
    [Show full text]
  • Assembly Language Step-By-Step: Programming with DOS and Linux
    Assembly Language Step-by-Step: Programming with DOS and Linux, Second Edition by Jeff Duntemann ISBN:0471375233 John Wiley & Sons © 2000 (613 pages) A “Lost World” journey into 16-bit assembler programming concepts and techniques. <?xml version="1.0" encoding="ISO-8859-1"?> Table of Contents Assembly Language Step-by-Step—Programming with DOS and Linux, Second Edition Foreword Introduction - "Why Would You Want to Do That?" Another Pleasant Valley Saturday Understanding What Computers Chapter 1 - Really Do Chapter 2 - Alien Bases Getting Your Arms around Binary and Hexadecimal Chapter 3 - Lifting the Hood Discovering What Computers Actually Are The Right to Assemble The Process of Making Assembly Language Chapter 4 - Programs NASM-IDE: A Place to Stand Give me a lever long enough, and a Chapter 5 - place to stand, and I will move the Earth. An Uneasy Alliance The x86 CPU and Its Segmented Memory Chapter 6 - System Following Your Instructions Meeting Machine Instructions up Close Chapter 7 - and Personal Chapter 8 - Our Object All Sublime Creating Programs that Work Dividing and Conquering Using Procedures and Macros to Battle Chapter 9 - Complexity Bits, Flags, Branches, and Tables Easing into Mainstream Chapter 10 - Assembly Programming Chapter 11 - Stringing Them Up Those Amazing String Instructions The Programmer's View of Linux Tools and Skills to Help You Write Chapter 12 - Assembly Code under a True 32-Bit OS Coding for Linux Applying What You've Learned to a True Chapter 13 - Protected Mode Operating System Conclusion - Not the End, But Only the Beginning Appendix A - Partial 8086/8088 Instruction Set Reference Appendix B - Segment Register Assumptions for Real Mode Segmented Model Appendix C - Web URLs for Assembly Programmers Appendix D - Segment Register Assumptions Appendix E - What's on the CD-ROM? Index List of Figures List of Tables Back Cover The bestselling guide to assembly language--now updated and expanded to include coverage of Linux.
    [Show full text]
  • Character Pattern Editor for On-Screen Display LSI for Windowstm
    To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding. Renesas Electronics website: http://www.renesas.com April 1st, 2010 Renesas Electronics Corporation Issued by: Renesas Electronics Corporation (http://www.renesas.com) Send any inquiries to http://www.renesas.com/inquiry. Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples.
    [Show full text]
  • Microcontrollers Apnote AP0827
    Microcontrollers ApNote AP0827 : Additional file AP082701.EXE available ADIS51 - Disassembler with One-Line Assembler for the 8051 and C500 8-Bit Microcontroller Family ADIS51 allows the analysis of program code for the microcontrollers of the 8051/C500 family. Program code in different formats can be loaded and displayed in Hex-dump or Dis- assembler format. Single instructions can be input using the built-in Assembler. Program code flow and instructions can be analysed and written into a Log-file in a list or assembler source format. SFR and bit symbol operation is provided using a symbol definition file. Richard Schmid, Microcontroller Product Definition, Siemens HL Munich Semiconductor Group 10.97, Rel. 01 ADIS51 - Disassembler with One-Line Assembler for the 8051 and C500 8-Bit Microcontroller Family Contents Page 1 Starting of ADIS51 . 3 2 Main Menu . 4 3 Basic Function <F1> : Loading of a Data File . 5 4 Basic Function <F2> : Writing Memory Buffer Contents into a HEX- or BIN-Files . 6 5 Basic Function <F3> : Selection of a Microcontroller Type . 7 6 Basic Function <F4> : Disassembler / One-Line Assembler Menu . 8 6.1 General Operation . 8 6.2 Memory Buffer Code Analysis . 9 6.3 Input of a New Address . 11 6.4 Generation of a Log-File . 12 7 Basic Function <F5> : Hex-Dump Menu . 16 7.1 General Operation . 16 7.2 Input of a New Address . 17 7.3 Generation of a Log-File . 17 8 Basic Function <F6> : Overview on the Memory Buffer Usage . 18 9 Basic Function <F7> : Selection of Options . 19 Appendix .
    [Show full text]
  • What Is Digital Forensics (Aka Forensic Computing)?
    Digital Forensics for Archivists: Fundamentals Instructor: Christopher (Cal) Lee University of North Carolina at Chapel Hill September 22, 2016 Greeley, CO 1 Digital Archives Specialist (DAS) Curriculum and Certification Program offered by SAA: . Foundational Courses—must pass 4 . Tactical and Strategic Courses—must pass 3 . Tools and Services Courses—must pass 1 . Transformational Courses—must pass 1 . Course examinations are administered online. 2 1 Agenda . Welcome and introductions . Motivation and scope . Technical background . Representation Information . File systems and file management . Extracting data from media . Tools and methods . Conclusions, questions, discussion 3 Welcome and Introductions 4 2 Motivation and Scope Applying Digital Forensics to Archival Work 5 Many archivists know how to process this stuff: Source: The Processing Table: Reflections on a manuscripts internship at the Lilly Library. https://processingtable.wordpress.com/tag/archival-processing/ 6 3 How about processing this stuff? Source: “Digital Forensics and creation of a narrative.” Da Blog: ULCC Digital Archives Blog. http://dablog.ulcc.ac.uk/2011/07/04/forensics/ 7 Same Goals as When Acquiring Analog Materials Ensure integrity of materials Allow users to make sense of materials and understand their context Prevent inadvertent disclosure of sensitive data 8 4 Same Fundamental Archival Principles Apply Provenance • Reflect “life history” of records • Records from a common origin or source should be managed together as an aggregate unit Original Order Organize and manage records in ways that reflect their arrangement within the creation/use environment Chain of • “Succession of offices or persons who have held Custody materials from the moment they were created”1 • Ideal recordkeeping system would provide “an unblemished line of responsible custody”2 1.
    [Show full text]
  • Microcontrollers Apnote AP1640
    Microcontrollers ApNote AP1640 : Additional file AP164002.EXE available ADIS16X - Disassembler with One-Line Assembler for the C16X 16-Bit Microcontroller Family ADIS16X allows the analysis of program code for the 16-bit microcontrollers of the C16X family. Program code in different formats can be loaded and displayed in Disassembler or Hex-dump format. Single instructions can be input using the built-in One-Line Assembler. Program code can be written into a Log-file in a list or assembler source format. SFR and bit symbol operation is provided using a symbol definition file. Richard Schmid, Microcontroller Product Definition, Siemens Munich Semiconductor Group 11.97, Rel. 02 ADIS16X - Disassembler with One-Line Assembler for the C16X 16-Bit Microcontroller Family Contents Page 1 Starting of ADIS16X . 3 2 Main Menu . 4 3 Basic Function <F1> : Loading of a Data File . 5 4 Basic Function <F2> : Writing Memory Buffer Contents into a HEX- or BIN-File . 6 5 Basic Function <F3> : Selection of a Microcontroller Type . 7 6 Basic Function <F4> : Disassemblers / One-Line Assemblers Menu . 8 6.1 General Operation . 8 6.2 Input of a New Address . 9 6.3 Generation of a Log-File . 9 7 Basic Function <F5> : HEX-Dump Menu . 11 7.1 General Operation . 11 7.2 Input of a New Address . 12 7.3 Generation of a Log-File . 12 8 Basic Function <F6> : Overview on the Memory Buffer Usage . 13 9 Basic Function <F7> : Selection of Options . 14 Appendix . 15 A Error and Status Messages . 15 B One-Line Assembler Formats . 16 C Definition of the Symbol Definition File .
    [Show full text]
  • Lloyd Research Ltd. , 7 / 7A Brook Lane, Warsash, Southampton, Hants
    INSTRUCTION MANUAL FOR ; LgOOO PROGRAMMER LloydResearch Ltd. INSTRUCTION MANUAL FOR L9OOO PROGRAMMER LAST UPDATE: 28/O4/95 LLOYD RESEARCH LTD. , 7 / 7A BROOK LANE, WARSASH, SOUTHAMPTON, HANTS. Tel: ( 01489 ) 885575/574O4O. Telex: No longer avaj-.]-abIe. Fax: (01489) BB5853. LgOOO PROGRAMMERACCESSORY LIST NOTE: PLxxx/L = 1 socket module PLxxx/2 = 2 socket module Plxxx/3 = 3 socket modul-e PLxxx/4 = 4 socket module SOFTWARE -PC SOFTWARE: provi-des remote control f rom a PC. Includes facility to store master eproms on disc, editj-ng and device selection. COMPRESS: Can Ue used by itseff, speeds up download over the Centronics port, typically 5 times, e.g. the download time for a lM eprom is 10 seconds. CONTRACTUPDATE SERVICE (IN UK): rwo software upaateFissued at six monthly intervals. MODULES PLo54/2 MOpULE: Covers NEC micro 78P054 family in quad flat pack (QFP). PL2OT/4 MODULE: Covers Toshiba mj-cro 47P2O\VP family in DIL package. przaz/a MopuLE: Covers microcontrollers such as 47P242VN in shrink dip package. PL3OO/2 & PL3OO/4 MOpULE: Covers 32/28/24 pin e(e)proms in DIL packages. Accommodates e(e)proms with a lead pitch of O.3" or 0.6". PL3OB/4 MODULE: Covers B pi-n serial eeproms in DIL packages. PL3r2/2 MOpULE: Covers NEC micro 7BP3L2AL family - PLCC package PL3L6/2 MODULE: Covers NEC micro 75P316GF family i-n quad flat pack (QFP). PL32O/4 MOpULE: Covers microcontrollers such as TMS320E. PL32B/2 &. PL32B/4 MOpULE: Covers '28 pin DIL eproms' with Jedec pJ-nout in PLCC packages such as 2764, 27128, 27256, 27512, etc.
    [Show full text]
  • Debugger Basics - Training
    Debugger Basics - Training TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Training ............................................................................................................................ Debugger Training ........................................................................................................................ Debugger Basics - Training ....................................................................................................... 1 System Concept ...................................................................................................................... 5 On-chip Debug Interface 6 Debug Features 6 TRACE32 Tools 7 On-chip Debug Interface plus On-chip Trace Buffer 9 On-chip Debug Interface plus Trace Port 11 NEXUS Interface 12 Starting a TRACE32 PowerView Instance ............................................................................. 13 Basic TRACE32 PowerView Parameters 13 Configuration File 13 Standard Parameters 14 Examples for Configuration Files 15 Additional Parameters 19 Application Properties (Windows only) 20 Configuration via T32Start (Windows only) 21 About TRACE32 22 Version Information 22 Prepare Full Information for a Support Email 23 Establish your Debug Session ............................................................................................... 24 TRACE32 PowerView .............................................................................................................. 25 TRACE32 PowerView Components 25 Main Menu Bar and Accelerators
    [Show full text]
  • Design and Building of Home Made 8051 Microcontroller Emulator
    Sudan Academy of Sciences ( SAS) Atomic Energy Council Design and building of home made 8051 Microcontroller Emulator By Abdclmoncim Elobeid Hussein iVI.Sc. in Electronics Engineering University of Khartoum ( 2002) A Thesis Submitted to the Sudan Academy of Sciences In Fulfillment of the Requirements for Doctor of Philosophy Degree Ph.D. in Electronics Engineering Supervisor Dr.Abd Elrasol Gabar Elzobaidi September 2009 Sudan Academy of Sciences (SAS) Examination committee Name External examiner Dr. Sid Ahmed Ibrahim Internal examiner Dr. P'arouk Idris llabbani Supervisor Dr. Abdelrasoul Gabar Hlzobaidi Dedication ll'or wfwm tfwy tfiougfit we are of their concern ^L&J all uu iao uu ^ i « J&Jl (J ic -llLa t-Lu 5 ^jrti <Vi I t^*iml <—L^Jl IJA 4. Ij&lM \ »J*-»lL) 3 j^JtjjULa ^ »_L>Ua]|j ac-LiU , A . O \ JjjLill SbVI jl nr.J jj— VAJ ^1 JJ^UI SbV ^JJ^^I J>\jd\ j CjL^ajjJ] .Lpj.1 .As*-* ialJLi j I^JIJJILU 3JJJJ vb byj ISjAi^a ^jjSjJl ^aJLxJl S^a.j (j^ia ^.l.^l.nl <_U*Jl IJtA J.Je»S ^JJjjjfUVI J»lj-iH ^ j J n-> j ijj jc SjLc- Clllj% ajjjl Lai .dljj l-t")!! (jiaxJ £-a (-^*-LJl j_c V JJ o>—% ojSI-ll) dib Ajj^aJl CJlAaaJt dial Vina ) 4 .aS'i j»£jkloll <L«AJ ^Jj La Sole ^ iViiii,all jj-alijjJ LSIj-aj <<• «ji>iati C_>jxl-tll jLj-a. £<e (J^ljail .^jlaJl SjSlill J- . jlll <• iu?i«ll «_1 axubJl ^Jc <4_al.lklu>l j£-aJ 1 >ji>i<i\l L_]jiJ-»ti ^Jc ^Ajla ^^aUjj ^1 J—jl (J}* «JJ J «J «, iji nail <-_) a ml ->It ^ifi.
    [Show full text]
  • Recovery from Soft Errors in Triplicated Computer Systems Operating in Lock-Step
    ' OLE COPY Nor REMOVE NBSIR 79-1927 0£c 14 1979 Recovery from Soft Errors in Triplicated Computer Systems O perat i ng in Lock-Step A. L. Koenig A. W. Holt System Components Division Center for Computer Systems Engineering Institute for Computer Sciences and Technology National Bureau of Standards Washington, D.C. 20234 June 30, 1979 Issued November 1979 Sponsored by Defense Nuclear Agency Washington, D.C. 20305 NBSIR 79-1927 RECOVERY FROM SOFT ERRORS IN TRIPLICATED COMPUTER SYSTEMS OPERATING IN LOCK-STEP A. L. Koenig A. W. Holt System Components Division Center for Computer Systems Engineering Institute for Computer Sciences and Technology National Bureau of Standards Washington, D.C. 20234 June 30, 1 979 Issued November 1979 Sponsored by Defense Nuclear Agency Washington, D.C. 20305 U S. DEPARTMENT OF COMMERCE Luther H. Hodges, Jr., Under Secretary Jordan J. Baruch, Assistant Secretary for Science and Technology NATIONAL BUREAU OF STANDARDS. Ernest Ambler, Director RECOVERY FROM SOFT ERRORS IN TRIPLICATED COMPUTER SYSTEMS OPERATING IN LOCK-STEP ABSTRACT A Triply Modular Redundant (TMR) computer system operating in clocked lock-step is being investigated for an application requiring a Mean Time Between Failure of five years. No mechanical memories are used; this allows comparison of the outputs of the three computers to be made each clock period. The most novel contribution is the method of recovery from soft errors, such as those produced by lightning strokes or alpha particles. Data are provided on the uptime history of an experimental system, which uses three commercial microcomputers. Key Words: Fault tolerant computer; soft errors; triply modular redundant; TMR.
    [Show full text]