For USB-specific code, select the following options in Visual Studio Professional 2019 In the New Project dialog box, in the search box at the top, type USB. In the middle pane, select Kernel Mode Driver, USB (KMDF).
- Apr 08, 2018 You send to the device that is using the USB port. You will need to know the device that you are connecting. If it's a virtual serial port device then the built-in serial port drivers are used. If it's some other device then you use the device drivers for that device, which might need to be supplied with the device. It all depends on what you are connecting to the USB port.
- NVIDIA Rolls Out New Vulkan Graphics Driver - Get Build 457.83 Beta Microsoft Rolls Out January 2021 Firmware for Surface Pro 7 Tablets AMD Rolls Out Its First 2021 Graphics Driver - Get Radeon 21.1.1.
- USB Visual Signal Indicator The USB HID visual signal indicator are powered and activated via the USB port. LEDs produce light in three of four colors; red, green, yellow, blue and white. Intensity, flash rate and duty cycle are all programmable. Optional internal piezo buzzer and internal tactile switch are available. Self powered from the USB.
This is the Solaris USB camera drivers project and it will first target on the OV511 cameras based on the Linux ov511 driver. NEW: USB Video Class on Solaris. See the project forum for. ...
- ov511_driver-0.1.zip
- so-usbcamera
- Freeware (Free)
- 73 Kb
- Solaris
Aiptek Hyperpen USB tablet drivers for Linux and X.Org/XFree86. Also includes GUI front-end for configuring the tablet while in-use. Supports Aiptek 6000U, 8000U, 12000U. May work with 4000U/5000U, also reported to work with off-brand clones such as. ...
- Aiptek_unified_package-10-29-2004b.tar.bz2
- aiptektablet
- Freeware (Free)
- 684 Kb
- BSD; Linux
The Developer Edition of RapidDriver includes all the features of the Explorer, and additionally allows you to create and distribute your own applications incorporating integrated ISA/PCI/USB/LPT drivers to control your hardware. You can manage your. ...
- rdeval.zip
- EnTech Taiwan
- Commercial ($349.00)
- Win98, WinME, WinXP, Windows2000, Windows2003
Joyst.c written in Borland C.2.0 Subject inputs patient number, has the option of practice, then recordingsbegin. Horizontal bar records subject's pain level with manipulation of arrow keys or joystick int 15h,84.not USBjoystick. File. ...
- Joyst.zip
- joystipainlevel
- Freeware (Free)
- 467 Kb
- Windows
MK Registry & USB Fixer is a small and very easy to use application that will allow you to quickly repair your registry and USBdrivers. All the features are accessible from the main window. You just have to select the actions you want to be. ...
- MK Registry & USB Fixer
- Mohammad Reza Karimi
- Freeware (Free)
- 1.7 Mb
- WinXP, Windows Vista, Windows 7, Windows 7 x64
USB Analyzer is a powerful tool for monitoring USB port activities on Windows. It enables intercepting, displaying, recording and analyzing data exchanged between applications and devices via USB ports in the system.
- usb_analyzer.exe
- Eltima Software
- Shareware ($69.95)
- 964 Kb
- WinXP, WinVista, WinVista x64, Win7 x32, Win7 x64, Windows2003, Windows 8, Windows 10, Windows Server 2012
J3DJoystick is a Joystick driver for Java3D which interfaces with the Linux Joystick J3DJoystick is a Joystick driver for Java3D which interfaces with the Linux Joystick drivers..
- j3djoystick-0.5.tar.gz
- j3djoystick
- Freeware (Free)
- 5 Kb
- BSD; Linux
A driver recovery cd works with a windows OS CD to restore your Toshiba Tecra M4 XP back to the original factory setup. Once windows has installed you put this disk into the drive as soon as windows gives you a found new hardware dialog box.
- Toshiba Tecra M4 Drivers
- Restore Disk
- Shareware ($19.95)
- 32 Mb
- All Windows PC OS
USBlyzer is an easy to use software-based USB Protocol Analyzer for Windows, which performs USB device activity analysis in real-time. USBlyzer allows you to capture, display and analyze IRP and URB requests and related structures used by USB device. ...
- USBlyzer.zip
- USBlyzer
- Freeware (Free)
- 3.86 Mb
- WinXP, WinVista, WinVista x64, Win7 x32, Win7 x64, Win2000, Windows2000, Windows2003, WinServer, Windows Vista
Free single/multi-player Tetris with amazing graphics, sounds, and music.Features: * 100% arcade perfect Gameboy to Windows conversion of the original * 1-2 player simultaneous Tetris action * Beautiful full color and high resolution graphics * Awesome digital sound effects * Amazing digitally orchestrated music soundtrack * Perfect control with keyboard and/or USB joystick * 6 different and exciting game modes * Saved game options * Saved ..
- TC2-Setup.exe
- Silent Hero Productions
- Shareware ($)
- 15.59 Mb
- WinXP, Win Vista, Windows 7
- Beautiful full color and high resolution visual graphics - Beautiful full color and high resolution visual graphics- Awesome digital sound effects- Amazing digitally orchestrated soundtrack- Play with keyboard, mouse, or USB joystick- 10 progressively harder levels- Saved high scores table for each game mode- Saved game preferences.
- PA-Setup.msi
- 16BitSoftdlT«
- Shareware ($)
- 3.4 Mb
- WinXP, Win Vista, Windows 7, Windows 8
RapidDriver is intelligent tool for driver development, PC hardware analysis and debugging. RapidDriver allows you to start work with hardware after just a few clicks. Simply install your new hardware, create a new RapidDriver project, and then. ...
- rdeval.zip
- EnTech Taiwan
- Shareware ($199.00)
- 5.2 Mb
- Win 98, ME, XP, 2000, 2003
Related:Usb Joystick Drivers - Usb Joystick Drivers For Games - Drivers Generic Usb Joystick - Generic Usb Joystick Drivers - Usb Vibration Joystick Drivers
In this topic you'll use the USB Kernel-Mode Driver template provided with Microsoft Visual Studio Professional 2019 to write a simple kernel-mode driver framework (KMDF)-based client driver. After building and installing the client driver, you'll view the client driver in Device Manager and view the driver output in a debugger.
For an explanation about the source code generated by the template, see Understanding the KMDF template code for a USB client driver.
Prerequisites
For developing, debugging, and installing a kernel-mode driver, you need two computers:
- A host computer running Windows 7 or a later version of the Windows operating system. The host computer is your development environment, where you write and debug your driver.
- A target computer running Windows Vista or a later version of Windows. The target computer has the kernel-mode driver that you want to debug.
Before you begin, make sure that you meet the following requirements:
Software requirements
- Your host computer hosts your development environment and has Visual Studio Professional 2019.
- Your host computer has the latest Windows Driver Kit (WDK) for Windows 8. The kit include headers, libraries, tools, documentation, and the debugging tools required to develop, build, and debug a KMDF driver. To get the latest version of the WDK, see Download the Windows Driver Kit (WDK).
- Your host computer has the latest version of debugging tools for Windows. You can get the latest version from the WDK or you can Download and Install Debugging Tools for Windows.
- Your target computer is running Windows Vista or a later version of Windows.
- Your host and target computers are configured for kernel debugging. For more information, see Setting Up a Network Connection in Visual Studio.
Hardware requirements
Get a USB device for which you will be writing the client driver. In most cases, you are provided with a USB device and its hardware specification. The specification describes device capabilities and the supported vendor commands. Use the specification to determine the functionality of the USB driver and the related design decisions.
If you are new to USB driver development, use the OSR USB FX2 learning kit to study USB samples included with the WDK. You can get the learning kit from OSR Online. It contains the USB FX2 device and all the required hardware specifications to implement a client driver.
You can also get a Microsoft USB Test Tool (MUTT) devices. MUTT hardware can be purchased from JJG Technologies. The device does not have installed firmware installed. To install firmware, download the MUTT software package from this Web site and run MUTTUtil.exe. For more information, see the documentation included with the package.
Recommended reading
- Developing Drivers with Windows Driver Foundation, written by Penny Orwick and Guy Smith. For more information, see Developing Drivers with WDF.
Instructions
Step 1: Generate the KMDF driver code by using the Visual Studio Professional 2019 USB driver template
For instructions about generating KMDF driver code, see the steps in Writing a KMDF driver based on a template.
For USB-specific code, select the following options in Visual Studio Professional 2019
- In the New Project dialog box, in the search box at the top, type USB.
- In the middle pane, select Kernel Mode Driver, USB (KMDF).
- Select Next.
- Enter a project name, choose a save location, and select Create.
The following screen shots show the New Project dialog box for the USB Kernel-Mode Driver template.
This topic assumes that the name of the Visual Studio project is 'MyUSBDriver_'. It contains the following files:
| Files | Description |
|---|---|
| Public.h | Provides common declarations shared by the client driver and user applications that communicate with the USB device. |
| <Project name>.inf | Contains information required to install the client driver on the target computer. |
| Trace.h | Declares tracing functions and macros. |
| Driver.h; Driver.c | Declares and defines driver entry points and event callback routines. |
| Device.h; Device.c | Declares and defines event callback routine for the prepare-hardware event. |
| Queue.h; Queue.c | Declares and defines an event callback routine for the event raised by the framework's queue object. |
Step 2: Modify the INF file to add information about your device
Before you build the driver, you must modify the template INF file with information about your device, specifically the hardware ID string.
In Solution Explorer, under Driver Files, double-click the INF file.
In the INF file you can provide information such as the manufacturer and provider name, the device setup class, and so on. One piece of information that you must provide is the hardware identifier of your device.
To provide the hardware ID string:
Attach your USB device to your host computer and let Windows enumerate the device.
Open Device Manager and open properties for your device.
On the Details tab, select Hardward Ids under Property.
The hardware ID for the device is displayed in the list box. Select and hold (or right-click) and copy the hardware ID string.
Replace USBVID_vvvv&PID_pppp in the following line with your hardware ID string.
[Standard.NT$ARCH$] %MyUSBDriver_.DeviceDesc%=MyUSBDriver__Device, USBVID_vvvv&PID_pppp
Step 3: Build the USB client driver code
To build your driver
- Open the driver project or solution in Visual Studio Professional 2019
- Select and hold (or right-click) the solution in the Solution Explorer and select Configuration Manager.
- From the Configuration Manager, select the Active Solution Configuration (for example, Windows 8 Debug or Windows 8 Release) and the Active Solution Platform (for example, Win32) that correspond to the type of build you're interested in.
- From the Build menu, select Build Solution.
For more information, see Building a Driver.
Install Driver For Usb Device
Step 4: Configure a computer for testing and debugging
To test and debug a driver, you run the debugger on the host computer and the driver on the target computer. So far, you have used Visual Studio on the host computer to build a driver. Next you need to configure a target computer. To configure a target computer, follow the instructions in Provision a computer for driver deployment and testing.
Step 5: Enable tracing for kernel debugging
The template code contains several trace messages (TraceEvents) that can help you track function calls. All functions in the source code contain trace messages that mark the entry and exit of a routine. For errors, the trace message contains the error code and a meaningful string. Because WPP tracing is enabled for your driver project, the PDB symbol file created during the build process contains trace message formatting instructions. If you configure the host and target computers for WPP tracing, your driver can send trace messages to a file or the debugger.
To configure your host computer for WPP tracing
Drivers Visual Productions Usb Devices Download
Create trace message format (TMF) files by extracting trace message formatting instructions from the PDB symbol file.
You can use Tracepdb.exe to create TMF files. The tool is located in the <install folder>Windows Kits8.0bin<architecture> folder of the WDK. The following command creates TMF files for the driver project.
tracepdb -f [PDBFiles] -p [TMFDirectory]
The -f option specifies the location and the name of the PDB symbol file. The -p option specifies the location for the TMF files that are created by Tracepdb. For more information, see Tracepdb Commands.
At the specified location you'll see three files (one per .c file in the project). They are given GUID file names.
In the debugger, type the following commands:
.load Wmitrace
Loads the Wmitrace.dll extension.
.chain
Verify that the debugger extension is loaded.
!wmitrace.searchpath +<TMF file location>
Add the location of the TMF files to the debugger extension's search path.
The output resembles this:
Trace Format search path is: 'C:Program Files (x86)Microsoft Visual Studio 14.0Common7IDE;c:driverstmf'
To configure your target computer for WPP tracing
Make sure you have the Tracelog tool on your target computer. The tool is located in the <install_folder>Windows Kits8.0Tools<arch> folder of the WDK. For more information, see Tracelog Command Syntax.
Open a Command Window and run as administrator.
Type the following command:
tracelog -start MyTrace -guid #c918ee71-68c7-4140-8f7d-c907abbcb05d -flag 0xFFFF -level 7-rt -kd
The command starts a trace session named MyTrace.
The guid argument specifies the GUID of the trace provider, which is the client driver. You can get the GUID from Trace.h in the Visual Studio Professional 2019 project. As another option, you can type the following command and specify the GUID in a .guid file. The file contains the GUID in hyphen format:
tracelog -start MyTrace -guid c:driversProvider.guid -flag 0xFFFF -level 7-rt -kd
You can stop the trace session by typing the following command:
tracelog -stop MyTrace
Step 6: Deploy the driver on the target computer
- In the Solution Explorer window, select and hold (or right-click) the <project name>Package , and choose Properties.
- In the left pane, navigate to Configuration Properties > Driver Install > Deployment.
- Check Enable deployment, and check Import into driver store.
- For Remote Computer Name, specify the name of the target computer.
- Select Install and Verify.
- Select Ok.
- On the Debug menu, choose Start Debugging, or press F5 on the keyboard.
Note Do not specify the hardware ID of your device under Hardware ID Driver Update. The hardware ID must be specified only in your driver's information (INF) file.
For more information about deploying the driver to the target system in Visual Studio Professional 2019, see Deploying a Driver to a Test Computer.
You can also manually install the driver on the target computer by using Device Manager. If you want to install the driver from a command prompt, these utilities are available:
This tool comes with the Windows. It is in WindowsSystem32. You can use this utility to add the driver to the driver store.
For more information, see PnPUtil Examples.
This tool comes with the WDK. You can use it to install and update drivers.
Step 7: View the driver in Device Manager
Usb Driver Device Manager
Enter the following command to open Device Manager:
devmgmt
Verify that Device Manager shows a node for the following node:
Samples
MyUSBDriver_Device
Step 8: View the output in the debugger
Visual Studio first displays progress in the Output window. Then it opens the Debugger Immediate Window. Verify that trace messages appear in the debugger on the host computer. The output should look like this, where 'MyUSBDriver_' is the name of the driver module:
Drivers Visual Productions Usb Devices 3.0
Related topics
Understanding the KMDF template code for a USB client driver
Getting started with USB client driver development