Service manual

To enter the RBD monitor, at the console prompt type:
>>> T/R ! This is the abbreviation for TEST/RBD.
! Early versions of the console only accept T/R.
RBDn> ! RBD prompt appears signifying entrance into
! RBD mode, where n is the XMI node number of
! the processor running the RBD monitor program.
The RBD commands are explained here and in Sections 2.3.2 and 2.3.6.
Table 2–2 gives the commands, their abbreviations, and functions.
Four programs run from the ROM-based diagnostics (RBD) monitor
program. The programs are CPU self-test, CPU/memory interaction tests,
the DWMBB tests, and memory RBD tests. Each of these programs has
several tests, as shown in Table 2–4 and Table 2–5. A fifth program is
available for the <REFERENCE>(hyperion) and tests it’s secondary cache.
The RBDs are designed for use by Digital customer service personnel.
The RBD monitor responds to several control characters. These characters
manage both the diagnostic and the monitor as shown in Table 2–3.
When CTRL/C is entered from the console terminal, the diagnostic stops
execution, runs cleanup code, and returns control to the RBD monitor
program. This happens immediately when running RBD 0, RBD 1, or RBD
2; there may be a wait of up to one minute for a response when RBD 3 is
running. If CTRL/C is typed at the RBD monitor prompt, it has the same
effect as CTRL/U.
When you use the DELETE key (or rubout key), characters being deleted
are preceded by a backslash ( \ ) and print as they are rubbed out. When
the next valid character is typed, it is preceded by a backslash ( \ ) to
delineate the deleted characters. You can use CTRL/R to refresh the line.
When the RBD monitor program receives a CTRL/U, the program
disregards all previous input typed and returns the RBD prompt. If a
test is running when CTRL/U is entered, CTRL/U is ignored.
When a CTRL/Y is received by the RBD monitor program from the console,
the diagnostic stops execution and returns control to the RBD monitor
program. No cleanup code is run, and the unit under test is left in an
indeterminate state. A CTRL/Y entered at the RBD monitor prompt has
the same effect as CTRL/U.
When the RBD monitor program receives a CTRL/Z, the program exits and
control is returned to the console program (>>>). CTRL/Z has the same
effect as the QUIT command. If CTRL/Z is entered while an RBD test
is running, CTRL/Z has the same effect as CTRL/C: it halts the test and
executes cleanup code.
Diagnostics 2–9