USB HOST DRIVER V03 Freescale Semiconductor / Motorola, USB HOST DRIVER V03 Datasheet - Page 114

• Manufacturer Part Number: USB HOST DRIVER V03
• Description: USB Host Driver v03
• Manufacturer: Freescale Semiconductor / Motorola

Device Driver, where the installation requires administrator rights. Once the MOTUSB
Driver is installed, standard user rights are sufficient to load the Driver and to use the
Driver by accessing its programming interface.
6.2. Setup (INF) File.
To be installed correctly, Drivers must have an INF file. An INF file is a text file that
contains all the necessary information about the Device(s) and file(s) to be installed, such
as Driver images, registry information, version information, and so on, to be used by the
Setup components. An INF file is basically an ASCII text file. The contents and the
syntax of an INF file are documented in the Microsoft Windows 2000 DDK.
The INF file is loaded and interpreted by an operation software component that is closely
related to the Plug&Play Manager, called the Device Installer. It handles hot plugging
and removal of USB Devices. If the new USB Device has been detected, the system
searches its internal INF file database, located in %SystemRoot%\Inf\, for a matching
Driver. If no Driver can be found the New Hardware Wizard pops up and the user will be
asked for a Driver.
A particular Device can be associated with the MOTUSB Driver through a string that is
called Hardware ID. The operation system PnP software component builds this string
from the 16-bit vendor ID (VID), the 16-bit product ID (PID), optionally the revision
code (REV) and other components. For USB Devices, the Hardware ID is prefixed by the
‘USB’ identifier. The OS uses the ordered Hardware ID lists provided by the bus Driver,
along with INF information, to select Drivers to load for a Device. Starting at the top of
the ordered Hardware ID list, the OS tries to match the Hardware ID there with a
Hardware ID in a system INF file entry.
Here is the template for Hardware ID string, that the vendor should specify in the INF
file.
USB\VID_xxxx&PID_yyyy&REV_zzzz
USB\VID_xxxx&PID_yyyy
The MOTUSB Driver installation should install the Driver
and dynamic link
motusb.sys
library
images. However
is optional and if the vendor wants to
motusb.dll
motusb.dll
use the Driver directly, no library image is required.
The description of other INF file entries is outside the scope of this guide, please refer to
Microsoft Windows 2000 DDK for detailed information. The setup information file
template is shown in the next section and should provide the basis for making the INF file
to install the MOTUSB Driver on a vendor Device. Note that the template assumes that
MOTUSB image files are located in a same directory with an INF file. The minimum set
of information should be known before modifying this template:
M
6-3
Driver Installation.
PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE