User`s guide

System Initialization and Acceptance Testing (Normal Operation)
4.3 CPU ROM-Based Diagnostics
User Determined Parameters
Parameters that you can specify are written out, as shown in the following
examples:
30 2005C33C Memory_Init_Bitmap *** mark_Hard_SBEs ******
54 20055181 Virtual_Mode *********
For example, the virtual mode test contains several parameters, but you cannot
specify any that appear in the table as asterisks. To run this test individually,
enter:
>>>T54
The MEM_bitmap test, for example, accepts 10 parameters, but you can only
specify mark_hard_SBEs because the rest are asterisks. To map out solid,
single-bit ECC memory errors, type:
>>>T300001
Even though you cannot change the first three parameters, you need to enter
either zeros (0) or ones (1) as placeholders. Zeros are more common and are
shown in this example. The zeros are placeholders for parameters 1 through 3,
which allows the program to parse the command line correctly. The diagnostic
executive then provides the proper value for the test.
You enter 1 for parameter 4 to indicate that the test should map out solid,
single-bit as well as multibit ECC memory errors. You then terminate the
command line by pressing
RETURN
. You do not need to specify parameters
5 through 10; placeholders are needed only for parameters that precede the
user-definable parameter.
For the most part tests and scripts can be run without any special setup. If
a test or script is run interactively without an intervening power up, such
as after a system crash or shutdown, enter the UNJAM and INIT commands
before running the tests or script. This will ensure that the CPU is in a well
known state. If the commands are not entered, misleading errors may occur.
Other considerations to be aware of when running individual tests or scripts
interactively:
• When using the TEST or REPEAT TEST commands, you must specify
a test number, test code or script number following the TEST command
before pressing
RETURN
.
• The memory bitmap and Q–bus scatter-gather map are created in main
memory and the memory tests are run with these data structures left
intact. Therefore, the upper portion of memory should not be accessed
System Initialization and Acceptance Testing (Normal Operation) 4–11