Cypress USB-Serial with Custom VID/PID and Manufacturing Interface Disabled - KBA222695
Employee
Feb 19, 2018
12:11 AM
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Feb 19, 2018
12:11 AM
Version: **
Translation - Japanese: カスタムVID/PIDおよび無効化された製造インターフェースでのサイプレスUSB-シリアル - KBA222695 - Community Translated (JA)
Question:
What is the driver binding procedure when a Cypress USB-Serial device is programmed with a custom VID/PID and with the manufacturing interface disabled?
Answer:
Cypress USB-Serial Configuration Utility allows the usage of a custom VID/PID for the USB-Serial devices. When using a custom VID/PID and with the manufacturing interface disabled, follow this procedure to bind the device with the Cypress binder:
Note: This document illustrates the procedure to bind the driver only for devices with vendor interface and not the CDC class devices.
- Modify the cyusb3.inf file to include the custom VID/PID. See this link for the procedure.
- In the Run command, type devmgmt.msc, and press Enter. This opens the Device Manager. With the manufacturing interface disabled, the device appears in the Device Manager as shown in the below figure:
- Double-click the device. In the Properties window, go to the Details tab. The hardware IDs of the device do not contain the manufacturing interface (MI) and will as listed in the below figure:
- Click the device in Device Manager and select Update Driver Software. The following figures show the steps to be performed to bind the device to the ‘USB-Serial Composite Device’ driver.
- After the device is successfully bound to the ‘USB-Serial Composite Device’ driver, the device again appears in the Device Manager under the Unknown Devices section. Now, the hardware IDs of the device contain the manufacturing interface (MI) number. Double-click the device. In the Properties window, go to the Details tab to view the hardware IDs.
- Repeat the same procedure to bind the driver to this device. Now, the device must be bound to the Vendor driver instead of the CDC driver as done earlier.
The device is now successfully bound to the proper Cypress drivers.
Labels
Rate this article: