MOTLoad Tests
http://www.motorola.com/computer/literature
3-3
3
automatically without any user interaction. There are a few tests where the
functionality being validated requires user interaction (that is, switch tests,
interactive plug-in hardware modules, etc.). Most MOTLoad test results
(error-data/status-data) are logged, not printed. All MOTLoad
tests/commands have complete and separate descriptions (refer to the
MOTLoad Firmware Package User’s Manual for this information).
All devices that are available to MOTLoad for validation/verification
testing are represented by a unique device path string. Most MOTLoad
tests require the operator to specify a test device at the MOTLoad
command line when invoking the test.
A listing of all device path strings can be displayed through the devShow
command. If an SBC device does not have a device path string, it is not
supported by MOTLoad and can not be directly tested. There are a few
exceptions to the device path string requirement, like testing RAM, which
is not considered a true device and can be directly tested without a device
path string. Refer to the devShow command description page in the
MOTLoad Firmware Package User’s Manual.
Most MOTLoad tests can be organized to execute as a group of related
tests (a testSuite) through the use of the testSuite command. The expert
operator can customize their testing by defining and creating a custom
testSuite(s). The list of built-in and user-defined MOTLoad testSuites, and
their test contents, can be obtained by entering testSuite -d at the
MOTLoad prompt. All testSuites that are included as part of a product
specific MOTLoad firmware package are product specific. For more
information, refer to the testSuite command description page in the
MOTLoad Firmware Package User’s Manual.
Test results and test status are obtained through the testStatus,
errorDisplay, and taskActive commands. Refer to the appropriate
command description page in the MOTLoad Firmware Package User’s
Manual for more information.
