Oracle Vacuum Cleaner CPU-56T User Manual
OpenBoot Firmware
Introduction
94
SPARC/CPU−56T
Alias
Device
ttyb
Serial interface B
tyyc
Serial interface C
tyyd
Serial interface D
vme
VME
OBDIAG
OBDIAG stands for OpenBoot Diagnostics and is an additional diagnostics drop−in driver
program which serves as an NVRAM configuration feature.
program which serves as an NVRAM configuration feature.
a
It allows to test the hardware by calling OBDIAG when the OpenBoot firmware is present
and the <ok> prompt has appeared. During the start−up sequence of the CPU, OpenBoot
searches for the presence of devices on all expansion buses and evaluates their
characteristics such as device ID, device type, vendor ID, and revision ID. In order to test
the hardware, OBDIAG requires selftest methods for the discovered devices. If OBDIAG
does not find any selftest methods in the device nodes, it looks for its own selftest
methods.
and the <ok> prompt has appeared. During the start−up sequence of the CPU, OpenBoot
searches for the presence of devices on all expansion buses and evaluates their
characteristics such as device ID, device type, vendor ID, and revision ID. In order to test
the hardware, OBDIAG requires selftest methods for the discovered devices. If OBDIAG
does not find any selftest methods in the device nodes, it looks for its own selftest
methods.
a
Executing OBDIAG
There are two different methods to execute OBDIAG:
a) Via Script
b) Manually
Via Script
In order to execute OBDIAG via script, set two configuration variables by enterring:
setenv mfg−mode chamber
setenv diag−switch? true
Now a script of additional diagnostic tests is executed automatically after each POST from
OBDIAG provided that POST has been running without failure during hardware power
on.
OBDIAG provided that POST has been running without failure during hardware power
on.
Manually
In order to execute OBDIAG manually, enter the following command at the ok prompt:
obdiag