Running the Modular Stress Test from the Command Line
Article
The best choice of command line for the Modular Stress Test varies depending upon the setup of the target device. You may be able to more easily experiment with different command-line options if you run the Modular Stress Test from a command prompt rather than running the test from the CETK.
The following table shows suggested commands for the Modular Stress Test for a variety of test scenarios. For detailed information about the command-line options for the Modular Stress Test, see Modular Stress Test Command-Line Options.
To run the Modular Stress Test from the command line
Scenario
Do this
Target device is connected to a development workstation that is running Platform Builder.
Copy all files from <Platform Builder installation path>\Cepb\Wcetk\Ddtk\<CPU> to the release directory.
Copy <Platform Builder installation path>\Cepb\Wcetk\Results.xslt to the release directory.
At the command prompt, type oemstress -result -history -autooom [-server:server_name].
An Oemstress.ini file must exist in the release directory on the development workstation. The harness creates a Result.xml results file and a History.csv history file in the release directory.
Target device is connected to a network but not connected to a development workstation that is running Platform Builder.
Copy all files from <Platform Builder installation path>\Cepb\Wcetk\Ddtk\<CPU> to the root directory on the target device.
Copy <Platform Builder installation path>\Cepb\Wcetk\Results.xslt to \\<machine_name>\<share>.
At the command prompt, type oemstress -ini:\\machine_name\share\oemstress.ini -result:\\machine_name\share\result.xml -history:\\machine_name\share\history.csv -autooom [-server:server_name].
An Oemstress.ini file must exist in the specified network share. The harness reads the Oemstress.ini initialization file from the network share. The harness creates a Result.xml results file and a History.csv history file on the network share.
Target device is not connected to a development workstation running Platform Builder and not connected to a network.
Copy all files from <Platform Builder installation path>\Cepb\Wcetk\Ddtk\<CPU> to the root directory on the target device.
Copy <Platform Builder installation path>\Cepb\Wcetk\Results.xslt to the same location as the Result.xml file.
On the target device, choose Start, choose Run, and then type oemstress –ini:\oemstress.ini -result:[path]result.xml -autooom [-server:server_name] to run the Modular Stress Test.
The initialization file must exist in the root directory of the target device, unless you explicitly specify another location for the file in the command line. The harness creates a results file in the root directory of the target device. You should create the results file on a non-volatile storage medium such as a flash memory card to avoid data loss if the target device crashes. Do not create a history file on the target device because the history file steadily increases in size over the duration of the testing run.
Note If you do not launch the Modular Stress Test from the release directory while the development workstation running Platform Builder is connected to the target device, the Modular Stress Test can run only if the files for the test are located in the root directory or the Windows directory. The CreateProcess and LoadLibrary functions search those directories for the lpszImageName and lpLibFileName parameters. To run the test from any directory, add the following registry key, which must be present at boot time: