76 Chapter 4
Test Controller
Test Controller modes
Test Controller modes
There are three basic operational modes for this utility:
• Stand-alone mode
• Interactive mode
• I/O Utility mode
In stand-alone mode, cxtest invokes the Test Controller. The Test
Controller reads test parameters from NVRAM (these parameters are
written into NVRAM by cxtest before it invokes the Test Controller),
executes the test and subtests specified in NVRAM, and sets a
completion bit in NVRAM when the test and subtests are finished.
cxtest is described in Chapter 5.
In interactive mode, a user interface allows the user to select the
processors to test, select the subtests to run, and examine error
information. The user interface is a set of menus described in this
chapter.
In the interactive mode, the Test Controller loops waiting for the start
command. Prior to issuing the start command, any global and/or
processor specific parameters can be modified. When all tests have
completed, the Test Controller waits for the next start command. Any
combination of parameter and tests may be modified and executed.
In I/O Utility mode, the Test Controller will load, and subsequenty
exectue, a firmware utility module from the test station. There are
currently two support utility modules: arrm and dfdutil. The
teststation utility tc_ioutil identifies the utility module to be loaded.
tc_ioutil updates an NVRAM location with the file name of the utility
module to be loaded. See tc_ioutil, arrm and dfdutil in Chapter 11,
“Utilities,” or more details.
An example of tc_ioutil would be:
tc_ioutil <node> dfdutil.fw
