3-2
Literature Center Web Site
MOTLoad Firmware
3
MOTLoad binary image(s). Currently the largest MOTLoad compressed
image is less than 1MB in size.
MOTLoad Commands
MOTLoad supports two types of commands (applications): utilities and
tests. Both types of commands are invoked from the MOTLoad command
line in a similar fashion. Beyond that, MOTLoad utilities and MOTLoad
tests are distinctly different.
MOTLoad Utility Applications
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 can not be executing concurrently).
❏
Utility applications may interact with the user. Most test
applications do not.
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. 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