Text preview for : U01-0000-21_Universal_One_Microcomputer_Development_System_Operator_Reference_Nov76.pdf part of



| Home

MILLENNIUM INFORMATION SYSTEMS ,INC.
UNIVERSAL ONE

Microco~er
Development System

Operator's Guide
UNIVERSAL ONE




Microco~er
Development System

Operators Gllide
Document No. U01-0000-21
Issued Nov. 1976




MILLENNIUM INFORMATION SYSTEMS ,INC.
420 MATHEW STREET, SANTA CLARA, CALI FORNIA 95050, 408-243-6652
DOCUMENT NO. U01-0000-21

PRICE - $35.00




Copyright 1976, Millennium I nformation Systems, I nco All rights reserved.

Mi Ilennium I nformation Systems, I nco claims trademark rights to the names
UNIVERSAL ONE and UNIVERSAL EMULATOR




ii
Table of Contents


Paragraph Page

CHAPTER INTRODUCTION
1 .1 Objectives of a Microcomputer Development System 1-1
1.2 Universal One Overview 1-1
1.3 About Th is Book. . . . . . . . . . . . . . 1-4

CHAPTER 2 SYSTEM DESCRIPTION
2.1 Introduction..... 2-1
2.2 Hardware....... 2-1
2.2.1 Development Computer 2-1
2.2.2 Emulation Hardware . 2-4
2.2.3 Dual Floppy Disk Subsystem 2-4
2.2.4 Peripherals...... 2-5
2.2.5 User-Supplied Peripherals . 2-7
2.3 Software......... 2-7
2.3.1 UDOS (Universal Disk Operating System) 2-7
2.3.2 The Debugger . . . 2-7
2.3.3 PROM Programming 2-8
2.3.4 The Editor . . . . 2-8
2.3.5 The Assemb ler. . . 2-8
2.3.6 Systems Readiness Test 2-8

CHAPTER 3 SYSTEM INSTALLATION AND OPERATION
3.1 Introduction.................. . 3-1
3.2 Unpacking.................. 3-1
3.2.1 Unpacking the Universal One Development Computer. 3-1
3.2.2 Unpacking the CRT Terminal . . 3-1
3.2.3 Unpacking the Floppy Disk Unit. 3-2
3.2.4 Unpacking the Line Printer. . 3-2
3.2.5 Installing the Emulation Cable. . 3-4
3.3 Physical Installation. . . . . . . 3-4
3.3.1 Power and Cable Interconnections 3-4
3.3.2 Controls and Indicators 3-7
3.3.3 Development Computer . . . . 3-7



iii
Table of Contents (Cant.)

Paragraph Page
3.3.4 Dual Floppy Disk Unit 3-8
3.3.5 CRT Terminal 3-9
3;3.6 Line Printer. . . . . 3-9
3.4 Operation . . . . . . 3-10
3.4.1 Formatting and Verifying New Diskettes. 3-10
3.4.2 System Startup Procedure 3-11
3.4.3 Manual Reset . . . . . . . . . . . 3-12

CHAPTER 4 UNIVERSAL DISK OPERATING SYSTEM
4.1 Introduction . . . . . . 4-1
4.2 UDOS Overview . . . . . 4-1
4.2.1 Resident U DOS Modu les . 4-2
4.2.2 UDOS Overlays . . . . 4-2
4.3 Files, Devices, and Channels 4-3
4.4 Entering UDOS Commands. 4-5
4.5 Special Keys 4-6
4.5.1 Delete Key 4-6
4.5.2 Escape Key 4-7
4.5.3 Space Bar. 4-7
4.5.4 CTR L-Z Command 4-7
4.6 The U DOS Commands. 4-8
4.6.1 The UDOS Command Structure 4-8
4.6.2 U DOS Command Completion 4-9
4.6.3 System Control Commands. 4-10
4.6.4 System Option Commands . 4-15
4.6.5 System Utilities Commands. 4-17
4.6.6 Object Program Uti Iity Commands 4-25
4.6.7 Command Files . . . 4-29
4.6.8 Command File Utilities 4-30
4.6.9 UDOS Error Messages . 4-32




iv
Table of Contents (Cont.)

Paragraph Page
CHAPTER 5 THE DEBUGGER
5.1 Introduction . . . . 5-1
5.2 The Debug Program. . . . 5-1
5.3 Invoking the Debugger. . . 5-2
5.4 Sample Debug Session (Using a 2650 Slave) 5-3
5.5 Debug Commands . . . . . . . . . . 5-7

CHAPTER 6 THE EDITOR
6.1 Introduction 6-1
6.2 Editor Overview . . . 6-1
6.3 U DOS Command Edit. 6-2
6.4 Edit Example . . . . 6-3
6.5 Editor Command Descriptions 6-10
6.5.1 Editor Command Line 6-10
6.5.2 Editor Command Description Conventions . 6-10
6.5.3 I nsertion Commands . 6-13
6.5.4 Deletion Commands 6-14
6.5.5 Alteration Commands . 6-15
6.5.6 Search Commands . . 6-17
6.5.7 I/O Commands 6-18
6.5.8 Buffer Line Pointer Commands 6-21
6.5.9 Utilities . . 6-21
6.5.10 MARCROS . 6-26
6.6 Editor Messages 6-27

CHAPTER 7 THE ASSEMBLER
7.1 Introduction 7-1
7.2 Assembler Overview. . . . . 7-1
7.3 Using the Assembler . . . . 7-1
7.4 Loading An Assembled Program 7-2
7.5 Sample Assembly Listing. . . 7-3




v
Table of Contents (Cont.)

Paragraph Page

CHAPTER 8 PROM PROGRAMMER
8.1 Introduction . . . . . . . . . . . . 8-1
8.2 PROM Programming Hardware and Software 8-1
8.3 Using the PROM Programmer . 8-1
8.4 PROM Programmer Commands . . . -. . 8-2

CHAPTER 9 SUPERVISOR CALL INTERFACE
9.1 Introduction.......... 9-1
9.2 General Description of Supervisor Calls 9-1
9.3 Service Request Block (SRB) . 9-2
9.3.1 SRB Bytes . . . . . . . 9-2
9.3.2 SVC Function Descriptions. 9-3



APPENDIX A UDOS COMMAND SUMMARY
APPENDIX B DEBUGGER COMMAND SUMMARY
APPENDIX C EDITOR COMMAND SUMMARY
APPENDIX D SVC FUNCTION CODES
APPENDIX E SRB STATUS CODES
APPENDIX F SMS TAPE FORMAT
APPENDIX G SYSTEM READINESS TEST
APPENDIX H SYSTEM UTILITY COMMAND FILES




vi
list of Ilustrations


Figure Page
1-1 The UNIVERSAL ONE Microcomputer Development System 1-0
1-2 General Block Diagram of a Microprocessor-based Product. 1-3
2-1 Overall Block Diagram of the UNIVERSAL ONE . . 2-2
2-2 Data Organization on a Diskette . . . . . . . . . 2-6
3-1 Development Computer Printed Circuit Board Layout 3-2
3-2 Development Computer (Top View) . . . . . . . 3-3
3-3 Envelope Dimensions of System Units. . . . . . . 3-5
3-4 Typical Cabling Diagram of UNIVERSAL ONE System Installation 3-6
3-5 Front Panel of the Development Computer. 3-8
3-6 Rear Panel of the Development Computer 3-9
3-7 Rear Panel of the Floppy Disk Drive . . . 3-10
3-8 Inserting a Diskette. . . . . . . . . . 3-11
5-1 Displays During Sample Debugging Session . 5-4
5-2 Typical Displays During Various Debugging Modes. 5-8
6-1 A Sample Source Program . . . . . . . . . . 6-3
6-2 Entering Text and Display the Buffer . . . . . . 6-5
6-3 Use of FIND, SUBSTITUTE and REPLACE Commands. 6-6
6-4 Displaying the Buffer and Filing . . . . . . . . . 6-6
6-5 Sample Double Precision Add and Subtract Programs. 6-7
6-6 Adding Data to an Existing File . . . . . . . . . 6-9
6-7 Inserting Lines Into the Buffer . . . . . . . . . 6-11
7-1 Sample 2650 Slave Program Listing Ready for Assembly. 7-4
7-2 Sample 2650 Slave Assembly Listing . . . . . . . . 7-5




vii
Chapter

Introduction

1.1 OBJECTIVES OF A MICROCOMPUTER DEVELOPMENT SYSTEM.

In the development of any product that includes a microprocessor, there are aspects
which have no parallel either in random logic design or in computer program develop-
ment (the two predecessors of microprocessor product development).

There is no clear cut demarcation between logic which should be implemented
using random logic hardware, or logic which should be implemented with programmed
instructions; that is what makes microprocessor product development unique. A
successful microcomputer development system, such as UNIVERSAL ONE, must
therefore support digital logic development and program creation with equal ease.

If in addition, the product or series of products can benefit from the use of different
microprocessors, a single universal hardware and software development system, of
the configuration of UNIVERSAL ONE, has several easily recognizable advantages:

1. It eliminates the cost of another development system each time a new micro-
processor is to be implemented.
2. It providesa common system for all development, thus eliminating heavy
investments in personnel training and software for multiple systems.
3. It frees the designer to consider any microprocessor-solely on the basis of
its capabilities and cost-effectiveness, rather than because the designer is
locked into a microprocessor from a previous product commitment.


1.2 UNIVERSAL ONE OVERVIEW.


1.2.1 Master/Slave Concept. UNIVERSAL ONE, achieves the required uni-
versality by dividing its operations into two functional areas. Those tasks that are
related to the development system itself are assigned to a master central processing
unit, and those that are prototype-related are assigned to a second, slave CPU. As
many as four different slaves may be installed simultaneously and individually invoked
with a corresponding slave diskette. This mUltiple architecture enables the hardware
to support a particular microprocessor with the addition of a printed circuit card
containing the corresponding slave CPU. Since the master processor need not be
changed to accommodate new slave units, all of the operating system software remain
the same.



1-1
The master CPU is responsible for all system services that are not prototype-
dependent, such as: