search

lure23 / ESP32-WSL

Instructions for setting up ESP32 development, within virtual Linux environments
8 stars 2 forks source link

Unnecessary to install drivers on host side #3

Open david-schoe opened 2 months ago

david-schoe commented 2 months ago

Installing drivers on the host side is unnecessary as all driver actions take place on the wsl side. The portion of this project which states to start systemd at boot is the only reason this works... that is, systemd fires up udev daemon, which handles the necessary driver installation at runtime for the wsl side. Specifically, when the usb device is (virtually) "plugged in" by using "usbipd attach -w -b " udev will get the necessary driver. In your case, it is fetching the necessary cp210x driver and then initializing the virtual usb port to be driven by the cp210x driver. In my case, it is fetching the necessary ch341 driver and then initializing the virtual usb port to be driven by the ch341 driver.

In a nutshell, my setup arranges the binary flash data being "written" to the esp32 to first be converted to serial input, (handled by the ch341 driver), then sends this data to be packaged with tcp/ip protocol, then sends this data to the host; from there the host will unpackage the tcp/ip layer, and then route the serial data down to the usb device. That is, no driving occurs on the host side.

The reason I learned all of this was in large part because of the portion of your readme which (inaccurately) states that i should install the cp210x driver on the host side.

My proposol is that you remove the driver installation portion of your code, and make a note of systemd handling all driver configurations...

Let me know your thoughts on the matter :)

david-schoe commented 2 months ago

Still... an extremely helpful REPO!!

Thanks for posting this... it for real saved me A LOT of time researching...

just thought it could maybe use a tune up ;)

lure23 commented 1 month ago

@david-schoe Thanks for the feedback!

My proposol is that you remove the driver installation portion of your code, and make a note of systemd handling all driver configurations...

I'm very happy to take a PR on this, from you.

This repo is in an inactive state (doesn't mean corrections are welcome if they are helpful to others!!). I've moved on to using Multipass on macOS for my ESP32 development.

So, shall it be: