To use DriverWizard:
|On Windows 7 and Vista you must run DriverWizard as administrator.|
Generate an INF file for DriverWizard:
On Windows 7/Vista/Server 2008/Server 2003/XP/2000, the driver for Plug-and-Play devices (such as USB) is installed by installing an INF file for the device. DriverWizard enables you to generate an INF file that registers your device to work with WinDriver (i.e., with the windrvr6.sys driver). The INF file generated by DriverWizard should later be distributed to your customers who are using Windows 7 / Vista / Server 2008 / Server 2003 / XP / 2000, and installed on their PCs.
The INF file that you generate in this step is also designed to enable DriverWizard to diagnose Plug-and-Play devices on Windows 7 / Vista / Server 2008 / Server 2003 / XP / 2000. Additional information concerning the need for an INF file is provided in section 12.1.1.
If you do not need to generate an INF file, skip this step and proceed to the next one.
To generate the INF file with DriverWizard, follow the steps below:
When you are done, clickand choose the directory in which you wish to store the generated INF file. DriverWizard will then automatically generate the INF file for you.
You can choose to automatically install the INF file by checking the
If the automatic INF file installation fails, DriverWizard will notify you and provide manual installation instructions (refer also the manual INF file installation instructions in section 12.1).
Select the desired alternate setting:
DriverWizard detects all the device's supported alternate settings and
displays them, as demonstrated in
Select the desired from the displayed list.
DriverWizard will display the pipes information for the selected alternate setting.
|For USB devices with only one alternate setting configured, DriverWizard automatically selects the detected alternate setting and therefore thedialogue will not be displayed.|
For a control pipe (a bidirectional pipe), click 5.7.. A new dialogue will appear, allowing you to select a standard USB request or define a custom request, as demonstrated in
When you select one of the available standard USB requests, the setup packet information for the selected request is automatically filled and the request description is displayed in thebox.
For a custom request, you are required to enter the setup packet
information and write data (if exists) yourself. The size of the
setup packet should be eight bytes and it should be defined using
little endian byte ordering. The setup packet information should
conform to the USB specification parameters
|More detailed information on the standard USB requests, on how to implement the control transfer and how to send setup packets can be found in section 9.2.|
For an input pipe (moves data from device to host) click. To successfully accomplish this operation with devices other than HID, you need to first verify that the device sends data to the host. If no data is sent after listening for a short period of time, DriverWizard will notify you that the .
To stop reading, click.
For detailed compilation instructions, refer to section 5.2.4.
You have the option to log all the WinDriver API calls using DriverWizard, with the API calls input and output parameters. You can select this option by selecting theoption from the menu or by clicking on the toolbar icon in DriverWizard's opening window.
After you have finished diagnosing your device and have ensured that it runs according to your specifications, you are ready to write your driver.
Generate code by selecting this option either via DriverWizard's xxx.wdp, where "xxx" is the project name). The files are saved in a directory DriverWizard creates for every development environment and operating system selected in the code generation dialogue box.toolbar icon or from the wizard's menu. DriverWizard will generate the source code for your driver, and place it along with the project file (
In the source code directory you now have a new
xxx_diag.c source file (where
xxx is the name you selected for your
DriverWizard project). This file implements a diagnostic USB application, which
demonstrates how to use WinDriver's USB API to locate and communicate with your
USB device(s), including detection of Plug-and-Play events (device insertion/removal,
etc.), performing read/write transfers on the pipes, resetting the pipes and
changing the device's active alternate setting.
The generated application supports handling of multiple identical USB devices.
The generated DriverWizard Visual Basic and Delphi code includes similar functions and provides similar functionality as the generated C code described in section 126.96.36.199.
The generated Delphi code implements a console application (like the C code), while the Visual Basic code implements a GUI application.
The generated DriverWizard C# and Visual Basic .NET code provides similar functionality as the generated C code [188.8.131.52], but from a GUI .NET program.
As explained above, on Windows you can select to generate project and workspace/solution files for any of the supported integrated development environments (IDEs) – MS Visual Studio 5.0/6.0/2003/2005/2008/2010, Borland C++ Builder, Visual Basic 6.0, Borland Delphi, MS eMbedded Visual C++, or MS Platform Builder – and you can also select to automatically invoke your selected IDE from the wizard. You can then proceed to immediately build and run the code from your IDE.
You can also build the generated code from any other IDE that supports the selected code language and target OS. Simply create a new project file for your selected IDE, then add the generated source files to your project and compile and run the code.
DriverWizard provides native support for the Ellisys Explorer 200 USB analyzer
on Windows XP and higher (32-bit only). This support enables you to:
To capture USB traffic:
To capture a discrete control trasfer check thecheck box in the control transfers dialogue box.