MOTLoad Firmware Package User's Manual - Bustec

Chapter 3 MOTLoad FirmwareMOTLoad Utility ApplicationsThe definition of a MOTLoad utility application is very broad. Simply stated, it is considered aMOTLoad command, if it is not a MOTLoad test. Typically, MOTLoad utility applications areapplications that aid the user in some way (that is, they do something useful). From theperspective of MOTLoad, examples of utility applications are: configuration, data/statusdisplays, data manipulation, help routines, data/status monitors, etc.Operationally, MOTLoad utility applications differ from MOTLoad test applications in severalways:■■Only one utility application operates at any given time (that is, multiple utility applicationscannot be executing concurrently)Utility applications may interact with the user. Most test applications do not.MOTLoad TestsA MOTLoad test application determines whether or not the hardware meets a given standard.Test applications are validation tests. Validation is conformance to a specification. MostMOTLoad tests are designed to directly validate the functionality of a specific SBC subsystemor 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. Oncelaunched, most MOTLoad tests operate automatically without any user interaction. There are afew 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 separatedescriptions (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 bya unique device path string. Most MOTLoad tests require the operator to specify a test deviceat the MOTLoad command line when invoking the test.A listing of all device path strings can be displayed through the devShow command. If an SBCdevice does not have a device path string, it is not supported by MOTLoad and can not bedirectly tested. There are a few exceptions to the device path string requirement, like testingRAM, which is not considered a true device and can be directly tested without a device pathstring. Refer to the devShow command description page in the MOTLoad Firmware PackageUser’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 bydefining and creating a custom testSuite(s). The list of built-in and user-defined MOTLoadtestSuites, and their test contents, can be obtained by entering testSuite -d at the MOTLoadprompt. All testSuites that are included as part of a product specific MOTLoad firmwarepackage are product specific. For more information, refer to the testSuite command descriptionpage in the MOTLoad Firmware Package User’s Manual.16MVME6100 Installation and Use (V6100A/IH2)