Video Memory test

Thoroughly tests the on-screen video memory (the memory part that is mapped on to the monitor) of the M64 video board in 8-bit, 16-bit, 32-bit, 64-bit, and 64 byte (block) modes. Entire on-screen video memory is tested by testing 512 bit blocks at a time (8x8 pixel block). Each block is tested in two passes. Each pass consists of a data write and read. In the first pass user specified data or random data is used and in the second pass one's complement of the data used in the first pass is used so that each on-screen video memory location (bit) is tested with a zero (electrical low state) and one (electrical high state).

RAMDAC test

Tests the RAMDAC in three phases. In the first phase the RAMDAC CLUT (Color LookUp Table) is tested using simple write/read patterns to determine if there are any bad bits in CLUT.

The data patterns used are:

• Random data

• Complement of the random data (used as first data pattern)

• The data pattern 0101

• The data pattern 10101

In the second phase, four different patterns are drawn on the screen. Each pattern stays on the screen for approximately three seconds. The four patterns are listed below. For each pattern the signature is captured and compared with the signature obtained for the same pattern on a known good board. This test verifies that all the different data paths within the RAMDAC are functioning properly.

Patterns drawn on screen:

• Red ramp with cursor at top-left corner of the screen

• Blue ramp with cursor at top-right corner of the screen

• Green ramp with cursor at bottom-left of the screen

• Grey ramp with cursor at bottom-right of the screen

In the last (third) phase of the RAMDAC test the Vertical Retrace Interrupt is tested for 300 interrupts.

Accelerator Port test

Tests all of the following:

• Data paths (sources: fixed color, host data, blit, fixed pattern)

• Arithmetic and logic unit (ALU)

• Color comparator

• Primitives (destinations: line, rectangle)

• Mono to color expansion logic

Primitives are drawn using a combination of different data paths (allowed), ALU functions, and color comparator functions. A checksum is generated for each data combination and is compared with the checksum generated for the same data combination on a known good board.

Frame Buffer Locking

This option is set to disable if the M64 is not the console device.

When Sunvts GUI is brought up FB Locking is enabled by default if M64 is console device. If M64 is not console device, FB Locking is disabled by default.

Connection

No

Not supported

Functional

(Offline)

Yes

The m64test verifies the M64 video board.

dev= device_name

device_name is the relative path name of the device being tested with respect to /dev/fbs. The default is m640.

S= subtest_number

subtest_number is the test number of the subtest to be run. Select from the subtests below. You can run multiple subtests by adding the subtest numbers. For example, n=0x00003 runs both test 00001 and test 00002; n=0x00005 runs both test 0x00001 and test 0x00004. Note that you do not need the leading zeros.

• n--0x00001 VRAM

• n--0x00002 RAMDAC

• n--0x00004 Accelerator port test (Rendering Pipeline)

More than one test can be selected by ORing subtest numbers. For example: n = 0x00005 means VRAM and Rendering Pipeline tests. A hex number must be preceded by 0x, decimal numbers are also acceptable.

F= #_of_subtest_loops

Specifies the number of times to repeat each subtest. The default is 1.

B= #_of_test_loops

Specifies the number of times to repeat a test loop before passing; default is 1.

L= disable

Disables the frame buffer lock. Disable the lock when the m64 is not the console or when the server is not running on the m64 under test.

P= test_pattern

Specifies the test pattern number. The default is r , for random patterns. You may also choose 0 for 0x0000000 , 3 for 0x3333333 , 5 for 0x5555555 , or 9 for 0x9999999 .