Overview
The Offline Diagnostics Environment (ODE) is an offline support
tools platform that enables you to troubleshoot a system that is
running without an operating system. ODE can be used to test systems that cannot
be tested using the online tools. The offline environment is also useful for some types
of testing in which it is not desirable to have to boot the system
first, as is often the case in manufacturing applications.
User interface for ODE
ODE provides an user-friendly interface for diagnostics
and utilities developed to run in this environment. The command line
interface (CLI) enables you to select specific tests and utilities
to execute on a specific hardware module. The menu-driven interface that
is available on 32-bit systems, enables you to specify the hardware module
for testing. ODE selects the appropriate tests to execute on the module.
Structure of ODE
ODE has a distributed
architecture consisting of several modules. Each module has a
specific function and uses well defined protocols to communicate
with other modules.
The Offline Diagnostic Environment consists of the following modules:
- Test Controller - Acts as an user interface and
launches the execution of the Test Modules.
- Test Modules - Consists of diagnostic or utility
programs designed to execute within ODE. These modules exercise
or diagnose the user specified hardware unit or may perform some
specific utility-type operation such as, firmware download.
- System Library (SysLib) - Consists of a set of common
routines for use by both the Test Controller and Test Modules.
These routines perform functions such as Input/Output (I/O), string
parsing, and system control.
Top of page
ODE on PA-RISC
Tools Provided
Diagnostics and utilities provided under ODE for PA-RISC computers
include:
- MAPPER - a utility for mapping out the physical layout of the
CPU and its peripherals.
- IOTEST - a utility for testing I/O cards using I/O Dependent
Code (IODC).
- PERFVER - a utility for testing peripherals attached to the
boot path.
- A set of diagnostics and utilities for testing disks.
- A set of diagnostics for testing CPU, memory, and selected
I/O modules.
The 64-bit computer systems like N-CLass have a different
version of the offline diagnostics programs. The 64-bit version has
a "2" appended to the program name. For example, the 64-bit version
of MAPPER is MAPPER2.
On 64-bit computer systems, a utility for updating firmware,
reading Vital Product Data (VPD) and World Wide Number (WWN) of
supported I/O cards is also available.
Note: You need to have license for running most of the ODE diagnostics
and utilities. Refer to the
HP 9000 CD Overview Guide
for information
on tools that require license on 64-bit computer systems.
Launching ODE
You can launch ODE on PA-RISC computers in the following ways:
- The complete set of offline diagnostics from the HP 9000 Offline
Diagnostics CD
- A subset of the offline diagnostics, run from the LIF volume
on the computer's system disk.
Note: To run the offline diagnostics from the system disk,
you must install the LIF product to the boot area of the system disk
from the HP 9000 Offline Diagnostics CD. Earlier, the LIF volume was a part
of the Support Plus Media. Starting with Support Plus Release Sept 2005,
LIF volume will not be available on the Support Plus Media. Instead, the LIF
volume will be available on the HP 9000 Offline Diagnostics CD. Refer to
How do I install LIF-LOAD on my HP 9000 system?
for information on the installation procedure.
Run from the HP 9000 Offline Diagnostics CD
For the following reasons, HP recommends that you launch the Offline
Diagnostics Tools using the HP 9000 Offline Diagnostics CD:
- You can access the complete set of Offline Diagnostics Tools.
- You can launch the offline diagnostics tools from the CD when
the system is not booted to the operating system.
- You do not need a system disk for launching ODE.
- You can run the Offline Diagnostics Tools on both HP 3000
(MPE/iX) systems and HP 9000 System (HP-UX).
- You can launch the Offline Diagnostics Tools from the CD
in the same duration as you launch it from the system disk.
- You can use both command line interface and menu-driven
interface to run the Offline Diagnostics Tools on 32-bit computers.
Run from the System Disk
If you do not have the HP 9000 Offline Diagnostics CD, you can launch the
Offline Diagnostics Tools from the system disk. Before you launch the Offline
Diagnostics Tools from the system disk, read the following:
- The system disk contains only a subset of the most commonly used
Offline Diagnostics Tools. Following lists the tools that are available on
the boot LIF volume of the system disk:
- For 32-bit systems (for example, K-Class systems): MAPPER2, IOTEST, PERFVER
- For 64-bit systems (for example, N-Class systems): MAPPER2, IOTEST2, PERFVER2
- You can launch ODE from the boot LIF volume,
when the system is at the PDC prompt.
- You cannot launch ODE on HP 3000 (MPE/iX) systems.
- You cannot use the menu-oriented interface.
Note: Starting with September 2005 release, the LIF volume will
not be available on Support Plus Media. The LIF volume will be
available only on the HP 9000 Offline Diagnostics CD.
Untill Support Plus Release May 2005, the LIF volume was available only
after the OnlineDiag bundle was installed. This bundle included Online
Diagnostics (STM), EMS Hardware Monitors, and subset of Offline
Diagnostics (LIFLOAD).
Top of page
You use ODE tools on Itanium Processor Family computers just as you would on the
PA-RISC computers. The syntax and operation is the same; the only differences
are the names of the tools and the way that ODE is launched. Instead of being
distributed on the Support Plus Media, ODE is distributed on the
Offline Diagnostics and Utilities CD for the Itanium Processor Family.
Tools Provided
For the Itanium Processor Family, the ODE tools include:
- CIODIAG2 - core I/O diagnostics
- CPUDIAG - CPU diagnostics
- MAPPER - utility for mapping out the physical layout of
the computer and its peripherals
- PERFVER - utility for testing peripherals attached to the
boot path
- MEMDIAG - memory diagnostics
- PLUTODIAG - diagnostics for the Zx1 ("Pluto") and "Mercury" Central
Electronics Complex (CEC)
- (Additional tools may appear on new releases.)
Two Ways to Run
You launch ODE either from CD-ROM
or from the HP Service Partition on the system disk. Previous to July
2003, you had no choice. You had to run ODE from the Offline
Diagnostics and Utilities CD for
the HP Itanium Processor Family.
With the July '03 release of the offline tools, you can run ODE from the HP
Service Partition (HPSP) -- a special disk partition that is available when the
operating system is not up.
Running ODE from the HPSP is considerably faster than from CD.
On the other hand, you would run ODE from CD:
- If the hard disk is not functioning or not available.
- If the computer does not support a HPSP.
- If the HPSP does not have the latest version of the tools.
On computers that have an HP Service Partition, you can copy the files to it
from the CD by using a command on the Launch menu (see
"Installing Files onto the HP Service Partition.").
This step is not necessary for computers that have the files pre-loaded on the
HPSP (for example, on some computers running HP-UX 11.23).
Run from Offline CD
- Obtain a copy of the Offline Diagnostics and Utilities CD for Itanium
Processor Family computers.
- Insert the CD into the CD/DVD drive, and reset system power. The
computer should come up to the Boot Manager menu, regardless of whether the
CD is re-inserted or not.
- See whether the CD/DVD drive is listed as one of the boot devices on the
Boot Manager menu.
- If the CD/DVD drive appears as a boot device, move the cursor to the
line that contains it and press the Enter key. The CD will boot to the
Launch menu.
- If the CD/DVD drive does NOT appear as one of the boot devices, select
the item on the Boot Manager menu to add a boot device. The exact
process is variable. A typical procedure:
- Be sure the CD is in the CD/DVD drive.
- Select "Boot Option Maintenance."
- Select "Add a Boot Option."
- Select "Removeable Media Boot." This option only appears if a CD
is in the drive.
- Answer the prompts. For "Boot Option Data Type," the Offline
Utilities and Diagnostics CD does not care what response you give.
- Exit the menu, then exit the Boot option maintenance menu. You
return to the Boot Manager menu.
- When you return to the Boot Manager menu, there should be an entry
for the CD/DVD drive as a boot device. Select it and the the CD
will boot to the Launch menu.
After configuring the CD/DVD drive as a boot device, you will not have
to add it again on subsequent boots.
- Start ODE by choosing the selection for ODE at the Launch menu.
- Alternately, you can start ODE from the EFI prompt. Change directories to
\EFI\HP\DIAG\ODE, then enter ODE. For example:
fs2:> cd \EFI\HP\DIAG\ODE
fs2:\EFI\HP\DIAG\ODE> ODE
Note:
After running any ODE module, you will need to reboot the system,
BEFORE booting the OS, and BEFORE running any non-ODE utility.
Run from HP Service Partition
- Reset system power. The computer should come up to the Boot Manager
menu.
- See whether the HP Service Partition is listed as one of the boot devices
on the Boot Manager menu (for example, "Run Offline Diagnostics and
utilities from HP Service Partition.")
- If the HP Service Partition appears as a boot device, move the cursor
to the line that contains it and press the Enter key. The computer will
boot to the Launch menu.
- If the HP Service Partition does NOT appear as a boot device, you will
have to copy the files from the CD. See "
Installing Files onto the HP Service Partition."
- Start ODE by choosing the selection for ODE at the Launch menu.
- Alternately, you can start ODE from the EFI prompt. Change directories to
\EFI\HP\DIAG\ODE, then enter ODE. For example:
fs2:> cd \EFI\HP\DIAG\ODE
fs2:\EFI\HP\DIAG\ODE> ODE
Note:
After running any ODE module, you will need to reboot the system,
BEFORE booting the OS, and BEFORE running any non-ODE utility.
Installing Files onto the HP Service Partition
- Boot from the CD to the Launch menu, as described in "
Run from Offline CD."
- At the Launch menu, choose the item for copying the contents of the CD to
the HP Service Partition ("Run CD Installer to install/update CD content to
HPSP".)
- When you return to the Boot Manager menu, there should be an entry for the
HP Service Partition as a boot device.
Top of page
Examples of Using ODE
1. Invocation example: This example is
fictitious, though it conforms to the guidelines and rules of
ODE.
Once ODE is started, the standard ODE banner will follow:
***********************************************************************
****** ******
****** OFFLINE DIAGNOSTIC ENVIRONMENT ******
****** ******
****** (C) Copyright Hewlett-Packard Co 2000 ******
****** All Rights Reserved ******
****** ******
****** ******
****** TC Version XX.XX.XX ******
****** SysLib Version XX.XX.XX ******
****** ******
****** ******
***********************************************************************
Type HELP for command information.
ODE> run cpudiag cr This TM will be executed.
***********************************************************************
****** ******
****** CPUDIAG ******
****** ******
****** (C) Copyright Hewlett-Packard Co 2000 ******
****** All Rights Reserved ******
****** ******
****** This program may only be used by HP support personnel and ******
****** those customers with the appropriate Class license or ******
****** Node license for systems specified by the license. HP ******
****** shall not be liable for any damages resulting from misuse ******
****** or unauthorized use of this program. This program ******
****** remains the property of HP. ******
****** ******
****** Version XX.XX.XX ******
****** ******
***********************************************************************
Type HELP for command information.
STARTING EXECUTION OF CPUDIAG
SECTION 001
SECTION 002
SECTION 003
END OF LOOP 1.
RUN COMPLETED.
ODE> cpudiag cr Select cpudiag.
Notice, the banner is only printed on first-time initialization or reset.
CPUDIAG> help cr
CPUDIAG Help Notice the TC commands follow TM commands.
Commands
--------
DIAGINFO -- Display information about LDIAG
SECTION -- Sets/Displays current test sections to execute
UP -- Test only one processor (the BSP)
MP -- Test all processors in the system
SEED -- Sets the default seed value to be used
PROC -- Selects which processors to test
PSTAT -- Displays information on processors to test
BREAK -- Sets breakpoints in diagnostic
MASTER -- Selects which cpu will play the master role in the
Multi-processor tests
CREG -- Displays selected control and application registers
ODE Commands Available from CPUDIAG
Basic Commands
--------------
HELP -- Prints detailed information to the screen, when
"help command" or "help var" is typed
LS -- List modules available on boot medium
Module_Name -- Load and initialize a module by typing its name
(For more help, type "help module_name")
RUN -- Run a module (after setting desired environment variables)
Control-Y|Control-C -- Abort an ODE command; pause a module run
RESUME -- Restart a paused module
DISPLOG -- After running a module, display contents of a log
EXIT -- Return to next higher level prompt
Environmental Variables
-----------------------
SHOWSTATE -- Display the value of the following environment variables:
LOOP -- Run a test this many times
ERRPRINT [ON|OFF] -- Print low-level error messages to console
(primarily for manufacturing use)
ERRNUM [ON|OFF] -- Print one-line, numbered errors to the console
ERRPAUSE [ON|OFF] -- Pause module upon error detection
ERRONLY [ON|OFF] -- Print ONLY error messages; disable non-error
and isolation message printing
INFOPRINT [ON|OFF] -- Print informational messages to the console
ISOPRINT [ON|OFF] -- Print fault isolation messages to the
console
ISOPAUSE [ON|OFF] -- Pause module when isolation message is
generated
LOGSIZE -- Set the size of a message log
DEFAULT -- Reset environment variables to default state
CPUDIAG> help section cr
SECTION {integer: 0..3 | integer integer | integer/integer |
[integer] [integer/integer] }. This command sets a 4 bit logical
integer bit mask. Each bit corresponds to a test section in the
diagnostic. For each bit that is set a test section is executed.
Examples: SECTION 3 sets bit three and clears all other bits. SECTION
1 3 sets bits one and three and clears all other bits. SECTION 1/3 is
equivalent to SECTION 1 2 3.
CPUDIAG> section 2 cr
CPUDIAG> loop 2 cr Loop twice on TM
CPUDIAG> run cr
STARTING EXECUTION OF CPUDIAG
SECTION 002
END OF LOOP 1.
STARTING EXECUTION OF CPUDIAG
SECTION 002
END OF LOOP 2.
RUN COMPLETED.
CPUDIAG> exit cr
ODE> exit cr Back to TC prompt
fs0:\efi\diag> Back to EFI prompt
2. Erroneous command example: The following
example shows three errors detected by the TC. The prompt is the
prompt of the TC.
ODE> fumblinG fIngers cr
INVALID COMMAND: COMMAND = FUMBLING Notice the case change.
ODE> load cr
MISSING PARAMETER: COMMAND = LOAD
ODE> load !4 cr
INVALID PARAMETER: COMMAND = LOAD !4
ODE> exit cr
fs0:\efi\diag> New prompt.
3. TM error detection example: The following
example shows one error detected by the TM (cpudiag). Pay close
attention to the prompt change. In this example, ERRPRINT is on,
ERRPAUSE is on, and this TM implements a command that dumps the
state of the general registers (REGISTER). This example begins with
only ODE loaded.
ODE> run cpudiag cr The TM is executed.
***********************************************************************
****** ******
****** CPUDIAG ******
****** ******
****** (C) Copyright Hewlett-Packard Co 1992 ******
****** All Rights Reserved ******
****** ******
****** This program may only be used by HP support personnel and ******
****** those customers with the appropriate Class license or ******
****** Node license for systems specified by the license. HP ******
****** shall not be liable for any damages resulting from misuse ******
****** or unauthorized use of this program. This program ******
****** remains the property of HP. ******
****** ******
****** Version XX.XX.XX ******
****** ******
***********************************************************************
Type HELP for command information.
STARTING EXECUTION OF CPUDIAG
SECTION 001
ERROR 002 DETECTED IN SECTION 001 WHILE TESTING THE CPU
General register 8 was 0x555555a5 should be 0x55555555.
CPUDIAG PAUSED> proc cr The prompt changes when paused.
The user enters a TM command
CPUDIAG PAUSED> resume cr
SECTION 002
SECTION 003
CPUDIAG DETECTED 1 HARDWARE ERROR
END OF LOOP 1.
RUN COMPLETED
ODE>
4. Multiple TMs invocation: The following
example shows two TMs being run. The two TMs are cpudiag and
memdiag; they both exist in the current directory. This example
begins with ODE loaded.
ODE> loop 2;run cpudiag memdiag cr These TMs will be looped
on twice.
***********************************************************************
****** ******
****** CPUDIAG ******
****** ******
****** (C) Copyright Hewlett-Packard Co 2000 ******
****** All Rights Reserved ******
****** *****
****** This program may only be used by HP support personnel and ******
****** those customers with the appropriate Class license or ******
****** Node license for systems specified by the license. HP ******
****** shall not be liable for any damages resulting from misuse ******
****** or unauthorized use of this program. This program ******
****** remains the property of HP. ******
****** ******
****** Version XX.XX.XX ******
****** ******
***********************************************************************
Type HELP for command information.
STARTING EXECUTION OF CPUDIAG
SECTION 001
SECTION 002
SECTION 003
***********************************************************************
****** ******
****** MEMDIAG ******
****** ******
****** (C) Copyright Hewlett-Packard Co 2000 ******
****** All Rights Reserved ******
****** ******
****** This program may only be used by HP support personnel and ******
****** those customers with the appropriate Class license or ******
****** Node license for systems specified by the license. HP ******
****** shall not be liable for any damages resulting from misuse ******
****** or unauthorized use of this program. This program ******
****** remains the property of HP. ******
****** ******
****** Version XX.XX.XX ******
****** ******
***********************************************************************
Type HELP for command information.
STARTING EXECUTION OF MEMDIAG
SECTION 001
SECTION 002
SECTION 003
END OF LOOP 1.
STARTING EXECUTION OF CPUDIAG
SECTION 001
SECTION 002
SECTION 003
STARTING EXECUTION OF MEMDIAG
SECTION 001
SECTION 002
SECTION 003
END OF LOOP 2.
RUN COMPLETED.
ODE> exit cr Returns to EFI
fs0:\efi\diag>
![[owl3000.gif]](../../img/owl3000.gif)
![[3khat16.ico]](../../img/3khat16.ico)
3kRanger![[archive16.gif]](../../img/archive16.gif "Wayback Archive")