DosPLTU.txt
-------------
This document describes about the executable "DosPLTU.exe".
Description:
------------
This is a DOS based utility and is targeted to be used by OEMs to streamline
their production, with as little human intervention as possible. This utility
supports checking the device firmware version, checking and / or updating the
device EEPROM with a template DAT file and performing R/W tests on all the
logical units (LUNs) supported by the device.
DosPLTU Usage:
---------------
DosPLTU [-h|-u] [-v] [-f"version"] [-t -n"loopcount" -s"testsize"]
[-e"DATFileName" | -w"DATFileName" | -x"DATFileName"]
[-l"LogFileName"] [-c"HostController"]
-h|-u ...............print help/usage
-v ..................verbose, optional, default is off
-f"version"..........version number that is to be checked against the firmware
version of the device
-t ..................perform R/W tests
-n"loopcount"........specifies the number of times the R/W tests are to be
performed. This is optional and a default value of 10
will be used if this is not specified
-s"testsize".........specifies the test transfer size in KB for the R/W tests.
This is optional and a default value of 64KB will be used
if this is not specified
-e"DATFileName"......name of DAT file (with full path) that is to be checked
against the device EEPROM. This option cannot be specified
with -w or -x options
-w"DATFileName"......name of DAT file (with full path) that is to be written
to device EEPROM This option cannot be specified with -e
or -x options
-x"DATFileName"......name of DAT file (with full path) that is to be checked
against the device EEPROM and if necessary that is to be
written to the device EEPROM. This option cannot be
specified with the -e or -w options
-l"LogFileName"......name of the log file (with full path) to which the test
status messages are logged
-c"HostController"...specifies the host controller to which the device is
connected. This should be one of "UHCI", "OHCI" or "EHCI".
This is an optional parameter and if not specified, the
default value of "UHCI" will be used.
-i ..................infinite loop, till user wants to quit
Note:
-----
1. All options can be specified using both UPPERCASE or lowercase letters.
2. The double quotes ("") around file names is optional.
If the path names does not contain blank spaces, then the double quotes are
not necessary. If the path names contain blank spaces, then the double quotes
are mandatory.
3. The file names are to be specified with full path information. If the files
are in the current directory, then the path information is not necessary.
Option Groups and Priority Levels:
--------------------------------------
1. The options are classified into 4 groups as described below.
a. Usage - "-h" or "-u"
b. Firmware check - "-f"
c. EEPROM check / update - "-e", "-w" and "-x"
d. R/W tests - "-t"
2. The utility has a proirity level for each group of options. The priority level
and processing details are described below.
a. Usage group - Has the highest priority (level 0). If this is specified, then
the utility would just display the program usage and exit. All other options
are ignored and are not processed.
b. Firmware check group - Has the next highest priority (level 1). The utility
processes this option before EEPROM check and R/W test options. If the device
firmware does not match the version specified with this option, then the
utility would display an error message and exit without processing any other
option.
c. EEPROM check / update group - Has a priority level of 2. If "-f" option is
specified, the utility would process this option after successfully checking
the device firmware version. Otherwise, this would be processed first. It is
important to note that this group has 3 options ("-e", "-w" and "-x") which
are mutually exclusive. That is, only one of the 3 options can be specified.
If any error occurs while processing this group, the utility ignores the
R/W test option and exits after displaying the corresponding error message.
d. R/W test group - This has the lowest priority (level 3) and is processed
last after successfully processing other specified options. This group has
two optional command line options ("-n" and "-s") and the corresponding
default values are used if those options are not specified.
Features:
---------
1. Checks the firmware version of the device.
2. Checks the device EEPROM against a template DAT file and returns an error if
any mismatch is found. This is achieved by using the "-e" option and is useful
in testing devices whose EEPROM has already been updated.
3. Updates the device EEPROM always with a template DAT file with out checking for
any mismatch. After every update, the serial number is automatically incremented
and the DAT file is updated. This is achieved by using the "-w" option and is
useful in updating the device EEPROM for the first time.
4. Checks the device EEPROM against a template DAT file and updates the device
EEPROM if any mismatch is found. If the EEPROM is updated, the serial number
is automatically incremented and the DAT file is updated. This is achieved by
using the "-x" option and is useful in testing devices whose EEPROM may or may
not have been already updated.
5. Performs R/W tests on all LUNs supported by the device. The tests are performed
using the loop count and test size values specified with "-n" and "-s" options.
6. Provides an option (-v) to turn on or off the additional debug / status comments.
7. Provides an option (-l"LogFileName") to log all messages to the user specified
log file.
8. Allows processing devices one after another in a loop till user wants to exit by
specifying the "-i" option in the command line. Otherwise, the utility will exit
after it is done with a single device.
9. Displays the status by showing a big "ERR", "FAIL" or "PASS" along with other
relevent information.
"ERR" - Means an error occurred outside of the test process. This can happen
if there are any errors while parsing the input arguments, or invalid
usage, or invalid file paths, or any errors while starting the host
controller and root hub.
The application will exit with error code 1 during such circumstances.
"FAIL" - Means an error occurred during the process of testing. This can happen
if no matching devices are found or any of the test fails. The actual
reason for the failure is given below the "FAIL" status.
The application will exit with error code > 1 during such circumstances.
"PASS" - Means no error occurred and the process of testing completed
successfully.
The application will exit with error code 0 during such circumstances.
10. The utility will return with one of the following exit codes.
0 - Indicates "PASS"
1 - Indicates "ERR"
2 - Indicates "FAIL" (Device not found error)
3 - Indicates "FAIL" (Firmware mismatch error)
4 - Indicates "FAIL" (Error while reading device EEPROM)
5 - Indicates "FAIL" (Device EEPROM and template DAT file mismatch error)
6 - Indicates "FAIL" (Error while writing to the device EEPROM)
7 - Indicates "FAIL" (Error verifying updated EEPROM data)
8 - Indicates "FAIL" (Error while initializing disk(s) for R/W tests)
9 - Indicates "FAIL" (Error while writing to disk)
10 - Indicates "FAIL" (Error while reading from disk)
11 - Indicates "FAIL" (Error verifying read and write data)
12 - Indicates "FAIL" (Error creating the log file)
NOTE:
-----
As mentioned above, when the device EEPROM is updated, the DAT file is updated with
the serial number incremented by one. During such cases, there is a chance for the
serial number to overflow from "FFFFFFFFFFFF" to "000000000000". When this overflow
occurs, there will be a warning displayed to indicate the overflow. However, the
testing on the current device continues normally as the overflow will matter only
with the next device that is to be tested. Even if the tests on the current device
pass successfully, the return value will be "ERR" to indicate the serial number
overflow error.
Limitations:
------------
1. The host controller to which the device is connected should be the first one of
it's kind in the enumeration order.
2. Supports devices connected only at the root hub level.
3. The first MSC device in the enumeration order has to be the device whose EEPROM data
is to be updated or read.
4. The utility does not distinguish between actual device failures and media specific
failures during R/W tests. Hence, it is recommended that the R/W tests are done
on devices with known good media.
5. It is recommended that no other USB devices are connected to the system, specially
when the system is booting.
6. It is recommended that the utility is used on systems having Pentium II or III
processors (400 - 800 MHz processor speed). The utility seems to fail more as
the processor speed increases. On systems having Pentium4 processors with speed
as high as 1.4 to 2.4 GHz, the utility works reliably around 80% of the times
and varies with different system configurations.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.