TTL to USB Cables from Prolific Chipsets and Older Model with Windows/WSL

Hey There,

Seth here. Um, does anyone know if using a Prolific Chipset TTL to USB cable works on the older am335x supported boards like the BBB or BeagleBone Green?


P.S. I have one and it reads via lsusb:

Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Phone Data Cable

But…the /dev/ttyUSB0 device does not show up… I am bummed out and want to try to figure this one out.

Some serial devices show up as ACMx devices

Thank you. I will check. This chipset is pre-2016 I think.


P.S. Plus, and this may matter right now, I am using WSL2 on a Windows Machine for testing out the chipset for the BBG.


For anyone testing with WSL2 Debian Bookworm, kernel 5.10.x, on Windows 11 Machines for the Prolific pre-2016, see below:

2-8 067b:2303 PL2303TA DO NOT SUPPORT WINDOWS 11 OR LATER, PLEASE CONTA... Not shared

and when I share it on the WSL2 side of things:

Bus 001 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Phone Data Cable

But, I have no way to contact the serial device via tio.

@benedict.hewson ,

Another Update

So, tio /dev/tty worked…

I am not getting a boot log yet. I will try to reboot.

Just an update here…

So, Linux should be the cure. Even though I can use usbipd on Windows 11 and install/attach/bind the device for WSL2 use, I get nothing in the form of /dev/ttyUSB0 and nothing in the form of /dev/ttyACM0.

This is okay, i.e. since I have a Debian Bookworm Distro handy I can utilize to handle the connection.

Updates on the way for anyone who cares!



And yes sir, so. Linux works out-of-the-box with the current image along with /dev/ttyUSB0. I am using a Debian Bookworm Distro for the host while the target, this BBG, has Bullseye on it.