USB drive installation and Firmware Programming, USB learning notes

USB drive installation and Firmware Programming, USB learning notes

As mentioned in previous blogs, the two core drivers are the xxx. sys file, the xxx. inf file, and the xxx. inf file on the host.

The following file describes the USB driver. For users, the xxx. sys file does not need to be modified. Users can modify the content of the xxx. inf file.

Is the name of the cy_usb application manual. You can find the manual to view information about the USB driver.

Is the system supported by the current driver.

Is a supported VID & PID pair, and note that if you modify the cyUSB3.inf file and add your own VID & PID, this will cause the device to become unsigned. We do not recommend that you use an unsigned driver in windows. Pay special attention to this.

The current version supports features and is compatible with drivers such as 2.0 and 3.0.

It is a description in the manual, mainly for users to modify cyUSB3.inf, you can add a device identification number, replace the cypress display characters during the installation of the corresponding driver, complete the driver custom wizard. The serial number corresponding to the GUID is fixed. refer to the previous blog.

Modify VID & PID Name:

Modify strings

The Manual stipulates that, if you only modify the content of the current VID and PID, you need to create a new xxx. inf file and modify the original content.

This section describes how to add the VID and PID to the corresponding operating system directory for different operating systems, as shown in:

If we want to generate our own control information, what should we do.

First, declare that a complete USB system should include firmware programs, drivers, and host computer programs to form a USB system. If you want to change the USB signature, you must start with the firmware program and driver program (someone asks, isn't that nonsense .... Okay, it's a good joke ).

USB firmware programming is the core of the entire design task. The USB firmware program is used to recognize, relist, and process devices, USB protocols, and external hardware, responsible for data communication with USB hosts. To change the signature, start with the firmware program. There are many firmware programs in the firmware file after the kit is installed, as shown in:

We can choose a firmware, such as bulkloop, which can be opened using the keil software, as shown in:

Note that the dscr. a51 file contains the USB descriptor, device descriptor, device limitation descriptor, configuration descriptor, string descriptor, and user descriptor. For more information about descriptors, see the related blog-Introduction to USB descriptors.

The point is that the firmware contains the device descriptor and other information. If you want to change the USB signature. First, change the VID, PID, and version ID on the graph. (This change may invalidate the digital signature. For more information, see the related blog-USB Digital Signature.)

Change the VID and PID as follows:

The string is changed to the following:

// ================================================ ======================================

Note !!!!!!

The above operations are the corresponding firmware operations. The VID and PID of the firmware correspond to 0x52EA, and the corresponding operations should also be performed in the driver, as shown in: