User`s guide

4. Conﬁgure the memory in the system and test only the ﬁrst 4 MB of memory.

If there is more than one memory module of the same size, the lowest

numbered memory module (one closest to the CPU) is tested ﬁrst.

If the memory test fails, the failing bank is mapped out and memory is

reconﬁgured and re-tested. Testing continues until good memory is found. If

good memory is not found, an error beep code (1-3-3) is generated and the

power-up tests are terminated.

5. Check the data path to the FEPROMs on the motherboard.

6. The console program is loaded into memory from the FEPROM on the

motherboard. A checksum test is executed for the console image. If the

checksum test fails, an error beep code (1-1-4) is generated and the power-up

tests are terminated.

If the checksum test passes, control is passed to the console code, and the

console ﬁrmware-based diagnostics are run.

2.9.2 Console Firmware-Based Diagnostics

Console ﬁrmware-based tests are executed once control is passed to the console

code in memory. They check the system in the following order:

1. Perform a complete check of system memory.

Steps 2–5 may be completed in parallel.

2. Start the I/O drivers for mass storage devices and tapes. At this time a

complete functional check of the machine is made. After the I/O drivers

are started, the console program continuously polls the bus for devices

(approximately every 20 or 30 seconds).

3. Check that EISA conﬁguration information is present in NVRAM for each

EISA module detected and that no information is present for modules that

have been removed.

4. Run exercisers on the drives currently seen by the system.

Note

This step does not ensure that all disks in the system will be tested or

that any device drivers will be completely tested. Spin-up time varies

for different drives, so not all disks may be on line at this point in the

power-up sequence. To ensure complete testing of disk devices, use the

test

command (Section 3.3.1).

Power-Up Diagnostics and Display 2–21