S24 Frame Buffer Test (tcxtest)

Through a series of protocol, memory, acceleration, and colormap tests, tcxtest checks the functionality of the S24 Frame Buffer SBus card used on the SPARCstation5 and checks the FSV (fast SBus video) ASIC on the SPARCstation4 motherboard.

---

Note - Disable all screen savers before testing any graphics device. Type xset s off at a UNIX prompt to disable the Solaris screen saver.

---

tcxtest has four distinct test groups:

• AFX Protocol Tests (in 8/16/32/64-bit mode)

  WRC

• Frame Buffer Memory Tests (in 8/16/32/64-bit14 mode)

  address

  constant

  random

• Acceleration Tests (both User and Raw modes)

blit
stip

• Colormap and Cursor Tests

  cursor (does not apply to SPARCstation4)

  colormap

tcxtest Subtests

WRC By performing multiple writes and reads, and then verifying the results, the WRC test exercises the FIFO inside the S24 chip. The WRC test is composed of these three subtests: test_afx_alt_wr, test_memafx, and test_afx_random.

If these tests fail, they print an error message showing the expected and observed data.

• test_afx_alt_wr

This test performs 16 writes to alternative pages (for example: WR (Page1), WR (Page2), WR (Page1+off), WR (Page2+off), etc.). It then reads back the data and compares it with the expected results.

This test also writes to the frame buffer space 16 times, followed by a write to a different page in the frame buffer space. The test then reads this data back and verifies it with the expected results.

• test_memafx

The CPU in the SWIFT chip has closely coupled interfaces for the DRAM and the AFX bus. This test checks the arbitration between the two accesses.

This test performs a number of alternating writes to the AFX and the CPU memory. After writing to different locations, the test reads and verifies the data. By performing an access across the page boundaries, the test covers both the cached and non-cached accesses.

• test_afx_random

After writing to one page in the DRAM memory, the test performs a few random writes/reads to random locations in the AFX space. The test then writes to a different page in the DRAM space, where it performs random accesses again.

This test does not perform any data verification, it just checks to see if any of these random accesses caused a time out.

constant
The constant test writes a data pattern to the whole memory. This pattern is
read back and compared with the expected data. Once the memory fill
operation is completed, the test reads the memory back and verifies that the
value read is correct.

address
The address test writes a data pattern (which is same as the value of the
address) to the whole memory. This pattern is then read back to verify that it is
the correct value.

random The random test writes a random data pattern to the whole memory. This pattern is read back and compared with the expected data. After the memory fill operation is completed, the test reads the memory and verifies the values read are correct.

blit The blit test has two parts, the raw blit test and the user blit test.

The raw blit test draws a 64x64x24 pixel image at the top left corner of screen. It then blits the image to the screen. The destination images are read back and compared with the original image to verify the raw blit operation executed correctly.

The user blit test draws a 64x64x24 pixel image at the top left corner of screen. It then blits the image to the screen. The destination images are read back and compared with the original image. The user blit test is the same as the raw blit test, except the user blit test uses the user data space for the blit command.

stip The stip test performs numerous corner cases for stipple. The test writes to the destination with different data values using a stipple operation. The destination data is read back and verified. For the fast SBus video (FSV), the following is checked:

• Walks 1 through pixel mask
• Walks 1 through ROP bits
• Walks 1 through destination byte
• Walks 1 through IDX byte

cursor (does not apply to SPARCstation4)

The cursor test performs a data register regression test. It writes a walking 1 pattern to the cursor data registers. The data is then read back and verified with the expected results. The test is repeated using a walking 0 as the data pattern

colormap Loads all locations in the colormap with varying values of RGB.

---

Note - If the system being tested has a monochrome or greyscale monitor, visual color problems are undetectable.

---

tcxtest Options

FB Locking

See the section about testing multiple frame buffers in SunVTS 2.0 User's Guide for details.

* Click to enable or disable Frame Buffer locking.

Figure 31-1 tcxtest

tcxtest Test Modes

Connectivity Mode Connectivity Mode is not applicable to frame buffer tests such as tcxtest.

Online Mode Online Mode is not applicable to frame buffer tests such as tcxtest.

Offlline Mode Offline mode is the default for tcxtest. Tcxtest executes the appropriate subtests for the hardware platform being tested.

tcxtest Command Line Syntax

/opt/SUNWvts/bin/tcxtest standard_arguments -o dev=device_name,lock=E(nable)/D(isable), X=bit_mode,T=test,S=[dfb8, dfb24, dfb32]

Argument	Explanation
dev=device_name	Specifies the filename of the device to be tested, for example: dev=tcx0
lock=E(nable)/D(isab le)	Enables/disables the window system locking option. See the section about Testing Frame Buffers in SunVTS 2.0 User's Guide for details. Do not use when device is the window system display.
X=bit_mode	Specifies the data transfer size; supported values are: 8..byte 16 short 32 long 64 double word
T=test	Specifies a particular test; to specify an individual test, replace test with: a..Address c..Constant r..Random b..Blit s..Stipple h..Cursor w..WRC Note: When you select either the Blit or Stipple test, both the user and raw mode tests are executed.
S=[dfb8, dfb24, dfb32]	Specifies which frame buffer memory space to use. dfb8 Dumb frame buffer 8-bit space. Memory is accessed only by bytes. dfb24 Dumb frame buffer 24-bit space. Memory is accessed only by 24-bit reads and writes. dfb32 Dumb frame buffer 8-bit space. Memory is accessed by 8-bit reads and writes.

tcxtest Error Messages

The error messages below are returned by the various subtests.

6000 FBIOGATTR failed in is_24bit subroutine

Probable_Cause(s):

a. Driver not installed b. OS driver problem

c. afx bus error

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6010 Colormap failure, Address: <address>, red, Expected:
<value> Observed: <value>

Probable_Cause(s):

a. Bad RAMDAC b. Bad a24 board

c. afx bus error

Recommended_Action(s):

a. Replace fram buffer card b. Examine system message files (/var/adm/messages) for other information

6011 Colormap failure, Address: <address>, green, Expected:
<value> Observed: <value>

Probable_Cause(s):

a. Bad RAMDAC b. Bad a24 board

c. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6012 Colormap failure, Address: <address>, blue, Expected:
<value> Observed: <value>

Probable_Cause(s):

a. Bad RAMDAC b. Bad a24 board

c. afx bus error

Recommended_Action(s):

a. Replace fram buffer card b. Examine system message files (/var/adm/messages) for other information

6013 THC Cursor Regression failed Address: <address>,
Expected: <value>, Observed: <value>

Probable_Cause(s):

a. Bad a24 board b. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6014 Can't clear frame buffer, dst_start: <address>,
src_start: <address>, Address: <value>, Observed: <value>
Expected: <value>

Probable_Cause(s):

a. Bad a24 board b. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6015 Frame buffer pattern test failed, dst_space:
<address>, src_space: <address>, check_x = <value>, check_y
= <value>, Address: <value>, Observed: <value> Expected:
<value>

Probable_Cause(s):

a. Bad a24 board b. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6016 Can't clear frame buffer pattern,  dst_space:
<address>, src_space: <address>, check_x: <value>, check_y:
<value>, Address: <value> Observed: <value> Expected:
<value>

Probable_Cause(s):

a. Bad a24 board b. afx bus error

Recommended_Action(s):

a. Replace frame buffer card

b. Examine system message files (/var/adm/messages) for other information

6017 Can't clear frame buffer after write, Address:
<value>, Expected: <value> Observed: <value>

Probable_Cause(s):

a. Bad a24 board b. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6018 Raw Blit test failed, Offset: <address>, Expected:
<value> Observed: <value>

Probable_Cause(s):

a. Bad a24 board b. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6019 Blit test failed CHECKING, Offset: <address>,
Expected: <value> Observed: <value>

Probable_Cause(s):

a. Bad a24 board b. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6020 Blit test failed, Offset: <value>, Expected: <value>
Observed: <value>

Probable_Cause(s):

a. Bad a24 board b. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6021 Blit accel test failed. Offset: <value>, Expected
:<value> Observed: <value>

Probable_Cause(s):

a. Bad a24 board b. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6022 Stipple test failed. Offset: <address>,
Expected:<value> Observed: <value>

Probable_Cause(s):

a. Bad a24 board b. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6025 Raw Stipple test failed. Offset: <address>,
Expected:<value> Observed: <value>

Probable_Cause(s):

a. Bad a24 board b. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6027 Frame buffer pattern test miscompare, y: <value> x:
<value> Observed: <value> Expected: <value> Address:
<value>

Probable_Cause(s):

a. Bad RAMDAC b. Bad a24 board

c. afx bus error

Recommended_Action(s):

a. Replace frame buffer card b. Examine system message files (/var/adm/messages) for other information

6029 Afx protocol test <message>  Expected: <value>

Probable_Cause(s):

a. afx bus error

b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6030 Null allocation to membase

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6031 Afx_mem test failure, Address: <address>, Expected:
<value>

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6032 Afx_mem Mem test failure, Address+0x4000 Value:
<value>, Exp 0x5555aaaa

Probable_Cause(s):

a. afx bus error

b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6033 Pattern test failed in Byte mode for DFB<value>.
Offset: <address>, Expected: <value> OBserved: <value>
xor(<value>)

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6034 Pattern test failed in Short mode for DFB<value>.
Offset: <value>, Expected:  <value> OBserved: <value>
xor(<value>)

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6035 Pattern test failed in Long mode for DFB<value>.
Offset: <value>, Expected: <value> OBserved:  <value>
xor(<value>)

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6036 Pattern test failed in Long mode for DFB<value>
Offset: <value>, Expected: <value> OBserved:  <value>

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6042 Pattern test failed in Dblword mode for DFB<value>,
Offset: <value>, Expected: <value> Observed:<value>,
xor:<value>

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6039 Random test failed in Byte mode for DF<value>, Offset:
<value>, Expected: <value> Observed: <value> xor: <value>

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6040 Random test failed in Short mode for DFB<value>,
Offset: <value>, Expected: <value> Observed: <value> xor:
<value>

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6041 Random test failed in Long mode for DFB<value>,
Offset: <value>, Expected: <value> Observed: <value> xor:
<value>

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6042 Pattern test failed in Dblword mode for DFB<value>,
Offset: <value>, Expected: <value> Observed: <value> xor:
<value>

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6043 Address test failed in Char mode for DFB<value>.
Offset: <value>, Expected: <value> Observed: <value> xor:
<value>

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6044 Address test failed in Short mode for DFB<value>,
Offset: <value>, Expected: <value> Observed: <value> xor:
<value>

Probable_Cause(s):

a. afx bus error

b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6045 Address test failed in Long mode for DFB<value>,
Offset: <value>, Expected: <value> Observed: <value> xor:
<value>

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6046 Address test failed in Dblword mode for DFB<value>,
Offset: <value>, Expected: <value> Observed: <value> xor:
value>

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

6047 Verifying Double:word writes,

Probable_Cause(s):

a. afx bus error b. Bad a24 board

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

8000 Open failure for device <device name>

Probable_Cause(s):

a. Driver not installed b. OS driver prblm

c. afx bus err

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

8001 Pattern test failed in Long mode, Offset: <value>,
Expected: <value> Observed: <value>

Probable_Cause(s):

a. Driver not installed b. afx bus error

c. Bad cpu board

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

8002 can't acquire console semaphor

Probable_Cause(s):

a. Not enough mem b. Not enough swap space

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

 8003 XCreateSimpleWindow failed

Probable_Cause(s):

a. Not enough mem b. Not enough swap space

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

8004 Multibuffering extension does not exists.

Probable_Cause(s):

a. Not enough mem b. Not enough swap space

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information

8005 Couldn't create enough buffers.

Probable_Cause(s):

a. Not enough mem b. Not enough swap space

Recommended_Action(s):

a. Examine system message files (/var/adm/messages) for other information