Changes between Version 23 and Version 24 of TBR/BSP/Psim

Timestamp:

12/02/10 19:24:01 (13 years ago)

Author:

E.begov

Comment:

TBR/BSP/Psim

@@ -59 +59 @@
 = Test Reports =
 
+A MOTLoad test application determines whether or not the hardware
+meets a given standard. Test applications are validation tests. Validation is
+conformance to a specification. Most MOTLoad tests are designed to
+directly validate the functionality of a specific SBC subsystem or
+component. These tests validate the operation of such SBC modules as:
+dynamic memory, external cache, NVRAM, real time clock, etc.
+All MOTLoad tests are designed to validate functionality with minimum
+user interaction. Once launched, most MOTLoad tests operate 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.
+
+
 
 {{Test Report