EK-DS730-UG-002 VAX-ll/730 Diagnostic Overview Manual
EK-DS730-UG-002 VAX-ll/730 Diagnostic Overview Manual Prepared by Educational Services of Digital Equipment Corporation
First Edition, January 1983 Second Edition, December 1983 Copyright © 1983 by Digital Equipment Corporation All Rights Reserved 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. Printed in U.S.A.
CONTENTS Page CHAPTER 1 INTRODUCTION 1.1 1.4 MANUAL SCOPE ................................................................................................... VAX-ll/730 DIAGNOSTIC SYSTEM STRUCTURE ......................................... DIAGNOSTIC STRATEGy .................................................................................... VAX-ll/730 REMOTE DIAGNOSIS OPTION .................................................... CHAPTER 2 CONSOLE SUBSYSTEM 2.1 2.2 2.2.1 2.2.2 2.2.3 2.3 2.4 2.5 2.5.
CHAPTER 4 MICRODIAGNOSTICS 4.1 4.2 4.3 4.4 INTRODUCTION .................................................................................................... LOADING THE MICMON ..................................................................................... MICRODIAGNOSTIC MONITOR COMMANDS ............................................... MICRODIAGNOSTIC ERRORS ............................................................................ CHAPTER 5 VAX-ll/730 DIAGNOSTIC SUPERVISOR AND LOAD PATH 5.1 5.
CHAPTER 8 BUILDING AND UPDATING THE SYSTEM DISK DIAGNOSTIC AREA 8.1 8.2 8.2.1 8.2.2 INTRODUCTION .................................................................................................... BUILDING AND UPDATING THE DIAGNOSTIC AREA ............................... Building and Updating the Diagnostic Area with the COpy Command ........ Building and Updating the Diagnostic Area with DUCT ................................ APPENDIX A VAX-ll/730 INTERNAL PROCESSOR REGISTERS ..........................
5-1 5-2 Diagnostic Programs on TU58 #39 .......................................................................... 5-5 Diagnostic Programs on TU58 #44 .......................................................................... 5-5 A-I A-2 Internal Processor Registers ..................................................................................... A-I Machine-Dependent Internal Registers .................................................................... A-2 EXAMPLES Example No.
7-11 7-12 7-13 7-14 7-15 8-1 Printout of the MENU Mode in Which Choice C Was Selected from the Main Menu ........................................................................................................ Printout of the MENU Mode in Which Choice D Was Selected from the Main Menu ........................................................................................................ Printout of a MENU Mode Successful Testing Sequence in Which Choice D Was Selected from the Test Menu .................
CHAPTER 1 INTRODUCTION 1.1 MANUAL SCOPE This manual describes the use of the VAX diagnostic system with the VAX-I 1/730 computer system. It covers the following topics: • Console commands • • • • • • Cold and warm start functions Microdiagnostics Diagnostic supervisor Level 4 macrodiagnostics Customer runnable diagnostics System disk diagnostic area This manual covers only details that pertain to the diagnostic system for the VAX-II /730 computer system.
These four levels of documentation form a progression from general to specific. The general level being the VAX Diagnostic System User's Guide and the specific being the Diagnostic Program Listings. To apply the YAX diagnostic system effectively, the user should become familiar with each documentation level. The VAX Diagnostic System User's Guide contains stable information that applies across all YAX computer systems.
1.
The VAX-II /730 diagnostic system provides flexibility concerning the load paths and execution control of different program levels. For example, the diagnostic supervisor and level 2 and level 3 programs can be loaded from either the console load media (TU58 tape drive) or from the system disk. If the primary mass storage load path does not work properly, the TU58 can load diagnostic programs which would help to repair the load path problem. (Refer to Chapter 5.
CHAPTER 2 CONSOLE SUBSYSTEM 2.1 INTRODUCTION The VAX-II /730 console subsystem is an important diagnostic tool.
Table 2-1 CPU Halt Codes and Halt Conditions Code Halt Conditions 00 Halt command - given by the operator while the processor is in the Console mode. 01 Self-test was successful. 02 CPU Halt - operator typed CTRLjP while the machine was in the Program mode. 03 Typed by the console on a power fail restart. Does not appear in the halt message. 04 Invalid interrupt stack (IS) or unable to read system control block (SCB). 05 CPU double error.
When the CPU enters the console mode, it prints on the console terminal: • A question mark followed by a two-digit halt code (Table 2-1). • The address contained in the program counter (PC). • The console prompt symbol, »>. For example: P ! CTRL/P typed at the console terminal ?02 PC=nnnnnnnn ! Halt code followed by the PC address ») ! Console prompt 2.2 FRONT PANEL CONTROLS AND INDICATORS The front panel of the VAX-l 1/730 has two switches and four indicator lights.
2.2.2 AUTO/RESTART Switch This three-position switch controls the machine in a power-up sequence, power restoration and software crash. The three positions of the AUTO/RESTART switch and the functions of each are shown in Table 2-3. Table 2-3 The Functions of the Three-Position AUTO/RESTART Switch Position Function OFF The system halts and prints the console prompt (»» after loading the microcode or executing a HALT instruction.
2.3 POWER-UP SELF-TEST Upon initial power-up, the VAX-ll/730 console subsystem system goes through a sequence of events that is shown in Figure 2-1. If the self-enable switch (SWl) on E47 of the WCS module (M8394 slot 3) is OFF (high), the console microprocessor performs a test of the + 15 V and -15 V power and the PROM resident self-test. If SW 1 is ON (low) the PROM resident self-test is bypassed.
During the self-test the word "CONVxyz" is printed on the console terminal. The "xyz" designation will vary according to the version of the console program. Each letter and digit of this word is a series of subtest completion flags. One letter or digit of the word "CONVxyz" is printed between each subtest and the last two digits are printed at the end of the test (Example 2-1).
• RAM March Test - The RAM march test writes a background of Os, then marches a 1 through it. This leaves a background of Is through which a 0 is marched. This subtest has a delay inserted in it so that the RAM refresh hardware is also tested. Failing Test Printout: Expected XXXXXXXX Received XXXXXXXX 2.
The steps indicated in Example 2-1 are outlined below: o o e o These are console self-test flags. This is the console program release version. The boot block instructions are executed by the console microprocessor. They load the file CONSOL.EXE from the console tape cartridge in the TU58 drive unit into the CPU writeable control store (WCS). The console prompt (»» is printed. The indirect command file POWER.CMD is accessed on the cartridge. The commands within this file are performed. a.
The indirect command file CODEOl.CMD is one of four possible command files that can load selected microcode into the CPU WCS. The file used depends upon the presence of the FPA and IDC. This presence is determined by a value passed to the console microprocessor from the execution of the microcode at OEOO (POWER. CPU). The values passed to the console microprocessor to indicate which command file is used are shown below. Value Returned FPA IDC File Used o o CODEOO.CMD CODEOl.CMD CODE02.CMD CODE03.
Table 2-5 Control Characters for the Console I/O Mode Control Character Function CTRL/P (program I/O mode) Aborts the current command, prints halt message, and returns the console to the console I/O mode idle loop The console prints: p ?02PC=nnnnnnnnn ») !CTRL/P. !Halt message. !Console idle !loop.
2.5.3 CONTINUE Command The CONTINUE command is: C(CR) If the CPU clock is running, the CONTINUE command restarts execution of a halted program at the address currently in the PC. If the CPU clock is not running because of a microcode break point or the CPU is in the microstep mode, the CONTINUE command restarts the clock and the console remains in the console I/O mode. 2.5.
Table 2-6 EXAMINE and DEPOSIT Qualifiers and Definitions Qualifier Definitions Data Length Qualifers /B /W /L Byte Word Longword Repetition Qualifiers /N: Executes the EXAMINE and DEPOSIT + 1 times (»>E/P/L/N:3 1000), and examines the 4-hexadecimal address in physical address space, starting in location 1000 Address Space Qualifiers /V Virtual Address: This does not work unless mapping is set up for the virtual address reference also.
Following another virtual or physical EXAMINE or DEPOSIT, the default is the sum of the address from the last EXAMINE/DEPOSIT plus the data length from the last EXAMINE/DEPOSIT. Typing a plus sign (+) or minus sign (-) for
(for DEPOSIT only) gets this default. Following another IPR or GPR EXAMINE/DEPOSIT, the default is the sum of the address from the last EXAMINE/DEPOSIT plus one.2.5.6 HALT Command The HALT command is: H The HALT command does not halt the CPU. HALT causes the console to print the contents of the PC when the CPU is already halted (CTRL/P is used to halt the CPU). 2.5.7 Indirect Command The indirect command is: @ The @ command loads and executes the indirect command file specified on the power-up sequence or by the operator. 2.5.
Table 2-7 The LOAD Qualifiers and Definitions Qualifier Definitions IS:
This start qualifier specifies a starting address for the load. If this qualifier is not given, then the console starts loading at address O. IP This qualifier forces physical main memory to be the destination of the load. IU This qualifier forces the console microprocessor memory to be the destination of the load. IC This qualifier forces the WCS to be the destination of the load.Examples of the MICROSTEP command are shown below. »)M 2
2.5.12 REPEAT Command The REPEAT command is: R(space>(console command>(CR> The REPEA T command causes the console to repeatedly execute the (either DEPOSIT, EXAMINE or INITIALIZE) specified until execution is terminated by CTRL/C, CTRL/P or the BREAK key. 2.5.13 START Command The START command is: S[(space>(address>](CR> or S/C(space>(address>(CR> The START command starts execution of a program that is loaded into memory (see LOAD command).
The operating state of the machine is altered whether or not the program is found. If the program is not found, the console subsystem returns to the console 1/0 mode to reload itself from the console tape. If the program is found, the console subsystem loads that program into memory and transfers control to it, as shown in Example 2-2. »)T CONVxyz ?01 FILE NOT FOUND DD1:ENSAB.EXE Loads and starts AUTO Mode customer runnable diagnostics. Performs the self-test. The AUTO Mode CRD file was not found on DD1.
CHAPTER 3 COLD AND WARM START FUNCTIONS 3.
o BOOT OPERATING SYSTEM "»> B DxO" PRINT "SYSTEM BOOT FAILED" • BOOT DIAGNOSTIC SUPERVISOR "»> B Sx1" OR "»> B SxO" PRINT "ATTEMPTING SYSTEM BOOT" HALT CPU IN CONSOLE I/O MODE WAIT LOOP "»>" YES INITIALIZE CPU, LOAD ADDRESS OF GOOD 64KB OF MEMORY INTO SP LOAD GENERAL REGISTERS RO-R5 & SP LOAD AND START VMB.EXE INTO MEMORY STARTING AT 64KB+200 Figure 3-1 LOAD AND START SYSBOOT.EXE LOAD AND START DIAGBOOT.EXE OPERATING SYSTEM DIAGNOSTIC SUPERVISOR "$" "DS>" • XXXBOO.
As shown in Figure 3-1, the sequence of events is essentially the same for all actions initiating a cold start. The sequence of events for each action is outlined in the following paragraphs. o o e Power-Up Cold Start Sequence - A power-up cold start of the operating system causes the console subsystem to perform the following sequence of events: • Execute the self-test, load the console program (Chapter 2), and check the setting of the AUTO/RESTART switch.
o e G AUTO/RESTART Switch Set to BOOT Sequence - Setting the AUTO/RESTART switch to the BOOT position, while the CPU is in the console I/O mode wait loop, causes the console subsystem to perform the following sequence of events: • Print the message ATTEMPTING SYSTEM BOOT on the console terminal. • Examine the cold start flag. If the flag is set, indicating a cold start has previously been attempted, the message SYSTEM BOOT FAILED is printed on the console terminal.
The instructions contained within these indirect command files causes the console subsystem to perform the following sequence of events (Figure 3-1): • Initialize the CPU to a known state and load the address of the first 64K bytes of good memory plus 200, which was located by the console program, into the stack pointer (SP which is GPR E). • Load parameters into the general registers RO through R5.
Table 3-1 Register Parameters Loaded into the General Registers at BOOT (Cont) Parameters R4 R5 Cold start block logical block number (LBN) <09:00> o (hex) 1 2 3 4 5 6 7 8 9 3.2.1.1 Description (hex) (hex) (hex) (hex) (hex) (hex) (hex) (hex) (hex) Software cold start control flags Conversational cold start Debug Initial Breakpoint Boot block Diagnostic monitor cold start Bootstrap breakpoint Image header Memory test inhibit File name (query) Halt before transfer VMB.
3.3 WARM START (REST ART) Warm start or restart refers to restarting the operating system without reloading it into memory. When the console subsystem gains control of the VAX-ll/730 following a CPU halt or power restoration, it performs the sequence of events shown in Figure 3-2. The sequence of events performed by the console subsystem for warm starting the operating system is outlined in the following list. The console subsystem: 1.
3. Checks for the presence of the restart parameter block (RPB) in memory. If the RPB is not found, the warm start fails. If the RPB is found, then the console subsystem checks to see if it is valid (see Section 3.3.1.) If the RPB is not valid warm start fails. If the RPB is valid the console terminal loads the SP with the address of the RPB plus X200. 4. Loads the AP (GPR C) with a value that indicates the cause of the warm start. 5.
CHAPTER 4 MICRODIAGNOSTICS 4.1 INTRODUCTION Microdiagnostics are the lowest level of diagnostics (level 5) in the VAX-II /730 diagnostic system. These diagnostics test the system at the console microprocessor and CPU microcode levels, and should be executed when higher level diagnostics (levels 4, 3, 2, 2R and 1) are unable to load or execute. They are the only level of diagnostics that provide for call-out of faulty module(s) for repair.
The ENKCx group executes from the WCS RAM (which writes over any system microcode that may be loaded) and uses the CPU micromachine to test the parts of the system listed in Table 4-2. NOTE There is no microdiagnostic for the DMF32 (COMBO board), as it is a UNIBUS device. The DMF32 contains a ROM board hard-core self-test which is evoked by either the power-up self-test (Chapter 2) or by commands from the execution of macrodiagnostics (Chapter 5).
Method 1 loads the MICMON prior to loading the system microcode. Perform the procedures below: 1. Insert TU58 tape cartridge #36 (labeled 11725/730 MICRODIAG) into TU58 tape drive 1. CAUTION Make sure that the stabilizer foot is extended from the bottom of the system cabinet before the CPU mounting box is extended. 2. Set the AUTO-RESTART/BOOT switch to the OFF position. 3. Turn the keyswitch to the LOCAL position.
3. Turn the keyswitch to the LOCAL position. The VAX-ll/730 powers up into the console I/O mode and the console terminal produces a printout as shown in Example 4-2. CONSOLE VERSION XX.nn »)@POWER.CMD »)L/C CONSLE.CPU »)L/C/S:0800 MMIE.CPU »)L/C/S:OEOO POWER.CPU »)S/C OB »)W »)@CODE01.CMD »)L/C/S:OEOO FP.CPU »)L/C/S:1AOO BITFLD.CPU »)L/C/S:1DOO CM.CPU »)L/C/S:2200 BASIC.CPU »)L/C/S:3BOO QUEUE.CPU »)L/C/S:4000 IDC.
4.3 MICRODIAGNOSTIC MONITOR COMMANDS The following is a list of MICMON commands to execute the microdiagnostics: DIRECTORY T/E REPEAT DIAGNOSE START RETURN CONTINUE LOAD SHOW S/U INITIALIZE DEPOSIT /EXAMINE SET/CLEAR These commands are defined and illustrated with examples in Appendix B. 4.4 MICRODIAGNOSTIC ERRORS Microdiagnostic errors are detected and error messages are displayed under two conditions: • Any time the CPU is under the control of the MICMON.
The xx in the error message shown in Example 4-4 is the hex error code shown in Table 4-3. The microdiagnostic error printout in Example 4-5 is explained below: o Diagnostic section in which an error occurred o Test number within that diagnostic section e o e o o o Error number. Within a particular test, several pieces of hardware may be tested, each by a subtest. The error number identifies the unique subtest that failed.
CHAPTER 5 VAX-ll/730 DIAGNOSTIC SUPERVISOR AND LOAD PATH 5.1 INTRODUCTION The VAX-II /730 diagnostic supervisor may be loaded off-line from the diagnostic distribution disk, system disk, or from the TU58 tape drive. If the user disk drive is not used by VMS, the supervisor is loaded from the distribution disk while the system is operating in the user mode. However, if the user disk drive is unavailable, the supervisor is loaded from the system disk.
5.2. t Loading the Supervisor Off-Line from the Diagnostic Distribution Disk The diagnostic supervisor is loaded off-line from the diagnostic distribution disk by booting the supervisor from that disk. To boot the diagnostic supervisor from the diagnostic distribution disk perform the following procedures: 1. Load the diagnostic distribution disk labeled VAX 725/730 CMPLT DIAG into the removable media disk drive and place the drive on line (LOAD button in). 2.
The console responds by printing a boot message and the diagnostic supervisor prompt (OS» as shown in Example 5-2. The OS> prompt indicates the diagnostic supervisor is loaded and executing. »)B SQO »)@DD1:SQOBOO.CMD »)1 »)D/G/L 0 00A80003 »)D/G 1 3 »)D/G 2 3FB86 »)D/G 3 0 »)D/G 4 0 »)D/G 5 10 »)E SP G OOOOOOOE 00000200 »)L/P/S:@ VMB.EXE »)S @ DIAGNOSTIC DS) Example 5-2 5.2.3 SUPERVISOR. ZZ-ENSAA-x.
5.2.4 Loading the Supervisor On-Line from the System Disk To load and execute the diagnostic supervisor in the on-line mode (with VMS) from the system disk, perform the following procedures: I. In response to the VMS prompt, type the following command to set default to the directory containing the diagnostic supervisor program (ENSAA.EXE): S SET DEFAULT SYSSMAINTENANCE 2.
Table 5-1 Section Program ENRKA.EXE ENRKA.HLP EVQDQ.EXE EVRAA.EXE EVRAA.HLP EVRAD.EXE EVRAD.HLP EVRGA.EXE EVRGA.HLP IDC Subsystem Functional Diagnostic Help file for the ENRKA Diagnostic IDC Standalone Driver VAX-II Disk Reliability Diagnostic Help file for the EVRAA Program VAX-II Disk Drive Functional Diagnostic Help file for the EVRAD Program RM80 Formatter Help file for EVRGA Program Table 5-2 5.3.1 Diagnostic Programs on TU58 #39 Diagnostic Programs on TU58 #44 Section Program EVRLA.
If EYKAA executes successfuly, at the end of each 16 passes the console produces a printout as shown below and rings the terminal bell. EVKAA Vn.n PASS #nn DONE! EVKAA Vn.n PASS #nn DONE! EVKAA Vn.n PASS #nn DONE! This program continues to execute and produce the above printout until a CTRL/P is typed. At that time the system returns to the console I/O mode and prints the console prompt, »>. If the level 4 diagnostic executes without error, the diagnostic supervisor (ENSAA.
c. d. e. Remove TU58 tape cartridge #35 from TU58 tape drive o. Insert TU58 tape cartridge #39, labeled VAX 725/730 IDe DIAG, into TU58 tape drive o. Use the RUN command to execute the diagnostic program ENRKA.EXE: DS>RUN ENRKA 7. For the VAX-II /730 system with the UDA50 disk controller, perform the following steps to define the hardware configuration and execute EVRLA: a.
b. Use one of the following commands to select the disk device for testing: DS>SELECT DUAO,DJAO DS>SELECT DJAO,DJA1 DS>SELECT DUAO DS>SELECT DJAO c. Remove TU58 tape cartridge #35 from TU58 tape drive O. d. Insert the TU58 tape cartridge #44, labeled VAX UDA50 SUBSYSTEMS, into TU58 tape drive O. e. Use the RUN command to execute the diagnostic program EVRLA.EXE: DS>RUN EVRLA 8.
The autosizer program (EVSBA.EXE) sizes the system on which it is executed (under the diagnostic supervisor in the console mode) and passes the system configuration to the diagnostic supervisor with a single command. To execute the autosizer, perform the following procedures: 1.
2. Type A TT ACH to the COMMAND? prompt to actually build the database in the diagnostic supervisor. 3. Type EXIT to the COMMAND? prompt to -exit the autosizer program. The autosizer prints the completion message shown below (if no errors were encountered) on exiting. It then returns console control to the diagnostic supervisor, OS>. COMMAND? EXIT . . . . . . . . • . . End of run, 0 errors detected, pass count is 1, time is dd-mmm-yyyy HH:MM:SS DS) 4. Select the devices to be tested.
CHAPTER 6 EXECUTING THE LEVEL 4 DIAGNOSTIC PROGRAM 6.1 LOADING AND EXECUTING THE LEVEL 4 DIAGNOSTIC PROGRAM Only one level 4 diagnostic program applies to the VAX-l 1/730 - EVKAA, a hardcore instruction test.
6.1.1 Loading EVKAA from the TU58 Tape Cartridge The level 4 diagnostic EVKAA is loaded and executed with the console command language as shown in the following steps: #11, I. Insert the TU58 tape cartridge drive o. 2. At the console prompt, »>, type the following commands to load and execute EVKAA: »)1 labeled VAX 11 HARDCORE INSTR, into the TU58 Initializes the CPU. Zero memory location FEOO. Loads the diagnostic into memory. »)D/P/L FEOO 0 »)L/P/S:O DDO:EVKAA.
IfEVKAA does not execute successfully, it prints the error message shown below and returns control to the console I/O mode. ???ERROR TEST #nn, SUBTEST #nn (instruction) FAILED (one line description of failure) EXPECTED DATA: XXXXXXXX RECEIVED DATA: XXXXXXXX ?06 00009301 ») 6.2 EVKAA ERROR INTERPRETATION AND LOOP CONTROL When EYKAA detects an error and the halt code is 06, it indicates that the processor executed a HALT instruction at the error.
Example 6-2 shows an EXAMINE and DEPOSIT to the location that contains the HALT instruction. »)E/P/B 9300 P 00009300 »)D/P/B9300 01 Examines location 9300. 00 Deposits 01 in the byte at. location 9300. Continue. The program should loop on error. »)C Example 6-2 Level 4 Diagnostic Program Set Up to Loop on Hard Error However, if the error is intermittent, the program may progress out of the loop on the first success.
CHAPTER 7 CUSTOMER RUNNABLE DIAGNOSTICS 7.1 INTRODUCTION Customer runnable diagnostics or CRD is a special control program to simplify the execution of microand macrodiagnostics in the VAX-II diagnostic system on the VAX-l1/730 system. The CRD package operates in two modes: AUTO and MENU. In the AUTO mode, OFF-LINE bottomup testing is performed on the system without user intervention.
VAX-ll/730 SBB System • VAX-ll/730 CPU Cluster with 1 Mb of Memory • Disk Controller (UDA50) • Dual TU58 Tape Drive • Console Terminal • One of the following Disk Drive Configurations RA60 for Drive 1 and either RA60, RA80 or RA81 for Drive 0 RA60, RA80, RA81 for Drive 0 • TU58 #34, VAX 11725/730 CONSOLE Tape Cartridge • TU58 #36, VAX 11725/730 MICRODIAG Tape Cartridge • One of the following Diagnostic Distribution Medias RA60 # 1, VAX 725/730 CMPLT DIAG Disk Cartridge for the System with an
VAX-ll/730 SBB System 1. Tests the CPU, memory and FPA with microdiagnostics. 2. Tests the CPU with level 4 diagnostics. 3. Boots the diagnostic supervisor from the disk drive (0 or 1). 4. Tests the DMF32 and the UDA50 disk drive with macrodiagnostics. Once AUTO mode is invoked, device testing is completed without user intervention in approximately 15 minutes. An exception to this would be when the system is improperly set up.
7.3.1 AUTO Mode Evocation AUTO mode is invoked after system preparation is performed. The system is prepared for testing and AUTO mode is invoked by performing the following procedures: 1. Insert TU58 tape cartridge #34, labeled VAX 11725/730 CONSOLE, into TU58 tape drive 1. 2. Insert TU58 tape cartridge #36, labeled 11725/730 MICRODIAG, into TU58 tape drive 3. Insert the diagnostic distribution disk cartridge into the- user disk drive. Depress the LOAD button on the disk drive to place it on-line.
If no errors are encountered, the console terminal produces a printout similar to that in Example 7-2. **** BEGIN VAX-11/730,725 AUTO TEST **** VERSION X.
3. The system disk drive is WRITE PROTECTed. 4. The system disk drive is off-line (LOAD button out). 5. The diagnostic tape in the TU58 tape drive has missing or corrupted diagnostic program files. After printing warning messages, AUTO mode handles each of the above situations differently. AUTO mode pauses for the first two situations above to allow the user to properly set up the disk drive (Example 7-1).
**** BEGIN VAX-11/730,725 AUTO TEST **** VERSION x.
7.3.3 AUTO Mode Errors Errors detected during AUTO mode cause an error message to be printed and the current diagnostic test to be aborted. Also, depending on which diagnostic test detected the error, AUTO mode aborts. If errors are· detected during the microdiagnostic or level 4 diagnostic testing, the program that detected the error along with the remaining test programs are aborted (Example 7-6). Also, if microdiagnostics attempt to test a device that is missing, other than the FPA, AUTO mode is aborted.
**** BEGIN VAX-11/730,725 AUTO TEST **** VERSION x.
7.4.1 MENU Mode Evocation MENU mode is invoked after the "base" system is fully prepared. Prepare the "base" system by performing the following steps: 1. Insert TU58 tape cartridge #34, labeled VAX 11725/730 CONSOLE, into the TU58 tape drive 1. 2. Insert TU58 tape cartridge #36, labeled 11725/730 MICRODIAG, into the TU58 tape drive O. 3. Insert the diagnostic distribution disk cartridge into the disk drive. Depress the LOAD button on the disk drive to place it on-line.
b. Type CRD in response to the supervisor prompt as shown below: DS>CRD Whichever method is used to evoke CRD MENU mode, user control is passed to the Main Menu which produces a printout similar to Example 7-8.
Choice A: If choice A is selected, MENU mode is aborted and user control is returned to the console I/O mode (Exam pIe 7-9).
Choice C: If choice C is selected, MENU Mode prints a list of the necessary system preparations required to test the SUPPORTED devices on the system (Example 7-11). After this list is printed, the Main Menu is printed again. Type one of the above (for example, A), and press RETURN, Enter MAIN MENU choice: C Hardware: Preparation: DMF32A, DMF32P, DMF32S, KA730, RK611 1. No Hardware Preparation required. Hardware: Preparation: RL02, RK07 1. Insert Disk cartridge in drive. Disk may contain useable data. 2.
Type one of the above (for example, A), and press RETURN, Enter MAIN MENU choice: D TEST MENU A1 KA730 CPU KAO 81 82 83 DMF32S DMF32A DMF32P COMM. COMM. COMM. XGAO TXA LCA C1 C2 C3 RL02 RaO RL02 DISK DISK DISK DLAO DQAO DQA1 D1 TEST ALL of the above suppor ,ted hardware Type one of the above (for example, start testing.
Type one of the above (for example) A1») and press RETURN to start testing. Enter TEST MENU choice: D1 Type the CTRL key and the C key (together) at any time to interrupt Functional Test ................. .
Type one of the above (for example, A1), and press RETURN to start testing. Enter TEST MENU choice: D1 Type the CTRL key and the C key (together) at any time to interrupt Functional Test ................. .
(CONTROL key and C typed together) CONTROL-MENU A Exit Menu Test B = Abort the current process} and return to MAIN MENU C = Resume the process interrupted by the CONTROL-C Type one of RETURN. the above (for example) A)} and press Enter CONTROL-C MENU choice: Example 7-15 Printout of an Unsuccessful MENU Mode Testing Sequence in Which Choice Dl Was Selected from the Test Menu 7.4.
CHAPTER 8 BUILDING AND UPDATING THE SYSTEM DISK DIAGNOSTIC AREA 8.1 INTRODUCTION The VAX-I 1/730 is shipped with one of two types of diagnostic distribution media. The media is either a disk cartridge or magnetic tape, depending on the system configuration. This FILES-II structured diagnostic distribution media is labeled VAX 11725/730 CMPLT DIAG. This media contains all microdiagnostic programs appropriate to the VAX-II /730.
3. Place the drive containing the diagnostic distribution media on-line by depressing the LOAD button on that drive. 4. At the $ prompt, type the following command to mount the diagnostic distribution cartridge: $MOUNT ddAn: CRDPACK where "dd" is the device type and "n" is the drive number (for example, DUAl is an RA60 disk drive in drive I; MSAO is the TU80 magnetic tape in drive 0). 5.
5. Type the following command at the $ prompt, to execute DUCT from the distribution media: $RUN ddAn:[SYSMAINT1DUCT.EXE where "dd" is the device type and "n" is the drive number (e.g. DUA 1 is an RA60 disk drive in drive 1 and MSAO is the TU80 magnetic tape in drive 0) where the diagnostic media is mounted. 6. When DUCT prints the menu below shown in Example 8-1, type the HELP command and follow the instructions to either build or update the system diagnostic area.
APPENDIX A VAX-ll/730 REGISTERS Table A-I Internal Processor Registers Address Hex Dec Mnemonic 0 1 2 3 4 8 9 A B C D 10 11 12 13 14 15 18 19 lA IB lC ID IE IF 0 1 2 3 4 8 9 10 11 12 13 16 17 18 19 20 21 24 25 26 27 28 29 30 31 KSP ESP SSP USP ISP POBR POLR PIBR PILR SBR SLR PCBB SCBB IPL ASTL SIRR SISR ICCS NICR ICR TODR CSRS CSRD CSTS CSTD 20 21 22 23 26 28 37 38 39 3A 3D 3E 32 33 34 35 38 40 55 56 57 58 61 62 RXCS RXDB TXCS TXDB MCESR ACCS WO RO * = = = Access WO WO RO RO WO RO WO RO WO MAPE
Table A-2 Machine-Dependent Internal Registers Address Hex Dec Register Mapping o o 1 2 3 4 1 2 3 Processor Status Longword CPU Microprogram Counter (UPC) Memory Controller CSR 1 Register Memory Controller CSR 2 Register Set Breakpoint @ Microaddress Enable/Disable WCS Control Store Parity WCS Control Store Register CPU Scratch Pad Memory (WR3:WRO) CPU Quotient Register CPU Scratch Pad Memory (Local Store) 5 6 13: 10 20 IFF: 100 4 5 6 19: 16 32 511 :256 A-2
APPENDIX B MICRODIAGNOSTIC MONITOR COMMANDS The following are the commands used with the MICMON. DIR[ECTORY] - Example: The directory of the TU58 being used (DDl or 000) is printed at the console terminal. MIC>DIR RET[URN] - The microprocessor program counter is forced to zero and the power-up routine is started again. If a console cassette (CONSOLE) is present, the system will power-up into the console I/O mode and the console terminal prints the prompt, »>.
This command loads microdiagnostic section ENKBC from the microcassette. INIT[IALIZE] - Initializes a WCS section. This command must be issued after a section is loaded by the LD command before tests are executed. It is automatically executed in a DI SE or DI command. Example: MIC>LD EHKBC MIC>IHIT X/C or X/U - Allows the remote diagnostic terminal to downline load a file into the console microprocessor memory (C for console memory) or WCS RAM (U for microcode).
Run test number 8 through to the end of the section that is currently in RAM memory. PASS - This keyword is used in conjunction with the TEST keyword to indicate the number of times a test(s) is performed. Example: MIC>DI SE EHKBD TE 2 5 PA 3 Load section ENKBD from the cassette into RAM memory and execute tests 2 through 5 three times. Example: MIC>DI TE 2 5 PA -1 Run tests 2 through 5 of the section that is currently in RAM memory and repeat forever (until interrupted by CTRL/C or CTRL/P).
NOTE HALT has a higher priority than LOOP. Thus, if both are set, halt on error occurs first. Example: NER - MIC>SE LO No error reports. SETting this flag causes the MICMON to skip the printout of error reporting. Example: MIC>SE NE BELL - Bell on error. SETting this flag causes the MICMON to ring the terminal bell each time an error is reported. Example: MIC>SE BE SER - Enable single bit errors to be reported as normal errors. SETting this flag causes the MICMON to print single bit errors.
STEP - Set single step. SETting this flag causes the MICMON to single step the CPU n times. If no valud is given, the CPU single steps once for each time the space bar is typed. Any other character type causes MICMON to exit to the command level (MIC». NOTE The character typed to exit to the command level becomes the first character of the next command. If a clean start is desired for the next command line, a CTRLjC must be typed to exit to the command mode.
EX[AMINE]/DE[POSIT] - The EXAMINE/DEPOSIT commands are used to read/write data from/ to various registers or memory locations. The following modifiers point to the area being accessed. EX
PA[TT]*# - Read data from the IDC ECC pattern register. Example: MIC)EX PA DB[UF]# - Examines the contents of the IDC Pattern Register (read only). Read/write data from/to the IDC's data buffer. Examples: MIC)EX DB - Examines the longword (four bytes) of the current data buffer (A or B) at the current data buffer address. The address is then incremented by four. MIC)DE DB 18FFCCA 1 - The value 18FFCCA 1 is deposited in the current data buffer at the current address.
MC[T]# - Read/write data from/to the memory controller's CSR registers. Examples: MIC)EX MC 2 - Examine data in MCT's CSR register 2. MIC)DE MC 1 2COOOOOOO TB# - Deposit data 2COOOOOO into MCT's CSR register 1. Read/write data from/to the memory controller's translation buffer. Examples: MIC)EX TB 5 - Read data from MCT's translation buffer 5. MIC)DE TB 10 7100 IC[SR] - Write data 7100 into MCT's translation buffer 10. Read/write data from/to the IDC's CSR register.
Reader's Comments VAX-11/730 Diagnostic Overview Manual Your comments and suggestions will help us in our continuous effort to improve the quality and usefulness of our publications.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Fold H e r e - - - - - - - - - - - - - - - - - - - - - _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 00 Not Tear - Fold Here and Staple - - - - - - - - - - - - - - - - ~DmDDmDTM III II I BUSINESS REPLY MAIL FIRST CLASS PERMIT NO.33 MA YNARD. MA.
Digital Equipment Corporation.
