Text preview for : Series37_Diagnostic_Specifications_May84.pdf part of HP Series37 Diagnostic Specifications May84 HP 3000 series37 Series37_Diagnostic_Specifications_May84.pdf
Back to : Series37_Diagnostic_Speci | Home
PTSDIAG External Specifications ]
PTSDIAG External Specifications
Mon, May 7, 1984, 3:23 PM
1 PRODUCT IDENTIFCA TION
1.1 Identification
Name: PIC - TIC - SIMB Diagnostic
Mnemonic: PTSDIAG
Product Number:
1.2 Abstract
PTSDIAG is a diagnostic program which verfies the 51MB of the HP3000 Mighty Mouse System. The
program is part of the Diagnostic/Utility System (DUS) for the Mighty Mouse System or Series 37.
The diagnostic will use both PICs and Tics to heavily load the backplane using DMA transfers to bring
out board contingencies. The diagnostic was built from sections of TICDIAG and PICDIAG.
1.3 Project Personnel
Laurie Schoenbaum
2 PRODUCT SPECIFICATIONS
2.1 Product Overview
The PTSDIAG is written in SPL/3000. It is run under DUS (Diagnostic/Utility System).
The user is prompted for path and channel information as well as the memory size and the number of
repetitions. DMA transfen are executed io load the backplane with operations. A transfer between
two PICs and a transfer from a TIC using loopback completes .one pass.
If data does not transfer properly or an error occurs in the transfer then an error will be displayed in
a clear and understandable manner.
Error messages may be suppressed or routed to the system printer.
2.2 User Definition
Manufacturing and iab personnei are the primary uSers of PTSDIAG. Some knowledge of the Mighty
Mouse system is expected to run the test and interpret the results.
The test is used to increase system reliability and detect backplane contentions.
PTSDIAG 1
2.3 Product Environment
2.3.1 Hardware Reqirements and Restrictions
The following hardware requirements must be met to run PTSDIAG:
1) A minimum configuration HP3000 Mighty Mouse system
2) The memory board used must work wen enough to initiate PSTDIAG
3) An HPIB tape drive and a functioning PIC as the coldload path to load DUS
4) At least one additional PIC
5) A system console and a functioning TIC in slot 1 of the main box for user interaction and
operation
6) An HPIB cable to connect the device PIC to the controller PIC
7) Optional: One or two additional PICs for busy channels
2.3.2 Software Reqirements and Restrictions
Diagnostic/Utility System Tape
2.4 User Documentation Reqirements
The following documents may be used as reference for additional information:
* PTSDIAG source listing
'" PICDIAG ES and source listing
'" TICDIAG ES and source listing
'" DMAEX 37 source listing
* HP300 Hardware I/O Subsystem ERS
* HP3000 Mighty Mouse Hardware Design Document
3 Detailed Functional Specifications
3.1 Individual Function Desriptions
The primary function of PTSDIAG is to keep the 51MB backplane loaded with traffic from both the
PIC and the TIC and to draw out problems with board interactions and timing dependencies. The test
combines Step 45 of PICDIAG and the Diagnostic Loopback test of TICDIAG. A minimum test con-
sists of two PICs, a TIC, a memory, and a CPU. One PIC is the controller PIC and the other PIC is the
device PIC. The cold load device may be attached to either PIC. The system printer may only be at-
tachd to the PIC chosen as the controller. The cold load device and system printer may also be at-
tached to the PICs chosen as busy PICs if there are more than two PICs in the system.
DUS expects the system console to be attached to channel I, PORT 0, therefore the port numben
chosen in the test are ports 1 thru 7.
3.1.1 Test Control
The operator is prompted for test configuration information, the memory size, and the number of
repetitions. The diagnostic may also be reconfigured for error pause and suppression of end of
program pa use.
PTSDIAG 2
3.1.2 Error Handling
Error messages may be suppressed from being displayed or routed to a printer. The printer will be
configured into the system when DUS is loaded or one may be added by using the appropriate com-
mand in MANAGER.
3.1.3 System Configurations
The system used in the test may be configured in different ways if there is an extender box used.
With an extender box all four PICs may be used and an additional memory may be added. With only
the main box, there is only one possible configuration.
The tape drive may be attached to either PIC. The system printer may only be attached to the PIC ac-
ting as the controller.
3.2 User Interface
All input to PTSDIAG is done through the system console. All responses made to the diagnostic or
DUS prompts should be followed by pressing the RETURN key.
PTSDIAG 3
Basic Procedu re Overview -
begin
I
I
V
3.Z.1 Coldload DUS
I
I
V
3.2.2 invoke Diagnostic
I
I
V
3.Z.3 Configure Diagnostic
I
I
V
Diagnostic Executes
I
I
V
3.Z.4 end of Diagnostic and return to DUS
3.2.1 How to Coldload DUS
a) Perform MPE shutdown to logoff every user, if applicable
b) Run console self -test by pressing TEST on the keyboard
c) Fully reset console by pressing RESET TERMINAL key rapidly twice
d) Install a DUS tape on the tape coldload device
e) Power-on the Mighty Mouse system by turning the keyswitch to the NORMAL position for the
system
f) The MM Microdiagnostics will run followed by a prompt to load DUS
Type 'H' for HELP -->
User should respond with 'L' followed by the Channel II, Device II of the Cold load device.
3.2.2 Invoke Diagnostic
The Diagnostic/Utility System should respond after load with a welcome message and prompt:
DIAGNOSTIC/UTILITY SYSTEM (REVISION XX.XX)
ENTER YOUR PROGRAM NAME (TYPE HELP FOR PROGRAM INFORMATION)
Respond to the DUS prompt with:
PTSDIAG
PTSDIAG 4
PTSDIAG will load and execute displaying the following greeting:
HP3000 Mighty Mouse PIC-TIC SIMB Diagnostic - (PTSDIAG NN.NN xx/u/u)
3.1.3 System and Diagnostic Configuration
PTSDIAG prompts the user for all information needed to run the test and to configure the diagnostic.
1) PTSDIAG prompts the user for PIC Channel information.
What is the Path /I of the Controller PIC (0-1)?
What is the Channel /I of the Controller PIC (I-IS)?
What is the Path /I of the Device PIC (0-1)?
What is the Channel /I of the Device PIC (1-15)?
At present, path a is the only path available on the HP3000 Mighty Mouse system. If the number en-
tered is out of range or the Channel/Path combination has already been used then an error message
will be displayed and the user will be prompted for the information again.
PTSDIAG will inform the user to connect the Controller PIC to the Device PIC via an HPIB cable.
2) PTSDIAG asks the user if there will be a third PIC used in the test.
Do you want a Busy PIC (YIN)?
If 'V' then PTSDIAG will prompt for channel information.
What is the Path /I of the Busy PIC (0-2)?
What is the Channel /I of the Busy PIC (1-15)?
The input will be verfied and if it is invalid the user will be prompted again.
3) If 'V' was the response for the above prompt then PTSDIAG will ask- if a fourth PIC is to used in
the test.
Do you want a second Busy PIC (YIN)?
If 'V' then PTSDIAG will prompt for channel information.
What is the Path /I of the 2nd Busy PIC (0-1)?
What is the Channel /I of the 2nd Busy PIC (1-15)?
The input will be verified and if it is invalid the user will be prompted again.
PTSDIAG S
4) PTSDIAG next prompts for the amount of memory in the system and the number of times the test
is to be repeated.
64K RAMS/l Board -> Banks - 4
64K RAMS/Z Boards -> Banks - 8
Z56K RAMS/l Board -> Banks - 16
ZS6K RAMS/Z Boards -> Banks - 3Z
Input /I of banks in system: (l-3Z)
Enter the Loop count - 0 for continuous looping (O-3Z"'):
If the input is invalid the user is re-prompted.
5) PTSDIAG will then prompt the user for information on error handling, reporting and diagnostic
control.
Pause on Error (YIN - N-Default)?
Output results to Line-Printer (Y /N - N-Default)?
Suppress results (Y /N - N-Default)?
6) The user may select not to halt at the end of the program before exiting back to DUS. If the tape
drive was removed during the test then this option should not be choosen because an error will occur
in DUS if the tape drive is not attached
Suppress End of Program Pause (YIN - N-Default)?
7) If at any time CNTRL-Y is used to stop the program execution a prompt will be displayed:
Enter 'GO' to continue~ 'RUN' to restart i or 'EXIT to return to DUS:
8) If an end of program pause or error pause is requested a prompt is displayed:
Enter 'GO' to continue, 'RUN' to restart, or 'EXIT to return to DUS:
When the diagnostic is restarted using 'RUN', PTSDIAG will ask the user if the PIC - TIC configura-
tion will be changed.
Do you want to change PIC-TIC configuration (Y /N - N-Default)?
This will also allow the user to change the diagnostic control configuration. If 'Y' the user will be
prompted for path/channel information. If not the diagnostic will run with the previous
configura tion.
When 'EXIT' is entered in response to the prompts, the diagnostic will return directly to DUS.
3.2.4 End of Diagnostic and return to DUS
As PTSDIAG is executed, after every pass a 'heartbeat' message is displayed informing the user of the
number of passes completed and the total number of errors. If the diagnostic is not exited early and
suppress end of pause is set, then when the loop count has expired a completion message is displayed
and the program returns to DUS.
PTSDIAG testing completed
PTSDIAG 6
3.4 CompatabiJity Specifications
The PTSDIAG is a new product and not a replacement. It takes one test from nCDIAG and one step
from PICDIAG to make one complete test using both the PIC and TIC.
3.5 Security Specifications
PTSDIAG runs under DUS and as such runs in priviledged mode. The system must be down to load
DUS and run the diagnostic.
3.6 Error Messages
If an error occurs during execution of PTSDIAG and it is not an error trapped by the PTSDIAG
program, it will result in a DUS error message. This should not occur except under very unusual cir-
cumstances, ie. some part of the system other than the TIC or PIC under test failed to function
properly.
Each error trapped by PTSDIAG will result in an error message.
3.6.1 PIC Error Messages
The following are errors generated from the PIC DMA transfers:
a) Output Transfer failed on PICs:
EXAD-%XXXXXX X'START-%XXXXXX Y'START