1 Introduction

The purpose of this document is to describe the diagnostic test plan which will be used to identify and isolate hardware problems with the Multi-Channel Output (MCO) board.

1.1 Goals

Based on experience with the earlier video option boards, quantitative goals will be set for the following areas:

Time to fail
Time to repair

1.2 Assumptions

It is assumed that the manufacturing process for the MCO board will be essentially identical to the current process used to manufacture other video option boards on the Indigo2 line. Boards are quickly tested in the functional test area with ``captured'' disk drives and then are sent to pack-out.

Failed MCO boards are sent to the board repair area (Board RA) where the boards are debugged and repaired.

1.3 Strategy

Diagnostics tests will be written to check the operation of each of the functional areas of the MCO.

The standalone ide program will be the primary program used to exercise graphics functionality. The Unix-level suite of tests, systest, may use Unix-level commands, (e.g. setmon) to verify MCO functionality, but the focus of the testing will in the standalone ide area.

The following chapters present a deailed list of the tests/areas-to-test which we plan to use to diagnose the MCO board.


Last Modified: 03:38pm PDT, August 25, 1997