System Maintenance Strategy
1.2 Product Service Tools and Utilities
• ROM-Based Diagnostics
ROM-based diagnostics have significant advantages:
Load time is virtually nonexistent.
The boot path is more reliable.
Diagnosis is done in a more primitive state.
RECOMMENDED USE: The CPU ROM-based diagnostic facility is the
primary means of offline testing and diagnosis of the CPU, memory,
Ethernet, and DSSI subsystems. The ROM-based diagnostics are
used in the acceptance test procedures (Section 4.4) when installing
a system, adding a memory module, or replacing the following: CPU
module, memory module(s), backplane, DSSI device, or H3604 console
module. Use the ROM-based diagnostic error messages in Table 5–9 to
isolate FRUs.
• Firmware Console Commands
Several commands and utilities are needed in configuring a system and
setting and examining system and device parameters. For example, the
CONFIGURE command is used to determine the proper CSR addresses
for modules; the SHOW MEMORY, SHOW DSSI, and SHOW QBUS
commands are used to examine the configuration and memory error
status; and the SET HOST command is used to access the DUP driver
to configure DSSI parameters.
RECOMMENDED USE: Use console commands to configure the system
and in setting and examining device parameters. Refer to Section 3.8
for information on firmware commands and utilities. Appendix A
provides information on all available console commands.
• Option LEDs During Power-Up
Many options and modules have LEDs that display pass/fail self-test
results.
RECOMMENDED USE: Monitor option and module LEDs during
power-up to see if they pass their self-tests. Refer to Sections 4.2.2 and
4.2.3 for information on power-up tests for Q–bus and mass storage
devices. For more information on individual options, refer to your
Microsystems Options
manual.
System Maintenance Strategy 1–3
