Extended Testing; The Human Interface - HP 340 Series Service Manual

Extended Testing
If
m
is pressed, the self-test will be started over and the long memory test will be executed,
taking approximately 4 seconds per megabyte rather than the default, short memory test taking
approximately 1 second per megabyte. This mode will also invoke extended testing on LAN
and SCSI interfaces (does external loop back and cable testing). The latter testing will request
the user to power off any SCSI peripherals and attach the appropriate end of the SCSI test
connector.
Extended Test Mode can be invoked while running in looping mode. The result is continuous
extended testing. SCSI extended testing will not be done in this combination.
With a ThinLAN interface board installed, all extended test functions will work. When an AUI
LAN interface board is installed, an external HP 30241A Backbone Media Attachment Unit
(MAU) must be connected to the LAN interface port for extended test functions to work. If an
external MAU is not connected, the extended test will report a failure.
Continuous Self-Test
Pressing [IJ causes the Boot ROM to continuously repeat the self-test portion of its code.
Entering configure mode while already in continuous self-test mode and choosing the "L" option,
will stop the continuous self-test and will cause the Boot ROM to continue normal operation.
While in continuous self-test rnode, the Boot ROM will not wait, beep or stop for most failures,
but will just continue looping through self-test. The following failures will stop self-test looping:
• A memory failure in the top 16K bytes.
In this case the Boot ROM stops with the display blanked and
000000 • •
on the LEDs.
• Boot ROM checksum failure
In this case the Boot ROM stops with the message
CONTINUE AT OWN RISK (RETURN To
Continue)
is displayed, the value
0000 • • • 0
on the LEDs, and then beeps appropriate low
and high tones. Pressing [
Return
I
will cause the Boot ROM to continue self-test looping.
The Human Interface
Some devices may act as the "console", or primary human interface, for the Boot ROM. As of
this revision, the list of possible console devices is explained in the next section.
Output Devices
• Supported HP terminals are defined as those terminals supported by HP on HP-UX for
Series 300. See the section of this chapter describing Remote Human Interface for Boot
ROM requirements ..
• Internal RS-232 controller with the remote bit set (with a supported HP terminal).
• The bit-mapped video circuit.
Only one output device at a tirrle will be used as the console output device, however, the Boot
ROM will initialize and clear the bit-mapped video circuit even if that circuit is not chosen as
the console device. Note that if a device fails self-test then for the above algorithm, the device
is considered "not present". The Boot ROM always tests a device before choosing it as the the
console output device.
72
Boot ROM Functions