1X00623H03模块备件

1X00623H03

MOTLoad实用程序的定义非常广泛。仅仅
如上所述，如果它不是机动负载测试，则被视为机动负载命令。
通常，MOTLoad实用程序应用程序是帮助用户的应用程序
在某种程度上（也就是说，他们做了一些有用的事情）。从
MOTLoad，实用程序应用程序示例包括：配置、数据/状态
显示、数据操作、帮助例程、数据/状态监视器等。
在操作上，非负载实用程序应用程序不同于非负载测试
以多种方式应用：
❏ 在任何给定时间（即，
多个实用程序应用程序不能同时执行。）
❏ 实用程序应用程序可以与用户交互。大多数测试
应用程序没有。
动载试验
MOTLoad测试应用程序确定硬件是否：
满足给定标准。测试应用程序是验证测试。验证是
符合规范。大多数动载试验旨在：
直接验证特定SBC子系统的功能，或
组成部分这些测试验证了以下SBC模块的操作：
动态内存、外部缓存、NVRAM、实时时钟等。
动载试验
http://www.motorola.com/computer/literature 3-3
3.
所有MOTLoad测试旨在以低限度验证功能
用户交互。一旦启动，大多数机动负载测试将运行
自动进行，无需任何用户交互。有几个测试，其中
正在验证的功能需要用户交互（即，
交互式插件硬件模块等）。大多数动载试验结果
（错误数据/状态数据）被记录，而不是打印。全车
测试/命令有完整和单独的描述（请参阅
MOTLoad固件包用户手册）。
MOTLoad可用于验证/验证的所有设备
测试由的设备路径字符串表示。大多数机动车
测试要求操作员指定机动负载下的测试设备
调用测试时的命令行。
可以通过devShow显示所有设备路径字符串的列表
命令如果SBC设备没有设备路径字符串，则不是
由机动车辆支持，不能直接测试。有几个
设备路径字符串要求的例外情况，如测试RAM
不被视为真正的设备，可以在没有设备的情况下直接测试
路径字符串。请参阅中的devShow命令描述页
MOTLoad固件包用户手册。
大多数MOTLoad测试可以组织为一组相关的测试来执行
通过使用testSuite命令测试（testSuite）。专家
操作员可以通过定义和创建自定义
测试套件。内置和用户定义的MOTLoad测试套件列表，以及

1X00623H03

1X00623H03

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. 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. MOTLoad Tests http://www.motorola.com/computer/literature 3-3 3 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. 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 by defining and creating a custom testSuite(s). The list of built-in and user-defined MOTLoad testSuites, and