https://github.com/kutukvpavel/esp32-win7-vcp-drivers

INF files that enable ESP32-S3 Serial/JTAG peripheral and TinyUSB CDC stack on Win7
https://github.com/kutukvpavel/esp32-win7-vcp-drivers

cdc driver drivers esp32 serialport win7 win8 windows-7 windows-8-1

Last synced: 6 days ago
JSON representation

INF files that enable ESP32-S3 Serial/JTAG peripheral and TinyUSB CDC stack on Win7

• Host: GitHub
• URL: https://github.com/kutukvpavel/esp32-win7-vcp-drivers
• Owner: kutukvpavel
• Created: 2022-04-25T21:26:42.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2023-05-06T21:36:52.000Z (over 1 year ago)
• Last Synced: 2024-09-23T20:33:04.044Z (10 days ago)
• Topics: cdc, driver, drivers, esp32, serialport, win7, win8, windows-7, windows-8-1
• Homepage:
• Size: 17.6 KB
• Stars: 19
• Watchers: 2
• Forks: 2
• Open Issues: 3
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# ESP32 Win7 VCP drivers

INF files that enable ESP32-S3 Serial/JTAG peripheral and TinyUSB CDC stack operation as VCP on Win7/8.

The issue with Win7 and Win8.1 is that usbser.sys class driver doesn't get installed automatically for devices belonging to the Communications Device Class (CDC), because Windows 7/8 lacks usbser.inf and possibly some other components I don't have the expertise to fiddle with. Therefore, even if you install WinUSB driver as per Espressif documentation (https://docs.espressif.com/projects/esp-idf/en/v4.3/esp32s2/api-guides/dfu.html?#api-guide-dfu-flash-win), you won't be able to get a serial port (only a useless "Universal Serial Bus Device" will show up).

This is well-documented on MS website:

 - https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-driver-installation-based-on-compatible-ids

 - https://docs.microsoft.com/en-us/troubleshoot/windows-client/deployment/how-to-use-reference-usbser-driver-universal-serial-bus

 - https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/supported-usb-classes

Therefore, the solution is simple: provide your own INF file with your VID/PID that references usbser.sys in some way. MS recommends to do it indirectly, through modem class. You don't have to install WinUSB using Zadig, if you use these custom INFs! If you did, you may need to uninstall it. Windows will warn you that it can't verify the publisher of these INFs, since I didn't include a \*.cat file, you can ignore it.

This repo contains INFs with VID/PID/MIs for:

 - ESP32-S3 embedded Serial/JTAG USB stack (located in ROM), activated as "(secondary) serial console" in configuration \[esp32-vcp-jtag.inf\]

 - ESP32-IDF TinyUSB stack, configured to use Espressif VID and TinyUSB PID \[esp32-tinyusb.inf\]

In case your particular chip has a different PID, you can just edit the INF yourself (look at \[Models. ...\] sections). Feel free to create pull requests for new chips.

Thanks to David Grayson for an INF template: https://stackoverflow.com/questions/41928144/inf-file-cant-find-usbser-sys-in-windows-7-only

# Additional info

Usually ESP32 native USB stack (the one contained in ROM) exposes 2 USB endpoints (devices). Only one of the 2 endpoints provides the serial port functionality. This is by design. Go to device manager -> device properties and look up "Compatible IDs". For one of the endpoints you should see `USB\Class_02&SubClass_02` - this is the COM port you have to install the INF for.