Running ODE Tools on Integrity Systems and Itanium Worksations
Diag documents | |
 Complete PDF | |
| Table of Contents | |
| Index |
This section shows the output of tools run on Integrity Systems and Itanium worksations systems. The complementary tools for HP 9000 systems will produce similar results. The following examples are provided:
Loading and running a test module.
Using the two test modules together.
Viewing an error detected by a test module.
Obtaining a list of the tools supported by your platform.
Examples that show the ODE output for various invalid commands.
The example in this section shows the following information:
The ODE startup banner
Running the test module cpudiag for the first time.
Running cpudiag for a second time (the banner information is not displayed).
Running the cpudiag help command
Setting and using environmental variables.
Exiting cpudiag and ODE
Example 4-1 Loading ODE and Running a Test Module
fs0:\EFI\HP\DIAG\ODE>ode
***********************************************************************
****** ******
****** OFFLINE DIAGNOSTIC ENVIRONMENT ******
****** ******
****** (C) Copyright Hewlett-Packard Co 2006 ******
****** All Rights Reserved ******
****** ******
****** ******
****** TC Version XX.XX.XX ******
****** SysLib Version XX.XX.XX ******
****** ******
****** ******
***********************************************************************
Type HELP for command information.
ODE> run cpudiag
***********************************************************************
****** ******
****** CPUDIAG ******
****** ******
****** (C) Copyright Hewlett-Packard Co 2006 ******
****** 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
CPUDIAG> help
CPUDIAG Help
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
CPUDIAG> loop 2
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
ODE> exit
fs0:\efi\diag> |
The example in this section shows two test modules, cpudiag and memdiag , being run.
Example 4-2 Running Multiple Test Modules
ODE> loop 2;run cpudiag memdiag *********************************************************************** ****** ****** ****** CPUDIAG ****** ****** ****** ****** (C) Copyright Hewlett-Packard Co 2006 ****** ****** 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 2006 ****** ****** 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 fs0:\efi\diag> |
The following example shows an error detected by the test module cpudiag. In the example, ERRPRINT is on, ERRPAUSE is on, and cpudiag implements a command that dumps the state of the general registers (REGISTER). This example begins with only ODE loaded. Notice the changes in the command prompt:
Example 4-3 Error Detection
ODE> run cpudiag *********************************************************************** ****** ****** ****** CPUDIAG ****** ****** ****** ****** (C) Copyright Hewlett-Packard Co 2006 ****** ****** 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 CPUDIAG PAUSED> resume SECTION 002 SECTION 003 CPUDIAG DETECTED 1 HARDWARE ERROR END OF LOOP 1. RUN COMPLETED ODE> |
Some ODE tools cannot be used on all platforms. Attempting to use an unsupported tool will generate an error message. For example:
Example 4-4 Using an Unsupported Tool
ODE> WDIAG The Hversion = 88c0. The Sversion = 491. UUT_MODEL = 88c --------------------------------------------------------------------- WARNING: THIS PROCESSOR MODEL 88c IS INCOMPATIBLE WITH THIS DIAGNOSTIC. --------------------------------------------------------------------- FATAL SOFTWARE ERROR !! EXECUTION OF WDIAG MAY PRODUCE UNDEFINED RESULTS ERROR: Initialization of WDIAG failed |
If you are uncertain about which tools you can use on your system, specify the ls command at the ODE prompt to obtain information about the tools your system supports. For example:
Example 4-5 Determining the System-Supported Tools
ODE> ls
Modules on this boot media are:
filename type size created description
-----------------------------------------------------------------------------
README2 TM 345 06/03/14 64 bit version that displays README file
MAPPER2 TM 800 06/03/14 64 bit version of the system mapping utility
MEM2 TM 1604 06/03/14 64 bit Memory diagnostic
MAKODIAG TM 9601 06/03/14 CPU diagnostic for PA8800 processors
PCIUTIL TM 942 06/03/14 PCI HBA Firmware Update Utility |
Common errors such as specifying an unknown command, a misspelled command, or an inaccurate parameter will cause ODE to generate error messages. Example 4-6 shows three such errors.
|
Chapter 4 Performing Common ODE Tasks |
Running ODE Tools on HP 9000 Systems |