HP Omnibook 800csct Service Manual

							Part 2
Troubleshooting
· Power-On Self-Test
· OmniBook Diagnostics
· Desktop Management Interface
· System Configuration Utility
· Troubleshooting Tips 
						

							4Power-On Self-Test
The OmniBook 800 BIOS includes a Power-On Self-Test (POST) facility that tests a number of
hardware and firmware items in the unit at each cold-start (BOOT or RESET).
The OmniBook self-test alone should not be used to diagnose a hardware problem.  If the self-
test results are absolutely clear and repeatable, confirm the results with at least two other non-
self-test failure symptoms.
Within POST, there are three kinds of messages:
· Error Messages – These messages appear when there is a failure in hardware,
software, or firmware.
· Informational Messages – These messages provide information to the user but
require no action.
· Beep Codes – This kind of warning sounds when POST errors occur and the screen
is not yet available.
Beep Codes
These multiple beep codes indicate a failure in a simple test of:
· a portion of base memory
· flash BIOS checksum
· a portion of conventional memory
· a portion of extended memory
If the unit fails to boot, ensure that
· all accessories are removed, including:
memory, floppy drive, docking station, modems and other  PC Cards, printers,
external displays, pointing devices, and keyboard
· clean AC power is provided (no “chained” battery chargers or auto adapters), and
press reset.
If the unit still fails to boot, it requires service.
Beep codes are used to identify a POST error that occurs when the screen is not available.
Once the screen is operating, diagnostic messages are reported to the screen.  There are beep
codes for both fatal and non-fatal system board errors.
Table 2 - POST Beep Codes
Beep CodeDescriptionS-S-S-P-S-S-L-PThe DMA page registers are faulty.S-S-S-P-S-L-S-PThe refresh circuitry is faultyS-S-S-P-S-L-L-PThe ROM checksum is incorrectS-S-S-P-L-S-S-PThe CMOS RAM test failedS-S-S-P-L-S-L-PThe DMA controller is faultyS-S-S-P-L-L-S-PThe interrupt controller failedS-S-S-P-L-L-L-PThe 8042 keyboard controller failedS-S-L-P-S-S-S-PNo video adapter was foundS-S-L-P-S-S-L-PNo RAM installed.  No message is displayed. 
						

							5Display Codes
There are a number of Power On Self Test (POST) tests that are performed after the Beep Code
tests.  Failure of one or more of these tests will result in a displayed failure code (such as
03044).  It is extremely important not to interpret a failure code immediately as a hardware
failure.  The failure should be confirmed with a clean boot.  A clean boot is defined as pressing
the reset button after removing all accessories (including additional memory, floppy drive,
modems, PC cards, and printers) and providing a reliable power source.  Note, make sure the
display is adjusted to be visible.
The following tables lists common PC error messages.  Not all of these messages will appear on
every model of the OmniBook 800.
Table 3 - POST Display CodesMessagePossible CauseCLOCK NOT TICKING CORRECTLYThe real time clock is not ticking.COLOR/MONO SWITCH INCORRECTThe COLOR/MONO switch on the system
board is incorrect for the installed
hardware.CMOS CHECKSUM INVALID - RUN SCUCMOS RAM information has been
corrupted and needs to be reinitialized via
the System Configuration Utility.CMOS FAILURE - RUN SCUCMOS RAM has lost power and needs to
be reinitialized via the System
Configuration Utility.FLOPPY CONTROLLER FAILEDThe floppy controller failed to respond to
the reset command. Power down the
system and check all appropriate
connections.  It the floppy  controller
continues to fail, you may need to replace
it.FLOPPY DISK TRACK 0 FAILEDThe floppy drive cannot read track 0 of
the floppy disk in the drive.  Try another
diskette.  If the problem persists, you may
need to replace the floppy drive.FLOPPY INFORMATION INVALID - RUN SCUThe drive parameters stored in CMOS do
not match the floppy drives detected in
the system.HARD DISK CONTROLLER ERRORThe hard disk controller failed to respond
to the reset command.  Possible
solutions:  1) Check the drive parameters.
2) Power down the system  and check all
appropriate connections.  If the problem
persists, you may need to replace the
hard disk controller.HARDWARE INFO DOES NOT MATCH VIDEO
CARD - RUN SCUThe video adapter type specified in
CMOS RAM does not match the installed
hardware.KEYBOARD CONTROLLER FAILUREThe keyboard failed the self-test
command.  Check to see if the keyboard
controller is properly installed.  If the
problem continues, replace the controller. 
						

							6MessagePossible CauseKEYBOARD FAILUREThe keyboard failed to respond to the
RESET ID Command.MACHINE IS LOCKED - TURN KEYThe system will not continue the boot
sequence until you insert the key into the
key lock and turn it.NO BOOTABLE FLOPPY DRIVE 0 INSTALLEDNo bootable floppy drive was detected.
Possible solutions:  1) Power down the
system and check all appropriate
connections, cables, etc.  2) In
configurations where no floppy drive is
installed, run System Configuration Utility
and make sure the diskette drive
configuration item is set to “None”.  3)
Replace the diskette drive if necessary.NO INTERRUPTS FROM TIMER 0The periodic timer interrupt is not
occurring.RAM PARITY ERROR AT LOCATION xxxxA RAM parity error occurred at the
specified (hexadecimal) location.ROM AT xxxx (LENGTH YYYY) WITH NON-ZERO
CHECKSUM (zz)An illegal adapter ROM was located at
the specified address.  An external
adapter (such as a video card) may be
causing a conflict.TIME/DATE CORRUPT - RUN SCUThe time and date stored in the real time
clock have been corrupted, possibly by a
power loss.UNEXPECTED AMOUNT OF MEMORY - RUN SCUThe amount of memory detected by
POST does not match the amount
specified in CMOS RAM.CMOS RAM TEST FAILEDA walking built test of CMOS RAM
locations 0E (Hex) - 3F (Hex) failed.DMA CONTROLLER FAULTYA sequential read/write of the transfer
count and transfer address registers
within the primary and secondary DMA
controllers failed.FAULTY DMA PAGE REGISTERSA walking bit read/write of the 16 DMA
controller page registers starting at
location 80 Hex failed.FAULTY REFRESH CIRCUITA continuous read/write test of port 61h
found that bit 4 (Refresh Detect) failed to
toggle within an allotted amount of time.INTERRUPT CONTROLLER FAILEDA sequential read/write of various
Interrupt Controller registers failed.ROM CHECKSUM INCORRECTA checksum of the ROM BIOS does not
match the byte value at F000:FFFF. 
						

							7OmniBook Diagnostics
The OmniBook diagnostics program provides an effective tool for diagnosing and isolating a
hardware problem.  The diagnostics software is intended for use in concert with additional
troubleshooting methods to accurately determine the cause of trouble.  The diagnostics program
is not designed for unassisted end customer use.
Diag is a DOS program developed to test the OmniBook 800 computer and docking station.  For
the most part Diag is a stand-alone program, testing components and subsystems independently.
Some tests require “loopback” adapters for complete testing, and some tests require other
hardware (e.g. SCSI devices).  Basic knowledge of running software is assumed.
Running the diagnostics program
A “clean boot” is the environment from which to run Diag.  For a system that normally boots up
to Windows for Workgroups, press F5 at bootup.  For a Windows 95 system, press Shift+F5.
Alternatively, the CONFIG.SYS and AUTOEXEC.BAT files may be modified to exclude drivers
and/or launch Diag if desired.  Please note that the SCSI tests do require loading some drivers;
those drivers will be addressed in the context of those tests.
The diagnostic program is located in the c:\omnibook\diag directory and is invoked by typing
diag followed by the Enter key.
Main diagnostic screen
The OmniBook diagnostic program is controlled primarily from a single screen.  The top two
thirds of the screen reports the tests selected and test results.  The bottom third is used to scroll
test results as the tests run.  Thirty tests are listed under the Menu heading.  See Figure 4 for a
sample of the main diagnostic screen.
Tests selected for looped running show a test level of 1 to 3 to the left of the test name.  When a
test ends, the status of the test and the date and time are reported.  As a test runs, ongoing
status can be reported either on the same line as the test, or scrolled into the bottom region.
When looping tests are performed, the bottom line reports when the loops begun and which loop
is currently running.  If a test ever fails, a red ‘x’ appears to the left of the test name.  The
version of Diag is reported near the bottom of the display, as is the version of the BIOS.
External monitor colors can be checked at a glance with the RED GREEN and BLUE colored
text boxes. 
						

							8Figure 4 - Main Diagnostic Screen
Running selected tests
Tests may be initiated individually, or as a group.  Some tests may be run at different levels.  In
general, tests that can take a long time to be fully checked have levels that permit testing more
quickly while still providing a reasonable level of testing.  An unselected test has a 
before the test name.  A test at a quick level has a  before the test name.  A standard level
test has a  before the test name.  A long test has a  before the test name.  Every test has
a standard level.  Some tests also have a quick level, and some tests also have a long level.
Some have both quick and long. Menu                     Status                                 Date   Time 2 CPU                Ok                                         08/08 14:36:182 Cache              Ok                                         08/08 14:35:201 RAM, motherboard   16 MB Ok                                   08/08 14:36:221 RAM, plug in       00 MB Ok                                   08/08 14:36:232 BIOS flash ROMS    OK C-F=8676? Altera=E56C? Boot=C600?       08/08 14:36:252 CMOS               Ok                                         08/08 14:36:26  Upper PC Card  Lower PC Card2 Timers             Ok                                         08/08 14:36:262 Real time clock    Ok                                         08/08 14:36:302 IRQ controller     Ok                                         08/08 14:36:312 DMA controller     Ok                                         08/08 14:36:32  IR port  Serial port  Printer port1 Hard disk          813Mb Ok                                   08/08 14:36:32  Floppy disk2 Battery            Bat=LiIo (OK) Chg=FC B%=60 Vb=8.17 Ta=57.2 08/08 14:36:33  SCSI loopback1 Keyboard           Ok                                         08/08 14:36:361 HP mouse           Ok                                         08/08 14:36:362 Audio              Ok                                         08/08 14:36:391 Display            Ok                                         08/08 14:36:421 Docked device      Ok: NOTHING.                               08/08 14:36:42  SCSI CD ROM  SCSI Hard disk  Dock slots  Dock keyboard  Dock PS2 mouse  Dock EEPROMKeyboard Power-On SelftestKeyboard IRQ TestKeyboard Interface Test   +3708         +3695DSP ChipDMA ChannelInterrupt LinesSound Output TestVersion 04 Jan 97, Bios 97/01/29  RED   GREEN   BLUE  ARROW keys select tests. ENTER or 1, 2, 3 runs test. Or press SPACE to mark tests then ENTER to run them.  F1 or ? gives help. DIAG /? Shows options.  loops=2/20. Last loop begun at 08/08 14:36:18 
						

							9The name of the currently selected test is always shown inversed.
To help monitor the progress of testing, the LEDs (near the On button) blink about once per
second from green to off.  If a test has failed the LEDs blink from red to off.  When Diag finishes
testing, the LEDs blink rapidly.  If the system locks up for some reason, the LEDs generally stop
blinking.
Alternative methods for running tests
Individual tests may be run by moving the highlight to the desired test and running it.  Move the
highlight and run the tests by the following means:
Keyboard – cursor  and  keys to select,  to run.  Also  to specify a
test level,  to cancel a test,  to exit Diag.  Many other features and options
are also available from the keyboard.
Contrast/Brightness buttons –  to select (mimics the Down key),  to run (mimics
the Enter key).  This is most useful on production units that have no keyboard.  For checking
“Newton rings” during display testing, it is necessary to adjust the contrast.  To have the contrast
keys operate normally, press both at once.  To have them mimic the Down and Enter keys, press
both again.
Mouse – when the -m command line option is specified, use the top or bottom “bumper” to
select, and left button to run.  Also use the right button to specify test level (space), right bumper
to cancel a test (Backspace), and left bumper to exit Diag (Esc).
Serial – same keys as with a keyboard, but from a remote system (HP 100LX, etc) connected
into the RS232 port on the OmniBook.  The remote computer’s serial port should be configured
for 9600,N,8,1.  The communication program Kermit is well suited to communicate with Diag, in
that it sends cursor and function key codes as PC key codes (e.g.  transmits  then
).  Controlling Diag via the serial port permits the same level of control of modes and toggles
as does direct keyboard control.  Please note that the serial test cannot be run when the serial
port is used for control (though the serial port gets a decent workout controlling Diag anyway).
Special test hardware requirements
The following tests require the following hardware to operate:
· The Upper/Lower PC Card tests require a Sycard test card and a modified
extender card.
· The IR port test requires another OmniBook 800 running the fast IR test.
· The Serial port test requires an HP RS-232 serial loop back connector.
· The Printer port test requires an HP parallel port loop back connector.
· The SCSI test requires an HP SCSI port loop back connector.
· The SCSI CD ROM test requires a CD ROM device connected by SCSI cable.
· The SCSI Hard disk test requires a Hard disk connected by SCSI cable.
· The Dock slots test are currently unimplemented.
· The Dock keyboard test requires a docking station and an external  keyboard.
· The Dock PS2 mouse test requires a docking station and a PS2 mouse.
· The Dock EEPROM test requires a docking station. 
						

							10Loop Back Connectors
In order to run the RS232 serial port, parallel port, and SCSI port self-test, a loop back connector
is needed.  The loop back may be placed on either the OmniBook port or at the end of the
corresponding cable.  This feature is also helpful in diagnosing a defective serial, parallel, or
SCSI cable.
Loop back connectors may be purchased or can easily be constructed.  The following illustrations
identify the correct pin-out configurations for the serial, parallel, and scsi loop back connectors.Figure 5 - Serial Loop Back ConnectorFigure 6 - Parallel Loop Back ConnectorFigure 7 - SCSI Loop Back Connector 
						

							11PCMCIA Type III extender card
The PCMCIA test that makes use of SyCard Technology’s SyCard also requires an extender
card modified with two jumpers or with solder bridges.  In order for the Sycard to be detected,
CD1- and GND must be shorted together, and GND with CD2- must also be shorted together.
These are both pairs of endmost pins on the extender.  Once these jumpers or solder bridges are
added, the SyCard will successfully be detected and the SyCard tests can be performed.  See
Figure 8.Figure 8 - SyCard Solder BridgesSolder Bridges 
						

							12Command line options
When Diag is run, either from the command line, or from a batch file, a number of switches (or
options) may be included to “customize” the operation of Diag.  Switches must be specified
separately, and must begin with either a - or a / character.  Upper or lower case may be used as
desired.  Switches may be used in any order.  The switches, a brief description, and their use are
described below:
Table 4 - Diagnotic Command Line OptionsSwitchDescription-?Report the standard command line options available.-!Report standard and hidden command line and keyboard commands available.-cNxxxxSpecify Nth ROM checksum.  The “BIOS flash ROMs” test the flash memory for
correctness.  In order for Diag to maintain usefulness in the face of new and
different BIOSes, a way is needed to specify the BIOS ROM values.  Though the
test will not fail (as of this writing) if the checksums are not specified, a ‘?’ will show
after a sum to indicate checksum uncertainty.  All three checksums must be
specified to fully qualify the ROMs.  As an example, to test a build with the
960701.ROM, the user would enter: Diag -c121E9 -c2D631 -c3C600.  Batch files
that need to work with both F1175 and F1360 OmniBooks may specify two
checksums after each switch, the first one for the F1175 and the second one for the
F1360.  For example, to test the 970121 ROMs for both units, use the following
switches:  -c1B7386A45 -c2DC8CDC8C -c316001600.-dSelect Dock tests only.  For testers wishing to test docks, this switch restricts the test
shown to those that pertain to the dock only.  The set of tests shown in this mode
include the following: Serial port, Printer port, SCSI loopback, Audio, Floppy disk,
Docked device, Dock keyboard, Dock PS2 mouse, Dock EEPROM.-fRun Fast IR loopback mode on startup.  The IR port test needs a computer running
in “passive” mode to send IR data back to the computer being tested.  An IR test
station can be automated by having the passive computer run Diag with the -f option
in its AUTOEXEC.BAT file.  The key  can also be used to put the computer
into passive mode.  Press  to exit from passive mode.-kRun a Keyboard macro file.  This switch is by far the most powerful and versatile in
that it lets the operator set up different configurations and test sequences and play
them back later just as though they were typing the commands from the keyboard.
For information on creating a keyboard macro file, see the  command.-mEnable Mouse keyboard control.  For units that do not have a keyboard, use this
option to control Diag with a mouse.  For more information on this feature, see the
 command-rRun nth test and return exit code.  For testing from a batch file, this switch can be
used to run a single test and return the test result in the errorlevel.  0=pass, 1=fail,
2=aborted, 3=no loop/can’t run.  Tests are specified by ordinal number counting
from 1 at the top.  Use the -1, -2, -3 option below to set the test level.-sDisable control via Serial port.  By default, the serial port can be used to control
Diag via a host computer (running Kermit connected at 9600, N, 8, 1) when no
keyboard is available, the unit cannot be easily accessed for entering commands, or
remote automated operation is needed.  Serial control is always automatically
disabled during the serial port test, but if the serial port is used for other activities,
use this switch to completely disable control.-xTest for the eXtra key on foreign keyboards.  Foreign keyboards have an extra key
to the left of the space key.  To include this key in the internal keyboard test, add a -
X parameter when running Diag.  Because the keyboard test is scancode based (not
ASCII character), the key names are NOT localized to their foreign equivalents.