Console Firmware-Based Diagnostics; Boot Sequence - DEC 4000 AXP Service Manual

2.3.3.2 Console Firmware-Based Diagnostics

Console firmware-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. If a system has more than one
memory module, the modules are checked in parallel.
2. Set memory interleave to maximize interleave factor across as many memory
modules as possible (one, two, or four-way interleaving). During this time the
console firmware is moved into backup cache on the primary CPU module.
After memory interleave is set, the console firmware is moved back into
memory.
Steps 3–7 may be completed in parallel.
3. 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).
4. Size, configure, and test the Futurebus+ options.
5. Exercise memory.
6. Check that the SCSI continuity card or a storage device is installed in the
removable-media storage bus (Bus E, connectors J6 and J7).
7. Run exercisers on the disk drives currently seen by the system.
This step does not currently ensure that all disks in the system will be
tested or that any device drivers will be completely tested. To ensure
complete testing of disk devices, use the
8. Enter console mode or boot the operating system. This action is determined
by the auto_action environment variable.

2.4 Boot Sequence

Bootstrapping is the process of loading a program image into memory and
transferring control to the loaded program. The system firmware uses the
bootstrap procedure defined by the Alpha AXP architecture and described in the
Alpha System Reference Manual. On a DEC 4000 AXP system, bootstrap can be
attempted only by the primary processor or boot processor. The firmware uses
Note
test command.
Power-On Diagnostics and System LEDs 2–33