CHAPTER 4

Troubleshooting Procedures

This chapter describes how to troubleshoot possible hardware problems and

includes suggested corrective actions.

This chapter contains the following topics:

■ Section 4.1 “Power-On Failure” on page 4-1
■ Section 4.2 “Video Output Failure” on page 4-2
■ Section 4.3 “Hard Drive or CD-ROM Drive Failure” on page 4-3
■ Section 4.4 “Power Supply Test” on page 4-4
■ Section 4.5 “DIMM Failure” on page 4-7
■ Section 4.6 “OpenBoot PROM On-Board Diagnostics” on page 4-7
■ Section 4.7 “OpenBoot Diagnostics” on page 4-12

4.1 Power-On Failure

This section provides examples of power-on failure symptoms and suggested
actions.

Symptom
The system unit does not power up when the keyboard standby key is pressed.

Action
Check the keyboard connection. Ensure that the keyboard is properly connected
to the system unit. Check the AC power cord. Ensure that the AC power cord is
properly connected to the system unit and to the wall receptacle. Verify that the

4-1
 power on/off switch is set to on.Verify that the wall receptacle is supplying AC
power to the system unit. Check the voltage select switch. Verify that the voltage
select switch is set properly.

Press the front panel standby switch. If the system unit powers on, the keyboard
may be defective or the system unit is unable to accept the keyboard power-on
signal. Power off the system unit and press the keyboard standby key again. If the
system unit powers on, no further action is required. If the system unit does not
power on, the CPU module may not be properly seated. Inspect the CPU module
for proper seating. If the system unit powers on, no further action is required. If
the system unit does not power on, the keyboard may be defective. Connect a
spare Sun Type-5 keyboard to the system unit and press the standby key.

If the wall receptacle AC power has been verified, the CPU module is properly
seated, and a spare Sun Type-5 keyboard has been connected to the system unit
and the standby key has been pressed but the system unit does not power up, the
system unit power supply may be defective. See Section 4.4 “Power Supply Test”
on page 4-4.

Symptom
The system unit attempts to power on but does not boot or initialize the monitor.

Action
Press the keyboard standby key and watch the keyboard. The keyboard LEDs
should light briefly and a tone from the keyboard should be heard. If a tone is not
heard or if the keyboard LEDs do not light briefly, the system unit power supply
may be defective. See Section 4.4 “Power Supply Test” on page 4-4. If a keyboard
tone is heard and the keyboard LEDs light briefly but the system unit still fails to
initialize, see Section 3.8 “Initializing Motherboard POST” on page 3-24.

4.2 Video Output Failure

This section provides video output failure symptoms and suggested action.

Symptom
The video does not display at the system monitor.

Action
Check the monitor AC power cord. Ensure that the AC power cord is connected
to the monitor and to the wall receptacle. Verify that the wall receptacle is
supplying AC power to the monitor. Check the video cable connection between
the monitor and the UPA graphics card output port (Ultra 10 only) or the video

4-2 Sun Ultra 5/10 Service Manual • November 1998

 output connector at the rear of the system unit. Check that the CPU module is
properly seated. If the AC connection to the monitor is correct, the video cable is
correctly connected, and the CPU module is properly seated, the system monitor,
UPA graphics card, or motherboard video chip may be defective.

4.3 Hard Drive or CD-ROM Drive Failure

This section provides hard drive and CD-ROM drive failure symptoms and
suggested actions.

Symptom
A hard drive read, write, or parity error is reported by the operating system or
customer application.

A CD-ROM drive read error or parity error is reported by the operating system or
customer application.

Action
Replace the drive indicated by the failure message. The operating system
identifies the internal drives as identified in the following table.

TABLE 4-1 Internal Drives Identification

Operating System Address Drive Physical Location and Target

c0t0d0s# Hard drive (Ultra 5) or rear hard drive (Ultra 10),

target 0
c0t1d0s# Front hard disk (Ultra 10), target 1

c0t6d0s# CD-ROM drive, target 6 (optional)

Note – The # symbol in the operating system address examples may be a numeral
between 0 and 7 that describes the slice or partition on the drive.

Symptom
Hard drive or CD-ROM drive fails to respond to commands.

Action
Test the drive response to the probe-ide command as follows:

Chapter 4 Troubleshooting Procedures 4-3

 Note – To bypass POST, type setenv diag-switch? false at the ok prompt.

At the system ok prompt:

ok% reset-all
ok% probe-ide

If the hard drive responds correctly to probe-ide command, the message identified
in CODE EXAMPLE 4-4 is displayed. If the drive responds and a message is displayed,
the system EIDE controller has successfully probed the device. This is an indication
that the motherboard is operating correctly. If an optional hard drive is installed
(Ultra 10 only) and one drive does not respond to the EIDE controller probe but the
other does, replace the unresponsive drive. If the probe-ide test fails to show the
device in the message, replace the drive (see Section 9.1 “Diskette Drive” on
page 9-1). If replacing the hard drive does not correct the problem, replace the
motherboard.

4.4 Power Supply Test

The section describes how to test the power supply. FIGURE 4-1 and TABLE 4-2 identify
power supply connector J17. FIGURE 4-2 and TABLE 4-3 identify power supply
connector J20.

1. Power off the system unit.

See Section 6.2 “Powering Off the System Unit” on page 6-4.

2. Remove the top cover.

See Section 7.1 “Removing the Top Cover” on page 7-1.

3. Remove the PCI card from riser board connector 2 (adjacent to power supply), if
necessary. Disconnect the ribbon cables from motherboard to expose connectors
J17 and J20 (J20 is used in Ultra 10 only).

4. Power on the system unit.

5. Using a digital voltage meter (DVM), check the power supply output voltages as
follows:

Note – Power supply connectors J17 and J20 must remain connected to the
motherboard.

4-4 Sun Ultra 5/10 Service Manual • November 1998

 a. With the negative probe of the DVM placed on a connector ground (Gnd) pin,
position the positive probe on each power pin.

b. Verify voltage and signal availability as listed in TABLE 4-2 and TABLE 4-3.

6. If any power pin signal is not present with the power supply active and properly
connected to the motherboard, replace the power supply.

10 1

20 11

FIGURE 4-1 Power Supply Connector J17 Pin Configuration

TABLE 4-2 Power Supply Connector J17 Pin Assignments

Pin Signal Description

1 +3.3V +3.3 VDC

2 +3.3V +3.3 VDC

3 Gnd Chassis ground

4 +5V +5 VDC

5 Gnd Chassis ground

6 +5V +5 VDC

7 Gnd Chassis ground

8 PWR_OK Power okay

9 5VSB

10 +12V +12 VDC

11 +3.3V +3.3 VDC

12 -12V -12 VDC

13 Gnd Chassis ground

14 PS_ON Power supply on

Chapter 4 Troubleshooting Procedures 4-5

 TABLE 4-2 Power Supply Connector J17 Pin Assignments (Continued)

Pin Signal Description

15 Gnd Chassis ground

16 Gnd Chassis ground

17 Gnd Chassis ground

18 -5V -5 VDC

19 +5V +5 VDC

20 +5V +5 VDC

6 1

FIGURE 4-2 Power Supply Connector J20 Pin Configuration (Ultra 10 only)

TABLE 4-3 Power Supply Connector J20 Pin Assignments

Pin Signal Description

1 Gnd Chassis ground

2 Gnd Chassis ground
3 SEN_COM Sense common
4 SEN_+3.3V Sense 3.3 VDC
5 +3.3V +3.3 VDC
6 +3.3V +3.3 VDC

4-6 Sun Ultra 5/10 Service Manual • November 1998

4.5 DIMM Failure
At times, the operating system, diagnostic program, or POST may not display a
DIMM location (U number) as part of a memory error message. In this situation, the
only available information is a physical memory address and failing byte (or bit).
The following table lists physical memory addresses to locate a defective DIMM.

TABLE 4-4 DIMM Physical Memory Address

DIMM Pair
DIMM Slot (non-interleave)

DIMM0 00000000 - 0fffffff

DIMM1
DIMM2 10000000 - 1fffffff
DIMM3

4.6 OpenBoot PROM On-Board Diagnostics

The following sections describe the OpenBoot PROM (OBP) on-board diagnostics. To
execute the OBP on-board diagnostics, the system must be at the ok prompt. The
OBP on-board diagnostics are listed as follows:
■ Section 4.6.1 “Watch-Clock Diagnostic” on page 4-7
■ Section 4.6.2 “Watch-Net and Watch-Net-All Diagnostics” on page 4-8
■ Section 4.6.3 “Probe-IDE Diagnostic” on page 4-9
■ Section 4.6.4 “Test alias name, device path, -All Diagnostic” on page 4-10
■ Section 4.6.5 “UPA Graphics Card (Ultra 10 Only)” on page 4-11

4.6.1 Watch-Clock Diagnostic

The watch-clock diagnostic reads a register in the NVRAM/TOD chip and displays
the result as a seconds counter. During normal operation, the seconds counter
repeatedly increments from 0 to 59 until interrupted by pressing any key on the Sun

Chapter 4 Troubleshooting Procedures 4-7

 Type-5 keyboard. The watch-clock diagnostic is initialized by typing the
watch-clock command at the ok prompt. The following code example identifies
the watch-clock diagnostic output message.

CODE EXAMPLE 4-1 Watch-Clock Diagnostic Output Message

ok watch-clock
Watching the 'seconds' register of the real time clock chip.
It should be 'ticking' once a second.
Type any key to stop.
49
ok

4.6.2 Watch-Net and Watch-Net-All Diagnostics

The watch-net and watch-net-all diagnostics monitor Ethernet packets on the
Ethernet interfaces connected to the system. Good packets received by the system
are indicated by a period (.). Errors such as the framing error and the cyclic
redundancy check (CRC) error are indicated with an X and an associated error
description. The watch-net diagnostic is initialized by typing the watch-net
command at the ok prompt and the watch-net-all diagnostic is initialized by typing
the watch-net-all command at the ok prompt. The following code example
identifies the watch-net diagnostic output message. CODE EXAMPLE 4-3 identifies the
watch-net-all diagnostic output message.

CODE EXAMPLE 4-2 Watch-Net Diagnostic Output Message

ok watch-net
Hme register test --- succeeded.
Internal loopback test -- succeeded.
Transceiver check -- Using Onboard Transceiver - Link Up.
passed
Using Onboard Transceiver - Link Up.
Looking for Ethernet Packets.
'.' is a Good Packet. 'X' is a Bad Packet.
Type any key to stop.
..................................................
................................................................
................................................................
........................................................
ok

4-8 Sun Ultra 5/10 Service Manual • November 1998

 CODE EXAMPLE 4-3 Watch-Net-All Diagnostic Output Message
ok watch-net-all
/pci@1f,0/pci@1,1/network@1,1
Hme register test --- succeeded.
Internal loopback test -- succeeded.
Transceiver check -- Using Onboard Transceiver - Link Up.
passed
Using Onboard Transceiver - Link Up.
Looking for Ethernet Packets.
'.' is a Good Packet. 'X' is a Bad Packet.
Type any key to stop.
........
................................................................
................................................................
................................................................
....................................
ok

4.6.3 Probe-IDE Diagnostic

The probe-ide diagnostic transmits an inquiry command to internal and external IDE
devices connected to the system unit on-board IDE interface. If the EIDE device is
connected and active, the target address, unit number, device type, and
manufacturer name is displayed. The probe-ide diagnostic is initialized by typing
the probe-ide command at the ok prompt. The following code example identifies
the probe-ide diagnostic output message.

CODE EXAMPLE 4-4 Probe-IDE Diagnostic Output Message

ok probe-ide
Device 0 ( Primary Master )
ATA Model: ST34342A

Device 1 ( Primary Slave )

ATA Model: ST34342A

Device 2 ( Secondary Master )

Removable ATAPI Model: CRD-8160B

Device 3 ( Secondary Slave )

Removable ATAPI Model:

ok

Chapter 4 Troubleshooting Procedures 4-9

4.6.4 Test alias name, device path, -All Diagnostic
The test diagnostic, when combined with a device alias or device path, enables a
device self-test diagnostic program. If a device has no self-test program, the
message: No selftest method for device name is displayed. To enable
the self-test program for a device, type the test command followed by the device
alias or device path name.

The following code example identifies the test diagnostic output message. Test
diagnostics are initialized by typing the test alias name or device path command at
the ok prompt. TABLE 4-5 lists the types of tests that can be used, a brief description
of each test, and preparation.

Note – The diskette drive (floppy) is selected as the test alias name example.

CODE EXAMPLE 4-5 Test Diagnostic Output Message

ok test floppy

Testing floppy disk system. A formatted disk should be in the

drive.
Test succeeded.

ok

TABLE 4-5 Selected OBP On-Board Diagnostic Tests

Type of Test Description Preparation

test screen Tests system video graphics hardware and Diag-switch? NVRAM parameter must
monitor be true for the test to execute.
test floppy Tests diskette drive response to commands A formatted diskette must be inserted into
the diskette drive.
test net Performs internal/external loopback test of An Ethernet cable must be attached to the
the system auto-selected Ethernet interface system and to an Ethernet tap or hub or the
external loopback test fails.

4-10 Sun Ultra 5/10 Service Manual • November 1998

 TABLE 4-5 Selected OBP On-Board Diagnostic Tests (Continued)

Type of Test Description Preparation

test ttya Outputs an alphanumeric test pattern on A terminal must be connected to the port
test ttyb the system serial ports: ttya, serial port A; being tested to observe the output.
ttyb, serial port B
test Executes the keyboard selftest. Four keyboard LEDs should flash once and
keyboard a message is displayed: Keyboard
Present.
test -all Sequentially test system-configured devices Tests are sequentially executed in device-
containing selftest. tree order (viewed with the show-devs
command).

4.6.5 UPA Graphics Card (Ultra 10 Only)

The UPA graphics card contains a built-in diagnostic test that is enabled through the
OBP. The UPA graphics card built-in diagnostic test verifies basic graphics
functionality without rebooting the operating system software.

To execute the built-in diagnostic test, the system must be at the ok prompt.

To initilize the UPA graphics card diagnostic:

1. At the ok prompt, type:

ok% setenv diag-switch? true

diag-switch? = true
ok% setenv diag-switch? true

2. At the ok prompt, type:

ok% test screen

Verifying Console Mode for Frame Buffer Board
This will take a few minutes
Verifying Frame Buffer Memory used for console mode
This will take about two minutes
FFB Frame Buffer functional test passed
ok%

Chapter 4 Troubleshooting Procedures 4-11

 3. When the UPA graphics card on-board diagnostics are completed, type:

ok% setenv diag-switch? false

diag-switch? = false

4.7 OpenBoot Diagnostics

The OpenBoot diagnostic (OBDiag) is a menu-driven diagnostic tool that verifies:
■ Internal I/O system
■ Ethernet
■ Keyboard
■ Mouse
■ Diskette drive (floppy)
■ Parallel port
■ Serial ports
■ NVRAM
■ Audio
■ EIDE
■ Video

OBDiag performs root-cause failure analysis on the referenced devices by testing

internal registers, confirming subsystem integrity, and verifying device functionality.

Note – The OBDiag test result data captured in the following code examples
represent the test result data that is output when the system being tested is
connected to a remote shell window through a tip connection. When the system
being tested is tested in a stand-alone configuration, the test result data may differ.

4.7.1 Starting the OBDiag Menu

1. At the ok prompt, type:

ok% setenv mfg-mode on

mfg-mode = on

4-12 Sun Ultra 5/10 Service Manual • November 1998

2. At the ok prompt, type:

ok% setenv diag-switch? true

diag-switch? = true

3. At the ok prompt, type:

ok% setenv auto-boot? false

auto-boot? = false

4. At the ok prompt, type:

ok% reset-all

5. Verify that the platform resets (CODE EXAMPLE 4-6).

CODE EXAMPLE 4-6 Reset Verification

ok setenv mfg-mode on
mfg-mode = on
ok setenv diag-switch? true
diag-switch? = true
ok setenv auto-boot? false
auto-boot? = false
ok reset-all
Resetting...

Software Power ON

@(#) Sun Ultra 5/10 UPA/PCI 3.11 Version 9 created 1998/03/06

10:31
Clearing E$ Tags Done
Clearing I/D TLBs Done
Probing Memory Done
MEM BASE = 0000.0000.2000.0000
MEM SIZE = 0000.0000.1000.0000
11-Column Mode Enabled
MMUs ON
Copy Done
PC = 0000.01ff.f000.1ffc
PC = 0000.0000.0000.2040
Decompressing into Memory Done
Size = 0000.0000.0006.e160

Chapter 4 Troubleshooting Procedures 4-13

 CODE EXAMPLE 4-6 Reset Verification (Continued)
ttya initialized
Reset Control: BXIR:0 BPOR:0 SXIR:0 SPOR:1 POR:0
UltraSPARC-IIi 2-2 module
Probing Memory Bank #0 256 + 256: 512 Megabytes
Probing Memory Bank #2 0 + 0: 0 Megabytes
Probing UPA Slot at 1e,0 SUNW,ffb

Probing /pci@1f,0/pci@1,1 at Device 1 pci108e,1000 network

Probing /pci@1f,0/pci@1,1 at Device 2 SUNW,m64B
Probing /pci@1f,0/pci@1,1 at Device 3 ide disk cdrom
Probing /pci@1f,0/pci@1 at Device 1 pci
Probing /pci@1f,0/pci@1/pci@1 at Device 0 pci108e,1000 SUNW,hme
Probing /pci@1f,0/pci@1/pci@1 at Device 1 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device 2 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device 3 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device 4 SUNW,isptwo sd st
Probing /pci@1f,0/pci@1/pci@1 at Device 5 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device 6 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device 7 Nothing there

Probing /pci@1f,0/pci@1/pci@1 at Device 8 Nothing there

Probing /pci@1f,0/pci@1/pci@1 at Device 9 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device a Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device b Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device c Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device d Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device e Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device f Nothing there

Probing /pci@1f,0/pci@1 at Device 2 Nothing there

Probing /pci@1f,0/pci@1 at Device 3 Nothing there
Probing /pci@1f,0/pci@1 at Device 4 Nothing there
Reset Control: BXIR:0 BPOR:0 SXIR:0 SPOR:1 POR:0
UltraSPARC-IIi 2-2 module
Probing Memory Bank #0 256 + 256: 512 Megabytes
Probing Memory Bank #2 0 + 0: 0 Megabytes
Probing UPA Slot at 1e,0 SUNW,ffb
Probing /pci@1f,0/pci@1,1 at Device 1 pci108e,1000 network
Probing /pci@1f,0/pci@1,1 at Device 2 SUNW,m64B
Probing /pci@1f,0/pci@1,1 at Device 3 ide disk cdrom
Probing /pci@1f,0/pci@1 at Device 1 pci
Probing /pci@1f,0/pci@1/pci@1 at Device 0 pci108e,1000 SUNW,hme
Probing /pci@1f,0/pci@1/pci@1 at Device 1 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device 2 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device 3 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device 4 SUNW,isptwo sd st
Probing /pci@1f,0/pci@1/pci@1 at Device 5 Nothing there

4-14 Sun Ultra 5/10 Service Manual • November 1998

 CODE EXAMPLE 4-6 Reset Verification (Continued)
Probing /pci@1f,0/pci@1/pci@1 at Device 6 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device 7 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device 8 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device 9 Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device a Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device b Nothing there

Probing /pci@1f,0/pci@1/pci@1 at Device c Nothing there

Probing /pci@1f,0/pci@1/pci@1 at Device d Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device e Nothing there
Probing /pci@1f,0/pci@1/pci@1 at Device f Nothing there

Probing /pci@1f,0/pci@1 at Device 2 Nothing there

Probing /pci@1f,0/pci@1 at Device 3 Nothing there
Probing /pci@1f,0/pci@1 at Device 4 Nothing there

Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 300MHz), No Keyboard

OpenBoot 3.11, 512 MB memory installed, Serial #9337777.
Ethernet address 8:0:20:8e:7b:b1, Host ID: 808e7bb1.

ok

6. At the ok prompt, type obdiag. Verify that the OBDiag menu is displayed
(CODE EXAMPLE 4-7).

7. At the OBDiag menu prompt, type 16 to enable toggle script-debug messages.

Note – Enabling the toggle script-debug messages allow verbose test message
displays.

8. At the OBDiag menu prompt, type 18 to disable external loopback test.

CODE EXAMPLE 4-7 OBDiag Menu

ok obdiag
stdin: fffe2008
stdout: fffe2010
loading code into: /pci@1f,0/pci@1,1/ebus@1
loading code into: /pci@1f,0/pci@1,1/ebus@1/eeprom@14,0
loading code into: /pci@1f,0/pci@1,1/ebus@1/ecpp@14,3043bc
loading code into: /pci@1f,0/pci@1,1/ebus@1/su@14,3062f8
loading code into: /pci@1f,0/pci@1,1/ebus@1/se@14,400000
loading code into: /pci@1f,0/pci@1,1/network@1,1
loading code into: /pci@1f,0/pci@1,1/ebus@1/fdthree@14,3023f0

Chapter 4 Troubleshooting Procedures 4-15

 CODE EXAMPLE 4-7 OBDiag Menu (Continued)
loading code into: /pci@1f,0/pci@1,1/ebus@1/
SUNW,CS4231@14,200000
loading code into: /pci@1f,0/pci@1,1/ide@3
loading code into: /pci@1f,0/pci@1,1/ide@3/disk
loading code into: /pci@1f,0/pci@1,1/ide@3/cdrom
loading code into: /pci@1f,0/pci@1,1/SUNW,m64B@2
Debugging enabled

OBDiag Menu

0..... PCI/Cheerio
1..... EBUS DMA/TCR Registers
2..... Ethernet
3..... Keyboard
4..... Mouse
5..... Floppy
6..... Parallel Port
7..... Serial Port A
8..... Serial Port B
9..... NVRAM
10..... Audio
11..... EIDE
12..... Video
13..... All Above
14..... Quit
15..... Display this Menu
16..... Toggle script-debug
17..... Enable External Loopback Tests
18..... Disable External Loopback Tests

Enter (0-13 tests, 14 -Quit, 15 -Menu) ===>

4.7.2 OBDiags
The OBDiags are described in the following sections:
■ Section 4.7.2.1 “PCI/PCIO” on page 4-17
■ Section 4.7.2.2 “EBus DMA/TCR Registers” on page 4-19
■ Section 4.7.2.3 “Ethernet” on page 4-19
■ Section 4.7.2.4 “Keyboard” on page 4-20
■ Section 4.7.2.5 “Mouse” on page 4-21
■ Section 4.7.2.6 “Floppy” on page 4-21
■ Section 4.7.2.7 “Parallel Port” on page 4-22
■ Section 4.7.2.8 “Serial Port A” on page 4-22
■ Section 4.7.2.9 “Serial Port B” on page 4-24

4-16 Sun Ultra 5/10 Service Manual • November 1998

 ■ Section 4.7.2.10 “NVRAM” on page 4-25
■ Section 4.7.2.11 “Audio” on page 4-25
■ Section 4.7.2.12 “EIDE” on page 4-26
■ Section 4.7.2.13 “Video” on page 4-26
■ Section 4.7.2.14 “All Above” on page 4-27

4.7.2.1 PCI/PCIO
The PCI/PCIO diagnostic performs the following:

1. vendor_ID_test – Verifies the PCIO ASIC vender ID is 108e.

2. device_ID_test – Verifies the PCIO ASIC device ID is 1000.

3. mixmode_read – Verifies the PCI configuration space is accessible as

half-word bytes by reading the EBus2 vender ID address.

4. e2_class_test – Verifies the address class code. Address class codes include
bridge device (0 x B, 0 x 6), other bridge device (0 x A and 0 x 80), and
programmable interface (0 x 9 and 0 x 0).

5. status_reg_walk1 – Performs walk-one test on status register with mask

0 x 280 (PCIO ASIC is accepting fast back-to-back transactions, DEVSEL timing is
0 x 1).

6. line_size_walk1 – Performs tests a through e. latency_walk1 – Performs

walk one test on latency timer.

7. line_walk1 – Performs walk one test on interrupt line.

8. pin_test – Verifies interrupt pin is logic-level high (1) after reset.

The following code example identifies the PCI/PCIO output message.

CODE EXAMPLE 4-8 PCI/PCIO Output Message

Enter (0-12 tests, 13 -Quit, 14 -Menu) ===> 0

TEST='all_pci/PCIO_test'
SUBTEST='vendor_id_test'
SUBTEST='device_id_test'
SUBTEST='mixmode_read'
SUBTEST='e2_class_test'
SUBTEST='status_reg_walk1'
SUBTEST='line_size_walk1'
SUBTEST='latency_walk1'
SUBTEST='line_walk1'

Chapter 4 Troubleshooting Procedures 4-17

 CODE EXAMPLE 4-8 PCI/PCIO Output Message (Continued)
SUBTEST='pin_test'
Enter (0-12 tests, 13 -Quit, 14 -Menu) ===>

4-18 Sun Ultra 5/10 Service Manual • November 1998

4.7.2.2 EBus DMA/TCR Registers
The EBus DMA/TCR registers diagnostic performs the following:

1. dma_reg_test – Performs a walking ones bit test for control status register,
address register, and byte count register of each channel. Verifies that the control
status register is set properly.

2. dma_func-test – Validates the DMA capabilities and FIFOs. Test is executed in

a DMA diagnostic loopback mode. Initializes the data of transmitting memory
with its address, performs a DMA read and write, and verifies that the data
received is correct. Repeats for four channels.

The following code example identifies the EBus DMA/TCR registers output
message.

CODE EXAMPLE 4-9 EBus DMA/TCR Registers Output Message

Enter (0-12 tests, 13 -Quit, 14 -Menu) ===> 1

TEST='all_dma/ebus_test'
SUBTEST='dma_reg_test'
SUBTEST='dma_func_test'
Enter (0-12 tests, 13 -Quit, 14 -Menu) ===>

4.7.2.3 Ethernet
The Ethernet diagnostic performs the following:

1. my_channel_reset – Resets the Ethernet channel.

2. hme_reg_test – Performs Walk1 on the following registers set: global register 1,

global register 2, bmac xif register, bmac tx register, and the mif register.

3. MAC_internal_loopback_test – Performs Ethernet channel engine internal

loopback.

4. 10_mb_xcvr_loopback_test – Enables the 10Base-T data present at the

transmit MII data inputs to be routed back to the receive MII data outputs.

5. 100_mb_phy_loopback_test – Enables MII transmit data to be routed to the

MII receive data path.

6. 100_mb_twister_loopback_test – Forces the twisted-pair transceiver into

loopback mode.

Chapter 4 Troubleshooting Procedures 4-19

 The following code example identifies the Ethernet output message.

CODE EXAMPLE 4-10 Ethernet Output Message

Enter (0-13 tests, 14 -Quit, 15 -Menu) ===> 2

TEST=’ethernet_test’
Using Onboard Transceiver - Link Up.
SUBTEST=’my_channel_reset’
SUBTEST=’hme_reg_test’
SUBTEST=’global_reg1_test’
SUBTEST=’global_reg2_test’
SUBTEST=’bmac_xif_reg_test’
SUBTEST=’bmac_tx_reg_test’
SUBTEST=’mif_reg_test’
SUBTEST=’mac_internal_loopback_test’
SUBTEST=’10mb_xcvr_loopback_test’
SUBTEST=’100mb_phy_loopback_test’
SUBTEST=’100mb_twister_loopback_test’
Enter (0-13 tests, 14 -Quit, 15 -Menu) ===>

4.7.2.4 Keyboard
The keyboard diagnostic consists of an external and internal loopback. The external
loopback requires a passive loopback connector. The internal loopback verifies the
keyboard port by transmitting and receiving 128 characters.

The following code example identifies the keyboard output message.

CODE EXAMPLE 4-11 Keyboard Output Message

setenv Enter (0-13 tests, 14 -Quit, 15 -Menu) ===> 3

TEST=’keyboard_test’
SUBTEST=’internal_loopback’
Enter (0-13 tests, 14 -Quit, 15 -Menu) ===>

4-20 Sun Ultra 5/10 Service Manual • November 1998

4.7.2.5 Mouse
The mouse diagnostic performs a keyboard-to-mouse loopback.

The following code example identifies the mouse output message.

CODE EXAMPLE 4-12 Mouse Output Message

Enter (0-12 tests, 13 -Quit, 14 -Menu) ===> 4

TEST=’mouse_test’
SUBTEST=’mouse_loopback’

###OBDIAG_MFG_START###
TEST=’mouse_test’
STATUS=’FAILED’
SUBTEST=’mouse_loopback’
ERRORS=’1 ‘
TTF=’1656 ‘
SPEED=’295.99 MHz’
PASSES=’1 ‘
MESSAGE=’Error: Timeout receiving a character’
Enter (0-12 tests, 13 -Quit, 14 -Menu) ===>

4.7.2.6 Floppy
The floppy diagnostic verifies the diskette drive controller initialization. It also
validates the status of a selected disk drive and reads the diskette drive header.

The following code example identifies the floppy output message.

CODE EXAMPLE 4-13 Floppy Output Message

Enter (0-12 tests, 13 -Quit, 14 -Menu) ===> 5

TEST='floppy_test'
SUBTEST='floppy_id0_read_test'
Enter (0-12 tests, 13 -Quit, 14 -Menu) ===>

Chapter 4 Troubleshooting Procedures 4-21

4.7.2.7 Parallel Port
The parallel port diagnostic performs the following:

1. sio-passive-lb – Sets up the SuperIO configuration register to enable

extended/compatible parallel port select, then does a write 0, walk one, write 0 x
ff to the data register. It verifies the results by reading the status register.

2. dma_read – Enables ECP mode and ECP DMA configuration, and FIFO test
mode. Transfers 16 bytes of data from memory to the parallel port device and
then verifies the data is in TFIFO.

The following code example identifies the parallel port output message.

CODE EXAMPLE 4-14 Parallel Port Output Message

Enter (0-12 tests, 13 -Quit, 14 -Menu) ===> 6

TEST='parallel_port_test'
SUBTEST='dma_read'
Enter (0-12 tests, 13 -Quit, 14 -Menu) ===>

4.7.2.8 Serial Port A

The serial port A diagnostic invokes the uart_loopback test. This test transmits
and receives 128 characters and checks serial port A transaction validity.

The following code example identifies the serial port A output message.

CODE EXAMPLE 4-15 Serial Port A Output Message

Enter (0-12 tests, 13 -Quit, 14 -Menu) ===> 7

TEST='uarta_test'
BAUDRATE='1200'
SUBTEST='internal_loopback'
BAUDRATE='1800'
SUBTEST='internal_loopback'
BAUDRATE='2400'
SUBTEST='internal_loopback'
BAUDRATE='4800'
SUBTEST='internal_loopback'
BAUDRATE='9600'
SUBTEST='internal_loopback'

4-22 Sun Ultra 5/10 Service Manual • November 1998

CODE EXAMPLE 4-15 Serial Port A Output Message (Continued)
BAUDRATE='19200'
SUBTEST='internal_loopback'
BAUDRATE='38400'
SUBTEST='internal_loopback'
BAUDRATE='57600'
SUBTEST='internal_loopback'
BAUDRATE='76800'
SUBTEST='internal_loopback'
BAUDRATE='115200'
SUBTEST='internal_loopback'
BAUDRATE='153600'
SUBTEST='internal_loopback'
BAUDRATE='230400'
SUBTEST='internal_loopback'
BAUDRATE='307200'
SUBTEST='internal_loopback'
BAUDRATE='460800'
SUBTEST='internal_loopback'
Enter (0-12 tests, 13 -Quit, 14 -Menu) ===>

Note – The serial port A diagnostic will stall if the TIP line is installed on serial
port A. The following code example identifies the serial port A output message
when the TIP line is installed on serial port A.

CODE EXAMPLE 4-16 Serial Port A Output Message With TIP Line Installed

Enter (0-12 tests, 13 -Quit, 14 -Menu) ===> 7

TEST='uarta_test'
'UART A in use as console - Test not run.'
Enter (0-12 tests, 13 -Quit, 14 -Menu) ===>

Chapter 4 Troubleshooting Procedures 4-23

4.7.2.9 Serial Port B
The serial port B diagnostic is identical to the serial port A diagnostic.

The following code example identifies the serial port B output message.

Note – The serial port B diagnostic will stall if the TIP line is installed on serial
port B.

CODE EXAMPLE 4-17 Serial Port B Output Message

Enter (0-12 tests, 13 -Quit, 14 -Menu) ===> 8

TEST='uartb_test'
BAUDRATE='1200'
SUBTEST='internal_loopback'
BAUDRATE='1800'
SUBTEST='internal_loopback'
BAUDRATE='2400'
SUBTEST='internal_loopback'
BAUDRATE='4800'
SUBTEST='internal_loopback'
BAUDRATE='9600'
SUBTEST='internal_loopback'
BAUDRATE='19200'
SUBTEST='internal_loopback'
BAUDRATE='38400'

SUBTEST='internal_loopback'
BAUDRATE='57600'
SUBTEST='internal_loopback'
BAUDRATE='76800'
SUBTEST='internal_loopback'
BAUDRATE='115200'
SUBTEST='internal_loopback'
BAUDRATE='153600'
SUBTEST='internal_loopback'
BAUDRATE='230400'
SUBTEST='internal_loopback'
BAUDRATE='307200'
SUBTEST='internal_loopback'
BAUDRATE='460800'
SUBTEST='internal_loopback'
Enter (0-12 tests, 13 -Quit, 14 -Menu) ===>

4-24 Sun Ultra 5/10 Service Manual • November 1998

4.7.2.10 NVRAM
The NVRAM diagnostic verifies the NVRAM operation by performing a write and
read to the NVRAM.

The following code example identifies the NVRAM output message.

CODE EXAMPLE 4-18 NVRAM Output Message

Enter (0-12 tests, 13 -Quit, 14 -Menu) ===> 9

TEST='nvram_test'
SUBTEST='write/read_patterns'
SUBTEST='write/read_inverted_patterns'
Enter (0-12 tests, 13 -Quit, 14 -Menu) ===>

4.7.2.11 Audio
The audio diagnostic performs the following:

1. cs4231_test – Verifies the cs4231 internal registers.

2. Line-in to line-out external loopback.

3. Microphone to headphone external loopback.

The following code example identifies the audio output message.

CODE EXAMPLE 4-19 Audio Output Message

Enter (0-13 tests, 14 -Quit, 15 -Menu) ===> 10

TEST=’audio_test’
SUBTEST=’cs4231_test’
Codec_ID=’8a’
Version_ID=’a0’
SUBTEST=’external_lpbk’

###OBDIAG_MFG_START###
TEST=’audio_test’
STATUS=’FAILED’
SUBTEST=’external_lpbk’
ERRORS=’1 ‘
TTF=’505 ‘
SPEED=’299.80 MHz’

Chapter 4 Troubleshooting Procedures 4-25

 CODE EXAMPLE 4-19 Audio Output Message (Continued)

PASSES=’1 ‘
MESSAGE=’Error: External Audio Test not run: Please set the mfg-
mode to sys-ext.’
Enter (0-13 tests, 14 -Quit, 15 -Menu) ===>

4.7.2.12 EIDE
The EIDE diagnostic validates both the EIDE chip and the IDE bus subsystem.

The following code example identifies the EIDE output message.

CODE EXAMPLE 4-20 EIDE Output Message

Enter (0-13 tests, 14 -Quit, 15 -Menu) ===> 11

TEST=’ide_test’
SUBTEST=’probe-cmd-device’
SUBTEST=’hd-and-cd-check’
Enter (0-13 tests, 14 -Quit, 15 -Menu) ===>

4.7.2.13 Video
The video diagnostic validates the UPA graphics.

The following code example identifies the video output message.

CODE EXAMPLE 4-21 Video Output Message

Enter (0-13 tests, 14 -Quit, 15 -Menu) ===> 12

TEST=’video_test’
Please connect the monitor and use ttya/ttyb when running this test
if you are using the screen it may be become unreadable
SUBTEST=’mach64-chip-id-vendor-id-check’
SUBTEST=’video-frame-buffer-test’
SUBTEST=’mach64-walk-one-test’
SUBTEST=’mach64-walk-zero-test’
Enter (0-13 tests, 14 -Quit, 15 -Menu) ===>

4-26 Sun Ultra 5/10 Service Manual • November 1998

4.7.2.14 All Above
The all above diagnostic validates the system unit.

The following code example identifies the all above output message.

Note – The all above diagnostic will stall if the TIP line is installed on serial port A
or serial port B.

CODE EXAMPLE 4-22 All Above Output Message

Enter (0-13 tests, 14 -Quit, 15 -Menu) ===> 13

TEST=’all_pci/cheerio_test’
SUBTEST=’vendor_id_test’
SUBTEST=’device_id_test’
SUBTEST=’mixmode_read’
SUBTEST=’e2_class_test’
SUBTEST=’status_reg_walk1’
SUBTEST=’line_size_walk1’
SUBTEST=’latency_walk1’
SUBTEST=’line_walk1’
SUBTEST=’pin_test’

TEST=’all_dma/ebus_test’
SUBTEST=’dma_reg_test’
SUBTEST=’dma_func_test’

TEST=’ethernet_test’
Using Onboard Transceiver - Link Up.
SUBTEST=’my_channel_reset’
SUBTEST=’hme_reg_test’
SUBTEST=’global_reg1_test’
SUBTEST=’global_reg2_test’
SUBTEST=’bmac_xif_reg_test’
SUBTEST=’bmac_tx_reg_test’
SUBTEST=’mif_reg_test’
SUBTEST=’mac_internal_loopback_test’
SUBTEST=’10mb_xcvr_loopback_test’
SUBTEST=’100mb_phy_loopback_test’
SUBTEST=’100mb_twister_loopback_test’

TEST=’keyboard_test’
SUBTEST=’internal_loopback’

TEST=’mouse_test’

Chapter 4 Troubleshooting Procedures 4-27

 CODE EXAMPLE 4-22 All Above Output Message (Continued)

SUBTEST=’mouse_loopback’

###OBDIAG_MFG_START###
TEST=’mouse_test’
STATUS=’FAILED’
SUBTEST=’mouse_loopback’
ERRORS=’1 ‘
TTF=’1011 ‘
SPEED=’299.80 MHz’
PASSES=’1 ‘
MESSAGE=’Error: Timeout receiving a character’

TEST=’floppy_test’
SUBTEST=’floppy_id0_read_test’

TEST=’parallel_port_test’
SUBTEST=’dma_read’

TEST=’uarta_test’
‘UART A in use as console - Test not run.’

TEST=’uartb_test’
BAUDRATE=’1200’
SUBTEST=’internal_loopback’
BAUDRATE=’1800’
SUBTEST=’internal_loopback’
BAUDRATE=’2400’
SUBTEST=’internal_loopback’
BAUDRATE=’4800’
SUBTEST=’internal_loopback’
BAUDRATE=’9600’
SUBTEST=’internal_loopback’
BAUDRATE=’19200’
SUBTEST=’internal_loopback’
BAUDRATE=’38400’
SUBTEST=’internal_loopback’
BAUDRATE=’57600’
SUBTEST=’internal_loopback’
BAUDRATE=’76800’
SUBTEST=’internal_loopback’
BAUDRATE=’115200’
SUBTEST=’internal_loopback’
BAUDRATE=’153600’
SUBTEST=’internal_loopback’
BAUDRATE=’230400’
SUBTEST=’internal_loopback’

4-28 Sun Ultra 5/10 Service Manual • November 1998

CODE EXAMPLE 4-22 All Above Output Message (Continued)

BAUDRATE=’307200’
SUBTEST=’internal_loopback’
BAUDRATE=’460800’
SUBTEST=’internal_loopback’

TEST=’nvram_test’
SUBTEST=’write/read_patterns’
SUBTEST=’write/read_inverted_patterns’

TEST=’audio_test’
SUBTEST=’cs4231_test’
Codec_ID=’8a’
Version_ID=’a0’
SUBTEST=’external_lpbk’

###OBDIAG_MFG_START###
TEST=’audio_test’
STATUS=’FAILED’
SUBTEST=’external_lpbk’
ERRORS=’1 ‘
TTF=’1030 ‘
SPEED=’299.80 MHz’
PASSES=’1 ‘
MESSAGE=’Error: External Audio Test not run: Please set the mfg-
mode to sys-ext.’

TEST=’ide_test’
SUBTEST=’probe-cmd-device’
SUBTEST=’hd-and-cd-check’

TEST=’video_test’
Please connect the monitor and use ttya/ttyb when running this test
if you are using the screen it may be become unreadable
SUBTEST=’mach64-chip-id-vendor-id-check’
SUBTEST=’video-frame-buffer-test’
SUBTEST=’mach64-walk-one-test’
SUBTEST=’mach64-walk-zero-test’
Enter (0-13 tests, 14 -Quit, 15 -Menu) ===>

Chapter 4 Troubleshooting Procedures 4-29

4.7.3 Ending the OBDiag Menu
1. At the ok prompt, type:

ok% setenv mfg-mode off

mfg-mode = off

2. At the ok prompt, type:

ok% setenv diag-switch? false

diag-switch? = false

3. At the ok prompt, type:

ok% setenv auto-boot? true

auto-boot? = true

4. At the ok prompt, type:

ok% reset-all

4-30 Sun Ultra 5/10 Service Manual • November 1998