Microchip / USB / Device - WinUSB - Generic Driver Demo / Driver and INF / mchpwinusb.inf. When the driver package is signed, any modifications to this.inf file. The Function Drivers implements various USB device classes as per the class specification. The USB Device Library architecture can support multiple instances of a function driver. An example would be a USB CDC device that emulates two serial ports. Function drivers provide an abstracted and an easy to use interface to the application. It seems like if windows 10 recognizes this device only if it’s connected when starting. I tried to desinstall / reinstall (automatically) the USB driver but there is no change. I need some help to make PICKit3 working normally with my PC under Win10.

-->

Summary

• Opening the device and obtaining WinUSB handle.
• Getting information about the device, configuration, and interface settings of all interfaces, and their endpoints.
• Reading and writing data to bulk and interrupt endpoints.

Important APIs

This topic includes a detailed walkthrough of how to use WinUSB Functions to communicate with a USB device that is using Winusb.sys as its function driver.

If you are using Microsoft Visual Studio 2013, create your skeleton app by using the WinUSB template. In that case, skip steps 1 through 3 and proceed from step 4 in this topic. The template opens a file handle to the device and obtains the WinUSB handle required for subsequent operations. That handle is stored in the app-defined DEVICE_DATA structure in device.h.

For more information about the template, see Write a Windows desktop app based on the WinUSB template.

Note WinUSB functions require Windows XP or later. You can use these functions in your C/C++ application to communicate with your USB device. Microsoft does not provide a managed API for WinUSB.

Prerequisites

The following items apply to this walkthrough:

• This information applies to Windows 8.1, Windows 8, Windows 7, Windows Server 2008, Windows Vista versions of Windows.
• You have installed Winusb.sys as the device's function driver. For more information about this process, see WinUSB (Winusb.sys) Installation.
• The examples in this topic are based on the OSR USB FX2 Learning Kit device. You can use these examples to extend the procedures to other USB devices.

Step 1: Create a skeleton app based on the WinUSB template

To access a USB device, start by creating a skeleton app based on the WinUSB template included in the integrated environment of Windows Driver Kit (WDK) (with Debugging Tools for Windows) and Microsoft Visual Studio.You can use the template as a starting point.

For information about the template code, how to create, build, deploy, and debug the skeleton app, see Write a Windows desktop app based on the WinUSB template.

The template enumerates devices by using SetupAPI routines, opens a file handle for the device, and creates a WinUSB interface handle required for subsequent tasks. For example code that gets the device handle and opens the device, see Template code discussion.

Step 2: Query the Device for USB Descriptors

Next, query the device for USB-specific information such as device speed, interface descriptors, related endpoints, and their pipes. The procedure is similar to the one that USB device drivers use. However, the application completes device queries by calling WinUsb_GetDescriptor.

The following list shows the WinUSB functions that you can call to get USB-specific information:

• Additional device information.

  Call WinUsb_QueryDeviceInformation to request information from the device descriptors for the device. To get the device's speed, set DEVICE_SPEED (0x01) in the InformationType parameter. The function returns LowSpeed (0x01) or HighSpeed (0x03).

• Interface descriptors

  Call WinUsb_QueryInterfaceSettings and pass the device's interface handles to obtain the corresponding interface descriptors. The WinUSB interface handle corresponds to the first interface. Some USB devices, such as the OSR Fx2 device, support only one interface without any alternative setting. Therefore, for these devices the AlternateSettingNumber parameter is set to zero and the function is called only one time. WinUsb_QueryInterfaceSettings fills the caller-allocated USB_INTERFACE_DESCRIPTOR structure (passed in the UsbAltInterfaceDescriptor parameter) with information about the interface. For example, the number of endpoints in the interface is set in the bNumEndpoints member of USB_INTERFACE_DESCRIPTOR.

  For devices that support multiple interfaces, call WinUsb_GetAssociatedInterface to obtain interface handles for associated interfaces by specifying the alternative settings in the AssociatedInterfaceIndex parameter.

• Endpoints

  Call WinUsb_QueryPipe to obtain information about each endpoint on each interface. WinUsb_QueryPipe populates the caller-allocated WINUSB_PIPE_INFORMATION structure with information about the specified endpoint's pipe. The endpoints' pipes are identified by a zero-based index, and must be less than the value in the bNumEndpoints member of the interface descriptor that is retrieved in the previous call to WinUsb_QueryInterfaceSettings. The OSR Fx2 device has one interface that has three endpoints. For this device, the function's AlternateInterfaceNumber parameter is set to 0, and the value of the PipeIndex parameter varies from 0 to 2.

  To determine the pipe type, examine the WINUSB_PIPE_INFORMATION structure's PipeInfo member. This member is set to one of the USBD_PIPE_TYPE enumeration values: UsbdPipeTypeControl, UsbdPipeTypeIsochronous, UsbdPipeTypeBulk, or UsbdPipeTypeInterrupt. The OSR USB FX2 device supports an interrupt pipe, a bulk-in pipe, and a bulk-out pipe, so PipeInfo is set to either UsbdPipeTypeInterrupt or UsbdPipeTypeBulk. The UsbdPipeTypeBulk value identifies bulk pipes, but does not provide the pipe's direction. The direction information is encoded in the high bit of the pipe address, which is stored in the WINUSB_PIPE_INFORMATION structure's PipeId member. The simplest way to determine the direction of the pipe is to pass the PipeId value to one of the following macros from Usb100.h:

  • The USB_ENDPOINT_DIRECTION_IN (PipeId) macro returns TRUE if the direction is in.
  • The USB_ENDPOINT_DIRECTION_OUT(PipeId) macro returns TRUE if the direction is out.

  The application uses the PipeId value to identify which pipe to use for data transfer in calls to WinUSB functions, such as WinUsb_ReadPipe (described in the 'Issue I/O Requests' section of this topic), so the example stores all three PipeId values for later use.

The following example code gets the speed of the device that is specified by the WinUSB interface handle.

The following example code queries the various descriptors for the USB device that is specified by the WinUSB interface handle. The example function retrieves the types of supported endpoints and their pipe identifiers. The example stores all three PipeId values for later use.

Step 3: Send Control Transfer to the Default Endpoint

Next, communicate with the device by issuing control request to the default endpoint.

All USB devices have a default endpoint in addition to the endpoints that are associated with interfaces. The primary purpose of the default endpoint is to provide the host with information that it can use to configure the device. However, devices can also use the default endpoint for device-specific purposes. For example, the OSR USB FX2 device uses the default endpoint to control the light bar and seven-segment digital display.

Control commands consist of an 8-byte setup packet, which includes a request code that specifies the particular request, and an optional data buffer. The request codes and buffer formats are vendor defined. In this example, the application sends data to the device to control the light bar. The code to set the light bar is 0xD8, which is defined for convenience as SET_BARGRAPH_DISPLAY. For this request, the device requires a 1-byte data buffer that specifies which elements should be lit by setting the appropriate bits.

The application can set this through the user interface (UI), such as by providing a set of eight check box controls to specify which elements of the light bar should be lit. The specified elements correspond to the appropriate bits in the buffer. To avoid UI code, the example code in this section sets the bits so that alternate lights get lit up.

Use the following steps to issue a control request.

1. Allocate a 1-byte data buffer and load the data into the buffer that specifies the elements that should be lit by setting the appropriate bits.

2. Construct a setup packet in a caller-allocated WINUSB_SETUP_PACKET structure. Initialize the members to represent the request type and data as follows:

   • The RequestType member specifies request direction. It is set to 0, which indicates host-to-device data transfer. For device-to-host transfers, set RequestType to 1.
   • The Request member is set to the vendor-defined code for this request, 0xD8. It is defined for convenience as SET_BARGRAPH_DISPLAY.
   • The Length member is set to the size of the data buffer.
   • The Index and Value members are not required for this request, so they are set to zero.

3. Call WinUsb_ControlTransfer to transmit the request to the default endpoint by passing the device's WinUSB interface handle, the setup packet, and the data buffer. The function receives the number of bytes that were transferred to the device in the LengthTransferred parameter.

Microchip Usb Devices Driver Updater

The following code example sends a control request to the specified USB device to control the lights on the light bar.

Step 4: Issue I/O Requests

Next, send data to the device's bulk-in and bulk-out endpoints that can be used for read and write requests, respectively. On the OSR USB FX2 device, these two endpoints are configured for loopback, so the device moves data from the bulk-in endpoint to the bulk-out endpoint. It does not change the value of the data or add any new data. For loopback configuration, a read request reads the data that was sent by the most recent write request. WinUSB provides the following functions for sending write and read requests:

To send a write request

1. Allocate a buffer and fill it with the data that you want to write to the device. There is no limitation on the buffer size if the application does not set RAW_IO as the pipe's policy type. WinUSB divides the buffer into appropriately sized chunks, if necessary. If RAW_IO is set, the size of the buffer is limited by the maximum transfer size supported by WinUSB.
2. Call WinUsb_WritePipe to write the buffer to the device. Pass the WinUSB interface handle for the device, the pipe identifier for the bulk-out pipe (as described in the Query the Device for USB Descriptors section of this topic), and the buffer. The function returns the number of bytes that are actually written to the device in the bytesWritten parameter. The Overlapped parameter is set to NULL to request a synchronous operation. To perform an asynchronous write request, set Overlapped to a pointer to an OVERLAPPED structure.

Write requests that contain zero-length data are forwarded down the USB stack. If the transfer length is greater than a maximum transfer length, WinUSB divides the request into smaller requests of maximum transfer length and submits them serially.The following code example allocates a string and sends it to the bulk-out endpoint of the device.

To send a read request

• Call WinUsb_ReadPipe to read data from the bulk-in endpoint of the device. Pass the WinUSB interface handle of the device, the pipe identifier for the bulk-in endpoint, and an appropriately sized empty buffer. When the function returns, the buffer contains the data that was read from the device. The number of bytes that were read is returned in the function's bytesRead parameter. For read requests, the buffer must be a multiple of the maximum packet size.

Zero-length read requests complete immediately with success and are not sent down the stack. If the transfer length is greater than a maximum transfer length, WinUSB divides the request into smaller requests of maximum transfer length and submits them serially. If the transfer length is not a multiple of the endpoint's MaxPacketSize, WinUSB increases the size of the transfer to the next multiple of MaxPacketSize. If a device returns more data than was requested, WinUSB saves the excess data. If data remains from a previous read request, WinUSB copies it to the beginning of the next read request and completes the request, if necessary.The following code example reads data from the bulk-in endpoint of the device.

Step 5: Release the Device Handles

After you have completed all the required calls to the device, release the file handle and the WinUSB interface handle for the device. For this, call the following functions:

• CloseHandle to release the handle that was created by CreateFile, as described in the step 1.
• WinUsb_Free to release the WinUSB interface handle for the device, which is returned by WinUsb_Initialize.

Step 6: Implement Main

The following code example shows the main function of your console application.

Microchip Usb Devices Driver Adapter

Next steps

Microchip USB Devices Driver

If your device supports isochronous endpoints, you can use WinUSB Functions to send transfers. This feature is only supported in Windows 8.1.

For more information, see Send USB isochronous transfers from a WinUSB desktop app.

Related topics

Microchip Usb Device Driver

WinUSB
WinUSB Architecture and Modules
WinUSB (Winusb.sys) Installation
WinUSB Functions for Pipe Policy Modification
WinUSB Power Management
WinUSB Functions
Write a Windows desktop app based on the WinUSB template

Course M203 - A Comprehensive Introduction to USB and USB Programming Using PIC24 and dsPIC Microcontrollers

Duration: 5 Days

Intended Audience

Attendees are expected to have some familiarity with C programming, as well as some experience of working on embedded systems.

Synopsis

The course will provide an introduction to programming USB devices in PIC24 and dsPIC based applications. The emphasis will be on practical applications covering Human Interface Device (HID), Communication Class Device (CDC) and Mass Storage device classes. The course will also cover usage of USB Protocol analysers for testing, debugging and reverse engineering of USB application protocols. Key topics covered will include

• An overview and critique of the USB 1.x and 2 protocol standards
• The use USB Protocol analysers in troubleshooting and debugging USB application problems
• An guided tour of the Microchip USB protocol stack
• Techniques for implementing USB based applications for control, data logging and data acquisition purposes

Microchip Usb Devices Driver Vga

Course Outline

Microchip Usb Devices Drivers

• Overview of USB
• History of USB
• Uses, benefits and limitations of USB
• Evolution of USB Standards - USB 1.0, USB 1.1, USB 2.0, USB 3.0, USB On-The-Go, Wireless USB
• Overview of USB Transfers and Transactions
• USB Transfer Types
• Control transfers
• Bulk transfers
• Interrupt transfers
• Isochronous transfers
• Time-critical transfers
• Device Enumeration - How the host learns about devices
• The enumeration process
• Device insertion and removal
• Interfaces and descriptors
• Control Transfers
• Structure of the control transfer process
• Standard USB requests
• Class-Specific requests
• Vendor-Defined requests
• Microchip PIC24 and dsPIC Devices and associated firmware and hardware
• PIC24 and dsPIC USB on chip device peripheral
• Overview of the MLA USB Protocol Stack
• Overview of the MLA USB Protocol Stack APIs for application development
• Understanding Host Communication with a USB Device
• USB Windows device driver model
• Linux USB device driver model
• Kernel mode vs. user mode drivers
• How a driver is matched to a device
• How a device is detected
• Human Interface Devices
• Overview of HID
• HID Reports
• HID case studies
• HID compliant consumer control devices
• Implementing a target board HID device
• Implementing a PC based application for controlling and interacting with a target HID device.
• Mass Storage Device Implementation
• Overview of SD Card technology
• Adding SD card support to Microchip applications
• Microchip File system and FAT32 filesystem firmware
• Case study - Implementing an SD Card - PIC24 and dsPIC USB based mass storage device
• Implementing Communication Class Devices (CDC) using Microchip Controllers
• Implementing a PIC24 and dsPIC USB based CDC device
• Microsoft Windows CDC device driver aspects and driver signing
• Controlling and interacting with a CDC target device from a PC
• USB - Bootloaders
• Overview of Bootloaders
• Overview of an Implementation of a USB based bootloader for a PIC24 and dsPIC USB microcontroller
• Advanced USB Topics
• USB OTG (On The Go) Protocol
• USB OTG compared with Host USB
• 16 bit Microcontrollers having USB OTG Modules
• Overview of DMA - Direct Memory Access
• PIC24/dsPIC microcontrollers with DMA support
• Using DMA with USB