Artesyn MOTLoad Firmware Package User's Manual (February 2015) - Manual (Page 20)

Introduction
MOTLoad Firmware Package User’s Manual (6806800C24D) 20
1.1.3 MOTLoad Utility Applications
The definition of a MOTLoad utility application is very broad. Simply stated, it is a MOTLoad
command that is not a MOTLoad test. Typically, MOTLoad utility applications are applications
that aid the user in some way. From the perspective of MOTLoad, examples of utility
applications are: configuration, data/status displays, data manipulation, help routines,
data/status monitors, and so on.
Operationally, MOTLoad utility applications differ from MOTLoad test applications in several
ways:
 Only one utility application may be operating at any given time (that is, multiple utility
applications can not be executing concurrently).
 Utility applications may interact with the user. Most test applications do not.
1.1.4 MOTLoad Tests
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. It is possible for a board's component to fail in the user application but pass
specification conformance. These tests validate the operation of such SBC modules as:
dynamic memory, external cache, NVRAM, real time clock, and so on.
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, and so on). Most MOTLoad test results (error-
data/status-data) are logged, not printed. Test results are not preserved and therefore not
available to user applications subsequent to their execution. All MOTLoad tests/commands are
described in detail in
Chapter 3, MOTLoad Commands .
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.