Can you give some insturctions how to do it?

[roysG]

No description provided.

[kutukvpavel]

How to do what exactly? Well, okay, I can think of 3 questions.

1. How to install INF files?

The same way you manually install any driver under Windows: device manager → device context menu → update drivers → select location → ... → profit.

In fact, the INF is merely a "driver setup information" file, you can always find one beside vendor-supplied driver executables. This might puzzle you. However, this file contains everything device manager needs to install a device driver, so yes, it will let you "install" the INF only.

The trick is, we don't need a custom driver executable, i.e. we don't need a custom driver at all. These INFs just point to a generic usb-to-serial class-driver already inluded with OS distribution, and instruct Windows to use it for specified device (VID, PID etc). This is mentioned in Readme.

2. How to edit the INFs to support custom VID/PID identifiers?

You just rename the INF file accordingly, open the INF in you favorite text editor, and edit relevant lines:

• under [Strings]
DriverPackageDisplayName="your driver package name"
esp="your device name to display in device manager"
• under [Models. ... ]
  Replace the VID and PID numbers for all 3 driver models (x86, x64, arm, we don't care about the host PC arch) to match yours. You may have to include interface ID (MI) for the "driver update" procedure to work. I do include MIs by default. You can find your PID/VID/MI in device manager → device properties → Hardware IDs.
• under [Version]
  I usually use current date, to ensure that my driver appears "newer" for the driver update procedure. But this is optional.

3. Native ESP32 USB stack exposes 2 devices (hence it's called Serial/JTAG, I believe), and obviously only one of them is the serial port that will become visible after INF installation. How to find out which one?

See updated readme.