1 utilities, 2 tests, 1 utilities 4.3.2 tests – Artesyn MVME55006E Single Board Computer Installation and Use (July 2014) User Manual

Page 66

Advertising
background image

MOTLoad Firmware

MVME55006E Single Board Computer Installation and Use (6806800A37J)

66

4.3.1

Utilities

The definition of a MOTLoad utility application is very broad. Simply stated, it is considered a
MOTLoad command if it is not a MOTLoad test. Typically, MOTLoad utility applications are
applications that aid the user in some way (that is, they do something useful). From the
perspective of MOTLoad, examples of utility applications are: configuration, data/status
displays, data manipulation, help routines, data/status monitors, etc.

Operationally, MOTLoad utility applications differ from MOTLoad test applications in several
ways:

Only one utility application operates at any given time (that is, multiple utility applications
cannot be executing concurrently).

Utility applications may interact with the user. Most test applications do not.

4.3.2

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. 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.

Advertising